Distribu-ready with the Modular Monolith
summary
Argues the modular monolith is distribu-ready by strictly enforcing module boundaries so slices can be plucked into standalone workloads. Demonstrates with the Tacky Tacos codebase: a single Web API as the executable glue, .NET assemblies per module, extension methods to wire endpoints, compile‑time encapsulation and architecture tests, and messaging via RabbitMQ for decoupling. Introduces the KitKat pattern and the satellite pattern where modules become Azure Functions or containers; shows this conversion working and warns about accrued technical debt.
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 3:51Monoliths vs. microservices
- 4:44When to scale
- 7:51Comparing architectures
- 11:46The distributed monolith trap
- 14:13The modular monolith alternative
- 17:24Implementing the KitKat pattern
- 21:18Decomposition strategies
- 27:17Transitioning to satellite services
- 32:19Structuring a modular project
- 36:59Inter-module communication
- 42:26Advanced messaging patterns
- 50:27Enforcing architectural integrity
- 57:05Conclusion
related talks
57mDistribu-ready with the Modular Monolith
43mModular Monoliths: The Architecture That Scales w Your Domain
57mUnderstanding Microservices: a guide for the monolithic developer
01h 04mModular Monoliths and Other Facepalms
01h 14mUnderstanding Microservices: A Guide For the Monolithic Developer
56mModular Monolith and the Prisoner of Microdisservices
02mOmphile Matheolane at DDD Europe 2025
51mModularization: Foundation of Microservices and Monoliths
