知识卡片
绿色迁移以可控影响和回滚衡量
好迁移应做到影响范围可控、早期发现缺陷、进度可见且能回退;是否完全零中断并非唯一标准。规划时同时列出迁移目标、难度、客户影响和执行责任。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第9章《Code Migrations》(源文件:`_epub-src/OPS/ch09.xhtml`,归一化正文 [8341:12720))
- 结论依据:原文比较红色与绿色迁移,并提出四类权衡维度。
- 原始内容:Green migration: Considering a different universe, the code does not break all over the place, was done transparently or within a reasonable and controlled blast radius, and changes were minimal; very few bugs were spotted and often very early, few production bugs, benefits for the business were clear, visible and they had crystal clear understanding of the progress. Rollbacks? Manageable. Which one was better: red or green migration? Green migration, right?