Bounded Context¶

A model is only valid within an explicit boundary; different contexts may have different models for the same real-world concept, and that's acceptable

Tension Addressed¶

Consistency vs. Autonomy

Recognizable As¶

"Customer" meaning different things in billing vs. support; explicit translation between systems; teams owning their own data models; avoiding enterprise-wide canonical models; context maps showing relationships

Canonical Sources¶

Evans, "Domain-Driven Design" (2003)

Transfers To¶

Linguistics (semantic fields), Organizational Design (team boundaries), Legal Systems (jurisdictions), Database Federation (schema heterogeneity)

Sub-concepts: - Ubiquitous Language: Consistent terminology within a bounded context - Context Mapping: Explicit definition of relationships between contexts - Anti-Corruption Layer: Translation boundary protecting one model from another