DataTerminology.comNEW
A boundary within which a specific domain model and ubiquitous language are consistently defined and applied.
DESCRIPTION
In Domain-Driven Design, a bounded context sets clear limits around where a particular model and language hold true. It prevents ambiguity and model corruption across complex domains by aligning teams and services around cohesive responsibilities. Context maps describe relationships and integration patterns between bounded contexts, such as anti-corruption layers. The pattern aligns naturally with microservices and modular architectures. Establishing precise boundaries improves autonomy, clarity, and evolvability in large systems.
ALTERNATIVE DEFINITIONS
Eric Evans DDD Reference
A description of a boundary (typically a subsystem, or the work of a particular team) within which a particular model is defined and applicable.
Authoritative definition from the originator of DDD, emphasizing applicability and team boundaries.
Martin Fowler
Bounded Context is a central pattern in Domain-Driven Design. It draws a boundary around a particular domain model.
Highlights centrality in DDD and the purpose of isolating models.
Wikipedia
A bounded context is a description of a boundary within which a particular domain model is applicable.
Concise encyclopedic phrasing consistent with DDD literature.
RELATED TERMS
Domain-Driven Design Ubiquitous Language Context Map Anti-Corruption Layer Microservices Subdomain Aggregate Context Mapping Team Topologies Canonical Data Model
COMPETING TERMS
Enterprise Canonical Data Model
RELATIONS
- Broader: Context
KNOWLEDGE AREAS
Software Modeling Data Architecture Domain & Business Context Data Modeling Collaboration
TARGET AUDIENCE
Software Architect Solution Architect Data Architect Product Owner Business Analyst Enterprise Architect
EXTERNAL SOURCES
- Wikipedia - Domain-driven design
- Eric Evans - Official DDD pattern definitions
- Martin Fowler - Explanation and guidance on bounded contexts
- Greg Young - DDD talk on boundaries and models
TOP QUESTIONS
Why are bounded contexts important in large systems?
They prevent model ambiguity and coupling across teams, enabling independent evolution and clearer communication via a shared ubiquitous language.
Category: Relevancy
How do bounded contexts relate to microservices?
They align naturally; each microservice can implement a single bounded context to preserve model integrity and autonomy.
Category: Architecture
What is a context map?
A context map documents relationships and integration patterns between bounded contexts, such as shared kernels and anti-corruption layers.
Category: Concepts
How do I identify a bounded context?
Look for cohesive language and responsibilities, organizational team boundaries, and transactional consistency requirements.
Category: BestPractices
What is a common mistake with bounded contexts?
Creating boundaries that mirror technical layers instead of domain splits often leads to poor alignment and coupling.
Category: Mistakes
How do bounded contexts affect data modeling?
Each context owns its schema and model; mappings are explicit at integration boundaries to avoid leakage.
Category: DataModeling
Can bounded contexts share a database?
It’s possible but risky; prefer separate schemas or databases with integration via APIs or events to preserve autonomy.
Category: Risk
What is an anti-corruption layer?
A translation layer between contexts that protects a model from external concepts and prevents semantic pollution.
Category: Concepts
How do bounded contexts evolve over time?
They may split or merge as domain understanding changes; keep context maps updated to reflect new boundaries.
Category: Evolution