知识卡片

结构图卡 · 3289.a

绞杀迁移逐步替代

理解等级:高级

绞杀模式用新上下文接收新需求,逐步迁走旧功能,旧上下文除紧急修复外停止演进。薄门面按迁移状态分发请求,迁完后移除旧系统和门面。过渡期为避免复杂集成,可暂时共享数据库,但前提是旧实现确实会尽早退休、最终数据库只归新实现;临时例外不能变成永久双重所有权。

结构图:

flowchart LR
 A[调用方] --> F[临时门面]
 F -->|未迁功能| L[旧上下文]
 F -->|已迁功能| N[新上下文]
 L --> D[过渡共享数据]
 N --> D
这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 现实中的领域驱动设计 · 查看原书依据

      The strangler migration pattern is based on the same growth dynamic as the tree the pattern is named after. The idea is to create a new bounded context—the strangler—use it to implement new requirements, and gradually migrate the legacy context’s functionality into it. At the same time, except for hotfixes and other emergencies, the evolution

    参考来源

    - 位置:《Learning Domain-Driven Design》第13章《现实中的领域驱动设计》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch13.html) - 结论依据:原文描述新旧上下文、门面路由、旧开发冻结以及共享数据库例外的退出条件。 - 原始内容:The strangler migration pattern is based on the same growth dynamic as the tree the pattern is named after. The idea is to create a new bounded context—the strangler—use it to implement new requirements, and gradually migrate the legacy context’s functionality into it. At the same time, except for hotfixes and other emergencies, the evolution