You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2021. It is now read-only.
Christopher Bennage edited this page Jan 30, 2015
·
1 revision
Bounded Context
A Bounded Context can be considered as a miniature application, containing it’s own Domain, own code and persistence mechanisms. Each BC has also its own MODEL and it could be based on a specific data-source (database, etc.).
Each BC may have its own Ubiquitous language, or dialect of the Ubiquitous language used for the system.
A description of a boundary (typically a subsystem, or the work of a particular team) within which a particular model is defined and applicable. - Eric Evans
The delimited applicability of a particular model. BOUNDING CONTEXTS gives team members a clear and shared understanding of what has to be consistent and what can develop independently.
Pasted from http://domaindrivendesign.org/resources/ddd_terms