20 Years of Domain-Driven Design: What I’ve Learned About DDD
summary
Claims that DDD is a 20-year practice focused on steering quality toward a core domain, not spreading it evenly; uses orange stickies in Event Storming for low-barrier collaborative modeling that surfaces who knows what; defines bounded contexts as model + ubiquitous language + team but recommends designing for autonomous modules (functionality over shared data); frames DDD as “knowledge crunching” and insists measurable customer value and direct domain expert conversations drive what gets refactored.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:45DDD Insights
- 10:33Customer Value
- 12:25Event Storming
- 17:44Bounded Contexts
- 27:24DDD Conclusions
related talks
39mDomain-Driven Design: Hidden Lessons from the Big Blue Book
38mWhat I talk about when I talk about Domain Driven design
45mDon't Overdose on Domain-Driven Design
39mLessons Learned from 10+ Years with Domain Driven Design
55mDomain-Driven Design: back to the roots
41mDomain-Driven Design: Hidden Lessons from the Big Blue Book
31mIs Domain-Driven Design Overrated?
44mStrategic Domain-Driven Design for dummies