Bounded Contexts: Manage the Understandability of Your Systems
summary
Argues that splitting by semantics — explicit bounded contexts — reduces cognitive load more than copying organizational or technical boundaries; shows a warehouse where extracting an efficiency bounded context (central resource manager for expedites, staff, locations) replaces scattered logic and enables global prioritization instead of brittle local hacks. Shows a biotech monolith refactored into a liquid-transfers abstraction, a robot/hardware boundary and separate quality-control and planning/execution contexts, which cuts branching, fixes a nightly “on fire” system and makes workflows testable and maintainable.
AI-written summary · about
chapters (8)
- 0:00Bounded contexts intro
- 3:36Why systems become hard to understand over time
- 16:39Bounded contexts as boundaries
- 22:56Biotech workflow example
- 39:44Designing workflow boundaries
- 50:02Refactoring for understandability
- 54:33Convincing stakeholders
- 59:51Q&A
related talks
55mCharting the uncharted: Discovering and evolving bounded contexts
56mAligning Bounded Contexts with Subdomains in Legacy Code
48mGrowing & Thriving in a Multi-model World
41mUsing Boundary-Driven Development to beat code complexity
36mBuilding Beautiful Systems with ...
46mBoundaries
59mGood Fences Make Good Neighbors
43mGood Fences Make Good Neighbours