知识卡片
限界上下文按实际使用划定
原书的货运预订教学例子里,预订应用消费新模型,模型团队控制的持久化模式也由该模型驱动,二者属于预订上下文。遗留货物跟踪系统另有模型,位于边界外;跨界翻译由遗留维护团队负责。航程排班团队虽然原本打算与预订共享系统,却只作松散协调,现实中并不处于同一上下文。
划界应先画项目现状,再决定如何改进协作。排班和预订团队在关系明确、过程建立前应谨慎共享代码或数据。
结构图:
flowchart LR
subgraph B[预订上下文]
M[预订模型]
A[预订应用]
DB[模型驱动的数据库模式]
M --> A
M --> DB
end
B --> T[边界翻译]
T --> L[遗留跟踪系统]
B -.关系待定义.-> S[航程排班上下文]
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第14章|B OUNDED C ONTEXTS Are Not M ODULES · 查看原书依据
This BOUNDED CONTEXT is made up of all those aspects of the system that are driven by this particular model: the model objects, the database schema that persists the model objects, and the booking application. Two teams work primarily in this CONTEXT: the modeling team and the application team.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第101章《BOUNDED CONTEXTS Are Not MODULES》(源文件:_epub-src/0321125215_ch14lev1sec1_split_001.html;单元01)
- 结论依据:原文逐一确定预订应用、模型驱动的数据库模式、遗留跟踪和航程排班的实际边界,并提醒先认清现状。
- 原始内容:This BOUNDED CONTEXT is made up of all those aspects of the system that are driven by this particular model: the model objects, the database schema that persists the model objects, and the booking application. Two teams work primarily in this CONTEXT : the modeling team and the application team.