知识卡片
扩展收缩提供过渡状态
扩展—收缩先增加新表达并保留旧表达,允许新旧消费者共存;待依赖完成迁移后再去掉旧结构。过渡期解决版本推进不同步的问题,也增加双份数据同步与清理责任。结束条件应由真实依赖消失的证据决定,而不只是预定日期。
结构图:
flowchart LR
A[仅旧结构] --> B[增加新结构]
B --> C[兼容期与同步]
C --> D[消费者逐步迁移]
D --> E[核实旧依赖消失]
E --> F[删除旧结构]
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Evolutionary Data · 查看原书依据
Using this pattern, developers have a starting state and an ending state, maintaining both the old and new states during the transition. This transition state allows for backward compatibility and also gives other systems in the enterprise enough time to catch up with the change. For some organizations, the transition state can last from a few days to months.
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第06章《Evolutionary Data》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch06.html;段落定位:Using this pattern, developers have a starting state)
- 结论依据:原文对“扩展收缩提供过渡状态”的定义或案例,支撑“扩展—收缩先增加新表达并保留旧表达,允许新旧消费者共存;待依赖完成迁移后再去掉旧结构”的归纳。据其上下文,过渡期解决版本推进不同步的问题,也增加双份数据同步与清理责任。
- 原始内容:Using this pattern, developers have a starting state and an ending state, maintaining both the old and new states during the transition. This transition state allows for backward compatibility and also gives other systems in the enterprise enough time to catch up with the change. For some organizations, the transition state can last from a few days to months.