知识卡片

普通读书笔记卡 · 3418

迁移后核对并删除旧代码

理解等级:高级

迁移不是新路径上线就结束。应跟踪旧入口调用量、错误与延迟,核对新旧结果,完成消费者迁移后退役旧代码;否则遗留路径使系统更复杂。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    原书出处

    参考来源

    - 位置:《Principles of Software Architecture Modernization》第9章《Code Migrations》(源文件:`_epub-src/OPS/ch09.xhtml`,归一化正文 [46522:50728)) - 结论依据:原文把未删除旧代码列为迁移摩擦和熵的重要来源,并提出观测、验证和退役。 - 原始内容:Do not skip decommissioning phase: Consider having a plan and strategy to decommission components, if you just add software and do not delete it, your problem just gets bigger and worse. Product mindset: Make engineering have a product mindset: Understand that speed, bugs, reliability, and availability are part of the customer experience, and engineers are also doing product work.