Bounded Context
Updated 2026-08-22
INTRODUCTION
English translation pending.
CORE DEFINITION
Bounded context is a central pattern in domain-driven design, introduced by Eric Evans. It states that a large system should be divided into explicit boundaries, within each of which a single model and a single ubiquitous language apply, and that the same word may carry different meanings in different contexts. The core claim is that forcing one global model on a complex domain produces contradictions, whereas explicit boundaries keep each model internally consistent. The qualification is that boundaries carry translation costs, so the pattern trades modelling clarity for mapping work between contexts.
SCAFFOLDING EFFECT
Reduce cognitive load
- Vocabulary check: ask which context a term is being used in before arguing about its meaning. - Boundary drawing: define precisely where one model stops applying and another begins. - Mapping duty: make the translation rules between adjacent contexts explicit rather than implicit.
Anchor fast decisions
A term acquires meaning from the model it belongs to, so when two teams use the same word for different things, every conversation carries a hidden translation that neither side knows is happening. Explicit boundaries surface that translation and confine each model to where it holds, so contradictions appear as boundary problems rather than as data errors. The cost is that crossing a boundary requires deliberate mapping work.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- zh.wikipedia.orghttps://zh.wikipedia.org/wiki/%E9%A2%86%E5%9F%9F%E9%A9%B1%E5%8A%A8%E8%AE%BE%E8%AE%A1verified
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.
RELATED MODELS