contextmaps

Context maps are a technique used in domain-driven design to map the relationships and integration semantics between bounded contexts within a software system. A bounded context encapsulates a model and language; the context map documents how those contexts connect, communicate, and influence one another.

A context map typically includes the set of bounded contexts, the nature of their relationships, and the integration patterns used to connect them. Common patterns include Shared Kernel (two teams share a small common model), Customer-Supplier (one context drives requirements for another), Conformist (one context follows another's model with little collaboration), Anti-Corruption Layer (ACL) to translate between incompatible models, Open Host Service (exposing services that others can use), and Published Language (shared, canonical language across contexts).

Context maps are used by teams to guide collaboration, governance, and incremental integration. They are usually developed collaboratively with domain experts and engineers, and kept as a living artifact that evolves as the domain and architecture change. Creating a map involves identifying bounded contexts, clarifying their ownership, selecting integration patterns, and documenting any linguistic or technical constraints.

Benefits include improved clarity of responsibilities, reduced coupling, and better risk management during migrations. Limitations include the potential for outdated maps if kept static, and the risk of overcomplicating the architecture with excessive patterns. When used well, context maps complement other DDD tools such as ubiquitous language and domain models.