Prem Chandrasekaran at DDD Europe 2025
summary
Compares three decomposition patterns: one-to-one mapping where a subdomain neatly matches a bounded context, multiple bounded contexts when a subdomain splits into contexts of different sizes, and an enveloping context that contains several subdomains. Recommends choosing the pattern that minimizes coupling and clarifies data ownership by measuring shared invariants, error blast radius, team size and rate of change. Flags an enveloping context as a likely smell and favors explicit APIs/events and clear ownership when responsibilities or velocities diverge.
AI-written summary · about
related talks
47mBounded Contexts: Team Topologies and Architecture boundaries aligned
51mDissecting Bounded Contexts -
01h 00mFrom Domain Driven Design DDD to Delivery
42mBounded Context — How to Modularize a System in a Few Steps
48mDomain Pattern – How the Domain Influences the Architecture
45mUsing DDD To Decompose Your Monolith
39mFrom Domain Boundaries to Software Architecture
44mStrategic Domain-Driven Design for dummies