知识卡片
部署可行性反向约束上下文边界
边界策略还决定发布协作:客户/供应商团队要共同测试可配套的版本,代码与数据迁移也需兼容;共享内核的部署协调负担更重。通过翻译层连接时,一侧可升级翻译实现而保持对另一侧的接口稳定。
因此画边界时要检查版本共存、数据迁移与发布顺序,不能只按概念模型漂亮与否决定。原书提出把复杂翻译层集中在单一进程可能减少多版本并存,是条件性设计建议,并非实际部署测量。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第14章|Choosing Your Model Context Strategy · 查看原书依据
Even deployment of the components of a single BOUNDED CONTEXT can be challenging when data migration takes time or when distributed systems can't be updated instantaneously, resulting in two versions of the code and data coexisting.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第114章《Choosing Your Model Context Strategy》(源文件:_epub-src/0321125215_ch14lev1sec13.html;单元04)
- 结论依据:原文说明不同上下文关系对应不同版本协调、数据迁移和翻译层部署负担,要求部署可行性反馈到边界选择。
- 原始内容:The choice of BOUNDED CONTEXT strategy has an impact on the deployment. For example, when CUSTOMER/SUPPLIER TEAMS deploy new versions, they have to coordinate with each other to release versions that have been tested together. Both code and data migrations have to work in these combinations. In a distributed system, it may help to keep the translation layers between CONTEXTS together within a single process, so that you don't have multiple versions coexisting. Even deployment of the components of a single BOUNDED CONTEXT can be challenging when data migration takes time or when distributed systems can't be updated instantaneously, resulting in two versions of the code and data coexisting. [...] The feasibility of a deployment plan should feed back into the drawing of the CONTEXT boundaries. When two CONTEXTS are bridged by a translation layer, one CONTEXT can be updated just so a new translation layer provides the same interface to the other CONTEXT. A SHARED KERNEL imposes a much greater burden of coordination, not just in development but also in deployment.
- 转录说明:`[...]` 标明部署环境与技术因素的中间说明省略;原 EPUB 强调标签边界造成的术语前空格已规范转录。