Context Mapping
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
A technique from domain-driven design for making the relationships between bounded contexts explicit, identifying which context is upstream and which is downstream and specifying how concepts translate across the boundary. Its core proposition is that the complexity of a large system comes mainly from ambiguous boundaries and implicit coupling rather than from the internals of any module, so making the relationships explicit converts unmanaged entanglement into manageable interfaces. The qualifier is that the map must be maintained.
SCAFFOLDING EFFECT
Reduce cognitive load
- Boundary drawing: identify the independent models, teams, or responsibilities inside the system. - Direction marking: label each relationship as upstream or downstream so change impact is visible. - Translation layer: define how concepts map at the boundary to prevent meaning leaking between contexts.
Anchor fast decisions
Each bounded context carries its own language and model, so a concept crossing a boundary without translation arrives with the wrong meaning. Naming the direction of dependency and inserting a translation layer makes the interaction explicit, which means a change on one side can be assessed against a known contract instead of discovered through breakage.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Domain-driven_designverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.