知识卡片

普通读书笔记卡 · 1841.h.2.b.1.a.1

旧开关复用放大事故

理解等级:高级

原书Knight案例描述:新算法只部署到部分服务器,复用的旧特征开关在未升级机器激活旧交易逻辑;回滚代码而未关闭开关又扩大影响。可迁移教训是版本不一致与残留行为会相互放大,不能仅凭代码回滚就认定系统已恢复。本卡依据书内案例,不将其简化叙述当作完整事故取证。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Building Evolvable Architectures · 查看原书依据

      A story in a popular blog called, “Knightmare: A DevOps Cautionary Tale” serves as a warning about snowflake servers. A financial services company previously had an algorithm called PowerPeg that handled trading details, but that code hadn’t been used in a number of years. However, the developers never removed the code. It resided underneath a feature toggle that remained off. Because of regulatory changes, developers

    参考来源

    - 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第07章《Building Evolvable Architectures》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch07.html;段落定位:A financial services company previously had an algorithm) - 结论依据:原文对“旧开关复用放大事故”的定义或案例,支撑“原书Knight案例描述:新算法只部署到部分服务器,复用的旧特征开关在未升级机器激活旧交易逻辑;回滚代码而未关闭开关又扩大影响”的归纳。据其上下文,可迁移教训是版本不一致与残留行为会相互放大,不能仅凭代码回滚就认定系统已恢复。 - 原始内容:A story in a popular blog called, “Knightmare: A DevOps Cautionary Tale” serves as a warning about snowflake servers. A financial services company previously had an algorithm called PowerPeg that handled trading details, but that code hadn’t been used in a number of years. However, the developers never removed the code. It resided underneath a feature toggle that remained off. Because of regulatory changes, developers