Bounded Context: Keep It Simple!
summary
Explains what bounded contexts are, how they relate to microservices, and why having clear boundaries (fewer unnecessary fences) reduces overall complexity. Covers patterns and practical recommendations for working with bounded contexts, and emphasizes the importance of a ubiquitous language; examples come from developing the Dodo IS system.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:16Speaker background
- 5:10Monolith problems
- 6:38DDD to reduce complexity
- 12:17Universal model problems
- 18:24Bounded context
- 19:51Finding context boundaries
- 24:14Event storming practice
- 30:15Bounded context canvas
- 32:30Evolving context boundaries
- 35:15Bounded context and microservices
- 37:27Modular monolith
- 38:30Bounded context benefits
- 40:39Garden metaphor
- 41:27Q&A
related talks
51mDissecting Bounded Contexts -
42mBounded Context — How to Modularize a System in a Few Steps
49mDDD & Microservices: At Last, Some Boundaries!
55mCharting the uncharted: Discovering and evolving bounded contexts
01h 00mPrinciples for Building MicroServices
47mBounded Contexts: Team Topologies and Architecture boundaries aligned
02mOmphile Matheolane at DDD Europe 2025
38mMicroservices, a bittersweet symphony
