Modularization — It Was Supposed to Be Beautiful but Turned Out as Usual :(
summary
The talk compares Event Storming (for eliciting domain knowledge) with C4 (for focusing on architectural drivers) and explains why teams often fail to move from one to the other. It presents how to convert Event Storming outputs into concrete architectural decisions using DDD strategic tools—context distillation and context mapping—and gives heuristics for designing a modular monolith or microservices with real autonomy by creating a single source of truth and avoiding single points of failure.
AI-written summary · about
chapters (9)
- 0:00Modularization problem
- 5:26Modularity traps example
- 9:12Conway's Law and architecture
- 13:53Context entanglement issues
- 20:19Context mapping concept
- 26:36Context ownership drift
- 32:56Ubiquitous language communication
- 40:23Ubiquitous language summary
- 47:30Conclusion reflections
related talks
51mModularization: Foundation of Microservices and Monoliths
43mGood Fences Make Good Neighbours
42mBounded Context — How to Modularize a System in a Few Steps
01mModularization: Foundation of Microservices and Monoliths
43mModular Monoliths: The Architecture That Scales w Your Domain
49mRealizing Domain Design Through Architectural Modularity ...
52mGood Fences Make Good Neighbours
47mModular Monoliths