Context mapping
A collection of patterns and resources to visualize relationships between bounded contexts and teams in Domain-Driven Design.
What is Context mapping?
Context Mapping is a visual modeling technique from Domain-Driven Design that helps architects and teams map the relationships between bounded contexts (distinct parts of a domain model) and the teams responsible for them. It provides a collection of nine patterns and three team relationships to analyze dependencies, integration strategies, and organizational boundaries in complex software systems. The project offers practical resources like cheat sheets and Miro starter kits to lower the barrier to applying these concepts effectively.
Software architects, technical leads, and development teams practicing or adopting Domain-Driven Design who need to visualize and communicate complex system boundaries and team interactions. It's particularly valuable for organizations undergoing digital transformation or dealing with microservices and distributed systems.
It distills abstract DDD concepts into actionable, visual patterns with ready-to-use collaboration templates, reducing the learning curve for teams. Unlike generic diagramming tools, it provides a structured vocabulary specifically designed for analyzing sociotechnical architecture, making it easier to identify integration risks and alignment opportunities.
Overview
Context Mapping is a technique from Domain-Driven Design (DDD) that helps visualize the relationships between bounded contexts and the teams that own them. It provides a structured way to analyze existing systems or plan new architectures by mapping out dependencies, governance, and model propagation. This repository offers practical resources to make context mapping more accessible, including a cheat sheet and a starter kit for collaborative tools like Miro.
Key Features
- Nine Context Map Patterns — Includes Open-host Service, Conformist, Anticorruption Layer, Shared Kernel, Partnership, Customer/Supplier Development, Published Language, Separate Ways, and Big Ball of Mud to describe various integration and governance scenarios.
- Three Team Relationships — Defines Mutually Dependent, Upstream/Downstream, and Free relationships to clarify organizational and technical dependencies.
- Practical Starter Kit — Provides a pre-built Miro board with all pattern objects and examples to kickstart remote collaboration sessions.
- Context Map Cheat Sheet — A quick-reference guide summarizing all patterns and relationships for easy consultation during design workshops.
- Best Practices Guidance — Recommends using small, focused context maps for specific questions rather than creating overwhelming monolithic diagrams.
Philosophy
Context Mapping aims to make complex sociotechnical architectures understandable by providing a shared visual language that bridges technical models and team dynamics, emphasizing clarity and targeted communication over completeness.
Related Projects
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
