Charting the uncharted: Discovering and evolving bounded contexts
summary
Argues that bounded context boundaries are often an art not a science and that real progress comes from specific practices: forge a ubiquitous language, draw and keep a context map, and use an anti‑corruption layer or Open Host Service for translations. Shows failures like a 275‑attribute “party” model, ambiguous order status (14‑day return vs shipped vs paid), and 10 episode scenarios; recommends one context one team, contract testing (Pact), collapsing transaction boundaries where atomicity matters, and isolating core domains (churn engine) to regain speed and reduce risk.
AI-written summary · about
chapters (11)
- 0:00Introduction to DDD
- 1:44Demystifying domains and contexts
- 9:57Bounded contexts in retail
- 14:12Lost in Translation episode 1
- 20:57Customer chameleon episode 2
- 27:20Dictionary dictatorship episode 3
- 36:20Monolith Maximus episode 4
- 41:17Layer cake illusion episode 5
- 45:53Swarm of nano-services episode 6
- 51:17Core domain isolation episode 7
- 54:48Summary and Q&A
related talks
51mDissecting Bounded Contexts -
47mBounded Contexts: Team Topologies and Architecture boundaries aligned
01h 01mBounded Contexts: Manage the Understandability of Your Systems
42mBounded Context — How to Modularize a System in a Few Steps
42mA different take on (context) mapping -
42mBounded Context: Keep It Simple!
48mGrowing & Thriving in a Multi-model World
54mFrom Domain Boundaries to Software Architecture