Domain-Driven Design Made Simple | What is it, and Why you need it? | Introduction to DDD | Geekific 

Thanks a lot! They're in the making, the list is big and am struggling to pick what to do next, but at some point we'll get there :)

ඔබ්විඝ්හ්ග්

Thank you!! Glad you liked it :)

Thanks a lot :) Working on it!

xD

Glad it was helpful! Thanks for the support :)

Glad you enjoyed it!

Thank you :) More are on the way! Stay Tuned!

Sure thing! Stay Tuned :)

Thank you, more are on the way!

Will be out this year promise.

@@geekific Thanks a lot. Now your channel became a source of information for me.

Glad you liked it! Will add it to my to-do list :) Stay Tuned!

Glad you liked it!

Wow! Thank you :)

Yes! Consider an application having a trivial context, easy to grasp, but maybe developing such an app could be challenging on the technical level (code wise). Cheers!

We already started doing this in our SpringBoot series! Check this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-pv-qFt69Bng.html. Part 2 will be uploaded very soon!

Glad I could help :) Answer #1: Yes, a bounded context can be thought of as a subdomain. A subdomain is a distinct area or aspect of a larger domain. In DDD, a bounded context is a logical boundary within which a domain model is defined. Answer #2: Yes, there can be some business logic implemented in the UI, especially in simpler applications. However, it's generally considered good practice to separate business logic from the UI layer in order to maintain a clean separation of concerns and to enable easier maintenance and testing. For example, in a web application where users can purchase products, the UI might include a form for users to enter their payment information. Some basic business logic could be implemented in the UI layer to perform basic data validation, such as ensuring that the user's credit card number is valid. However, more complex business logic, such as calculating taxes or applying discounts, would likely be implemented in a separate business logic layer. Answer #3: An entity in the domain is not exactly the same as the model in MVC, but there are some similarities. In DDD, an entity is a domain object that has a unique identity and is defined by its attributes and behavior. It represents a meaningful concept within the domain, and it encapsulates the domain logic related to that concept. In contrast, the model in MVC is a broader concept that encompasses the entire application's data representation and the logic for manipulating that data. It includes the business logic, but also the UI logic and other application-specific logic.

It is going to take time. Sorry. But it is on my list of upcoming videos. I promise :) Stay Tuned!

@@geekific hopefully soon enough, I learned lot about DDD unfortunately I was out for a while and I think I found the perfect place to reload my mind, you really do have the talent to teach brother I shall watch more of your videos

2ahla b Ghadi! Hope you found our videos helpful :)