知识卡片
上下文也是交付边界
限界上下文不只划分词义,也应形成独立实施、演进和版本化的服务或项目边界。边界内多个子域可以由包、模块或命名空间作逻辑隔离。这样不同上下文可以按需要选用技术栈,但仍须通过明确契约协作,独立演进不意味着完全没有依赖。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 管理领域复杂度 · 查看原书依据
Bounded contexts serve not only as model boundaries but also as physical boundaries of the systems implementing them. Each bounded context should be implemented as an individual service/project, meaning it is implemented, evolved, and versioned independently of other bounded contexts. Clear physical boundaries between bounded contexts allow us to implement each bounded context with the
参考来源
- 位置:《Learning Domain-Driven Design》第3章《管理领域复杂度》(来源项目:book-sources;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch03.html)
- 结论依据:原文对该概念的定义、应用条件及相邻概念的比较支撑本卡解释。
- 原始内容:Bounded contexts serve not only as model boundaries but also as physical boundaries of the systems implementing them. Each bounded context should be implemented as an individual service/project, meaning it is implemented, evolved, and versioned independently of other bounded contexts. Clear physical boundaries between bounded contexts allow us to implement each bounded context with the