Domain-Driven Design: Hidden Lessons from the Big Blue Book
summary
Argues that Domain-Driven Design hides nontechnical levers: bounded contexts as org design (splitting a monolith into team-owned contexts cuts coordination and yields demos every three weeks instead of months), practical patterns like an anti-corruption layer that let a promotion feature coexist with legacy code after a day of cleanup, and collaborative modeling techniques—called event storming—that surface domain rules quickly and make teams 10x more effective at discovering what to build.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:24TOP SOURCES OF PRODUCT IDEAS
- 9:32LESSON LEARNED
- 17:53THE DOMAIN QUIZ
- 19:03RULES, LAWS, AND PRINCIPLES
- 23:37LEGACY LASAGNE
- 33:27HIDDEN LESSONS
- 37:50What is the difference between Event storming workshop and user story mapping?
related talks
39mDomain-Driven Design: Hidden Lessons from the Big Blue Book
48mDomain-Driven Design tactically and practically
55mDomain-Driven Design: back to the roots
44mStrategic Domain-Driven Design for dummies
38mWhat I talk about when I talk about Domain Driven design
01h 02mDomain-Driven Design in ProductLand
59mDomain-Driven Design - Where Rubber Meets the Road
58mDDD really matters!