ddd-strategic-patterns
Scope
This skill owns system-level boundary decisions — how multiple bounded contexts relate, integrate, and share infrastructure without coupling.
Identifying Bounded Contexts
A bounded context is a boundary within which a domain model is consistent and a ubiquitous language applies. Each context is deployed, developed, and migrated independently.
How to Find Boundaries
Apply these heuristics in order:
-
Different ubiquitous language — If two teams (or two features) use the same word to mean different things, that's a boundary. "User" in Identity means credentials + roles. "User" in Forum means display name + avatar. They are different models.
-
Different volatility profiles — If two areas change at different rates, for different reasons, or by different stakeholders, they belong in separate contexts. This aligns with IDesign's volatility principle — applied at the system level.
-
Different business capabilities — Authentication, billing, discussion, household management are distinct capabilities. Each gets its own context.