Domain-Driven Design: Hidden Lessons from the Big Blue Book
summary
Argues that the 15-year-old DDD book hides practical moves for today: use event storming to map processes end-to-end and involve developers in continuous discovery; apply concrete heuristics (for example the money heuristic, marry‑me, T1000, Erlang) to decide when to refactor, wrap, or split code; treat bounded contexts as team boundaries so teams gain autonomy — one case shows a squad decoupling about 95% of dependencies and delivering months ahead.
AI-written summary · about
chapters (20)
- 0:00Start
- 6:01CONTINUOUS DISCOVERY & DELIVERY
- 8:16SUSTAINABLE EVOLUTION
- 9:06HOW TO CREATE EVOLVABLE SYSTEMS
- 11:20EVENT STORMING
- 12:01MODEL DOMAIN AS TIMELINE
- 12:57ADD COMMANDS, USERS, POLICIES
- 13:08EXTERNAL SYSTEMS, MONEY, UX
- 13:52PERSONAL ES TRIUMPHS
- 15:33HIDDEN LESSONS
- 17:49ANTI-CORRUPTION LAYER
- 20:12LEGACY LASAGNE
- 21:53HEURISTICS FROM THE BOOK
- 22:45MORE HEURISTICS
- 24:43GAME OF THRONES HEURISTIC
- 25:41HEURISTICS MASTERS
- 28:53MULTIPLE HIDDEN CONTEXTS
- 29:04MULTIPLE BOUNDED CONTEXTS
- 33:59HOW TO FIND BOUNDARIES
- 36:59DESIGNING COMPLEX SYSTEMS
related talks
38mDomain-Driven Design: Hidden Lessons from the Big Blue Book
41mDomain-Driven Design: Hidden Lessons from the Big Blue Book
29m20 Years of Domain-Driven Design: What I’ve Learned About DDD
58mDDD really matters!
57mDomain-Driven Design in Productland
01h 11mAn introduction to DDD
49mDomain-Driven Design & Team Topologies For Product-led Organizations
50mIt's All About the Domain, Honey - Domain-Focused Architecture with DDD
