The DDD Trilemma Explained and Solved (by a Lead Software Architect)

In this video I present a trilemma described in an excellent blog post on Domain Driven Design by Vladimir Khorikov: Domain model purity vs domain model completeness.

Vladimir believes that we can only have two of the following attributes when we translate a domain model into actual code: purity, completeness, and performance.

If we choose completeness and purity, we have to move database reads to the edges of an application. While, if we favor completeness and performance, we need to accept out-of-process dependencies in our model. Finally, choosing purity and performance forces us to split the business logic between the domain layer and the controller one.

Vladimir's suggest to opt for purity and performance. I don't fully agree. Tactical DDD offers several building blocks to define a domain model that were not considered in the blog post: Entities, Value Objects, Aggregates, Services, Repositories, etc.

Watch the video to know more!

-----
Vladimir Khorikov's blog post: https://enterprisecraftsmanship.com/posts/domain-model-purity-completeness/

🤝 *Do you want to connect with me? / Do you need my services?* 🤝
Visit my website: https://marcolenzo.eu
Add me on LinkedIn: https://www.linkedin.com/in/marcolenzo/
Add me on Twitter: https://twitter.com/marco_lenzo

📝 *Subscribe to my newsletter!* 📝
https://news.marcolenzo.eu

#ddd #softwarearchitecture #softwaredevelopment #softwaredesign

Тэги:

#domain_driven_design #trilemma #ddd #tactical_ddd #domain-driven_design #software_architecture #design_patterns #software_architecture_patterns #what_is_domain_driven_design #domain-driven_design_eric_evans #domain_driven_design_eric_evans #software_engineering #software_design #software_architecture_and_design

Скачать видео