Bounded Context

A bounded context is a concept from Domain-Driven Design that establishes boundary within a domain and contains models related to that context. The concepts, entities, value objects, and aggregates within the bounded context are written using a ubiquitous language. This language is also used in things such as documentation for the project and spoken throughout meetings on the project.

A domain may have multiple bounded contexts within its environment. Each bounded context may be maintained by a team. Context Mapping is used to help explain the relationships between two bounded contexts as well as indicate the relationship needed between the teams that maintain those two contexts.

eCommerce example of bounded contexts Permalink for this section

This is an example of a context map showing bounded contexts that may be in an eCommerce system and how they interact.

The bounded contexts include:

• Catalog
• Content Management
• Customer
• Fraud Detection
• Inventory Management
• Marketing
• Order
• Product Recommendation

Upstream/Downstream

Partnership

Nonrelated

Catalog

Order

Customer

Content Management

Product Recommendation

Marketing

Fraud Detection

Inventory Management

References Permalink for this section

• Domain analysis for microservices - Azure Architecture Center
• Martin Fowler’s Bliki: BoundedContext
• Bounded Contexts - Eric Evans - DDD Europe 2020
• DDD Reference - Domain Language

Learn More Permalink for this section

• On-Demand Webinar: Intro to Domain-Driven Design with C#
• Email Course: Intro to DDD

[Anti-Corruption Layer](/content/domain-driven-design/anti-corruption-layer/ "Anti-Corruption Layer"/index.html) [Context Mapping](/content/domain-driven-design/context-mapping/ "Context Mapping"/index.html)