This Is How Domain-Driven Design Makes Object-Oriented Design More Powerful

Become a sponsor to access source code ►   / zoranhorvat  
Join Discord server with topics on C# ► https://codinghelmet.com/go/discord
Enroll course Beginning Object-Oriented Programming with C# ► https://codinghelmet.com/go/beginning...
Subscribe ►    / @zoran-horvat  

It is my most profound belief that only through understanding the problem we are facing can we measure the impact of any given method that pertains to addressing that problem. So it stands for the Domain-Driven Design, which this video will try to assess. What problem are we trying to solve with design, and how does DDD help?
Whether some programmers want to acknowledge it or not, Domain-Driven Design has tremendously impacted how we do Object-Oriented Design nowadays. Programmers without knowledge of DDD will speak of entities, value objects, and even aggregates. They will know how to deal with an entity's identity almost instinctively and will take care to reference only specific entities - did anyone say aggregate roots? That indicates there is truth in DDD.
At the other end of the spectrum, we find hardline proponents of DDD who will tell you straight that applying only the tactical part of it is nothing compared to its true power. As if DDD could make all the troubles go away. It cannot, so my experience tells me.
Where is the truth, then? - you must be asking. I can hardly answer that question, but I know another question that is easier to decipher: How can we decide whether to use DDD and to what extent? Answering this question begins with my most profound belief that only through understanding the problem we are facing can we measure the impact of any given method that pertains to addressing that problem.
What problem does DDD address? - that is at the root of all questions. It's the same as what OOD does, only it does it better! Watch the video and learn how DDD adds magic on top of OOD to make it a more expressive and robust design method.

00:00 Intro
01:44 Dealing with Complexity
05:03 Designing with DDD
11:46 CQRS and Persistence

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⭐ CONNECT WITH ME 📱👨

🌐Become a patron ►   / zoranhorvat  
🌐Buy me a Coffee ► https://ko-fi.com/zoranhorvat
🗳 Pluralsight Courses ► https://codinghelmet.com/go/pluralsight
📸 Udemy Courses ► https://codinghelmet.com/go/udemy
📸 Join me on Twitter ►   / zoranh75  
🌐 Read my Articles ► https://codinghelmet.com/articles
📸 Join me on LinkedIn ►   / zoran-horvat  
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
👨 About Me 👨
Hi, I’m Zoran, I have more than 20 years of experience as a software developer, architect, team lead, and more. I have been programming in C# since its inception in the early 2000s. Since 2017 I have started publishing professional video courses at Pluralsight and Udemy and by this point, there are over 100 hours of the highest-quality videos you can watch on those platforms. On my YouTube channel, you can find shorter video forms focused on clarifying practical issues in coding, design, and architecture of .NET applications.❤️
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⚡️RIGHT NOTICE:
The Copyright Laws of the United States recognize a “fair use” of copyrighted content. Section 107 of the U.S. Copyright Act states: “Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phono records or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright." This video and our youtube channel, in general, may contain certain copyrighted works that were not specifically authorized to be used by the copyright holder(s), but which we believe in good faith are protected by federal law and the Fair use doctrine for one or more of the reasons noted above.

#csharp #dotnet #domaindrivendesign