How to cook Domain Driven Design
summary
Explains why and when to use Domain-Driven Design, its pros and cons, and concrete ways to design a service’s internal architecture for maintainability and clarity. Uses one service as a running example to show DDD practices, architectural styles beyond CRUD/MVC, and practical tips for writing extensible, understandable code for developers at any level.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:43What is Domain Driven Design
- 5:53Strategic versus tactical design
- 9:28DDD architectural styles
- 13:37DDD code structure
- 20:26Interfaces and infrastructure layer
- 22:17Application services and business logic
- 27:30Presentation layer and tech independence
- 29:34Layer interaction in practice
- 31:06Transactions and eventual consistency
- 33:16Book recommendations and summary
- 35:06Q&A
- 38:45Registry and resources Q&A
- 41:59Libraries and tools Q&A
- 42:43Engaging with business
- 44:08Testing and architecture checks
- 45:13Implementation and training Q&A
- 47:01Additional resources
- 48:03DDD drawbacks and conclusion
related talks
38mWhat I talk about when I talk about Domain Driven design
48mDomain-Driven Design tactically and practically
46mDomain Driven Design The Basics
42mDomain Driven Design - So Your Code Speaks Plain Language
44mGo in Domain Driven Design
59mDomain-Driven Design - Where Rubber Meets the Road
45mDomain Driven Modular Architecture
55mDomain-Driven Design: back to the roots