Dissecting Bounded Contexts -
summary
Argues that bounded contexts have 50+ measurable attributes (language, business differentiation, technical complexity, team topology) and proposes treating them like a bounded context genome to identify repeatable patterns (octopus, bubble, gateway, interchange). Uses a business-differentiation vs complexity axis to name patterns such as decisive core and first-to-market cores, cites Slack as a generic→core surprise, recommends Team Topologies and dynamic reteaming, and pushes for living documentation plus cost/benefit metrics (serverless) to drive design decisions.
AI-written summary · about
chapters (10)
- 0:00Introduction and motivation
- 2:15Why modular systems matter
- 4:50Language and boundaries
- 11:54Bounded contexts and business models
- 16:49Core domain patterns
- 21:46Team architecture alignment
- 33:07Team topologies and collaboration
- 36:19Bounded context DNA
- 43:58Porous boundaries and patterns
- 44:41Future of domain-driven design
related talks
55mCharting the uncharted: Discovering and evolving bounded contexts
47mBounded Contexts: Team Topologies and Architecture boundaries aligned
42mBounded Context: Keep It Simple!
42mBounded Context — How to Modularize a System in a Few Steps
01mPrem Chandrasekaran at DDD Europe 2025
45mSystems Thinking by combining Team Topologies with Context Maps
39mFrom Domain Boundaries to Software Architecture
01mMike Wojtyna's Lightning talk about Domain Archetypes at DDD Europe