知识卡片
退役前保存恢复材料并清理死代码
确认无人依赖旧系统后,先通知、备份并归档旧代码和数据,再关闭服务、删除消费者死代码与多余配置。只停服务器而保留旧调用路径会继续制造维护负担。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第10章《Data Migrations》(源文件:`_epub-src/OPS/ch10.xhtml`,归一化正文 [59013:63224))
- 结论依据:原文列出退役沟通、验证停服、代码归档、完整备份和删除消费者代码。
- 原始内容:Full data backup: Do not just shut down the servers and throw away the data; fully backup the old data and archive it in S3 / Glacier 119 . Delete consumer code: Do not leave behind dead code; decommission consumer code by deleting code and cleaning up dependencies. Cleaning up code and data is probably one of the most underperformed activities in our industry. People do not delete code, and this is wrong.