Modular Monoliths: The Architecture That Scales w Your Domain
summary
Argues that a single deployable modular monolith scales with the domain by using DDD: explicit bounded contexts, aggregates as transactional roots, and in-memory domain events collected at commit and dispatched to decouple modules. Shows file layouts, simple code for aggregate roots and event handlers, and promotes customer–supplier and anti‑corruption layers for clean contracts. Claims faster delivery and lower ops overhead than premature microservices, and recommends shared, versioned utilities for cross‑module needs.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 2:02Why monoliths get a bad rap
- 7:26Modular monoliths vs big ball of mud
- 9:32What is a modular monolith
- 11:40Domain Driven Design basics
- 12:46Bounded contexts explained
- 14:13Code structure for modularity
- 15:56Aggregates and transactional boundaries
- 19:29Domain events for module communication
- 22:36Context maps and module interactions
- 24:42Effective context map patterns
- 29:59Shared utilities in modular monoliths
- 32:08Recap of key concepts
- 33:54Modular monolith vs microservices trade-offs
- 39:09Key takeaways and conclusion
related talks
59mMajestic Modular Monoliths
02h 29mPractical advice for building glorious monoliths
53mCrafting a self-documenting Modular Monolith with DDD principles (theory not included)
01h 01mModular Monolith Instead of Microservices: How, When and Why
45mOnce Upon a Time... Modular Monolith: The Quest for the Perfect Architecture
01h 04mModular Monoliths and Other Facepalms
50mMajestic Modular Monoliths
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development