Loading content
A Bounded Context defines explicit boundaries within a domain model where terms, rules, and interfaces remain consistent. It prevents semantic drift across teams, enables autonomous development and integration, and provides the conceptual basis for clear context boundaries in distributed systems and microservice-based architectures. Clear boundaries also sup…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
A bounded context is an explicitly named boundary within which a domain model and its terms have one unambiguous meaning. The same words may mean something different outside that boundary.
Eric Evans introduced the bounded context in his 2004 work on Domain-Driven Design. It addressed complex software systems where one enterprise-wide model became unmanageable because terms and rules conflicted.
Imagine a map made up of several countries. Each country has its own language, rules, and coherent model. Translation happens explicitly at the border: a “customer” in sales may be a different object with different data in billing. The boundary therefore shapes the model, code, and ownership, while relationships with other contexts are designed deliberately.
Domain experts and developers use the same precise vocabulary within the context.
The boundary defines where terms, rules, and data structures are valid together.
It describes relationships, dependencies, and translations among multiple contexts.
An accountable team can evolve its context's model and interfaces independently.
Bounded contexts help split large domains, clarify team boundaries, and shape microservices around coherent business models. Too many small contexts create integration overhead; overly broad boundaries couple conflicting models again. Language and domain rules should drive the cut.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.