Trivialization of DDD or Not?
summary
The talk examines Domain-Driven Design beyond its common toolkit (Aggregates, Entities, Value Objects) and focuses on modeling business domain problems without adding code complexity. It reviews approaches for understanding the problem space and presents a deep, code-level modeling approach called Model-Driven Design to align the product core with domain experts’ expectations. The presenter emphasizes collaborative, domain-focused techniques to clarify complexity, resolve conflicts, and keep software adaptable to business needs.
AI-written summary · about
chapters (15)
- 0:00DDD trivialization intro
- 3:10Blue Book origins
- 8:31Bounded Context origins
- 14:53Six DDD approaches
- 15:38Event Storming overview
- 17:22Event Storming modeling
- 18:28Event Storming design
- 20:57Event Storming code gap
- 23:05Example Mapping aggregates
- 24:53CRC Cards design
- 25:37Supple Design practices
- 27:46Deep Modelling
- 30:37DDD serious approach?
- 32:48Cargo cult risks
- 33:30DDD strategy conclusion
related talks
38mWhat I talk about when I talk about Domain Driven design
38mModel-Driven Design
59mDomain-Driven Design - Where Rubber Meets the Road
42mDomain Driven Design - So Your Code Speaks Plain Language
31mIs Domain-Driven Design Overrated?
45mDon't Overdose on Domain-Driven Design
46mDomain Driven Design The Basics
48mObject modeling: Theory vs Practice. Round 1