知识卡片

普通读书笔记卡 · 1841.h.2.c.4

可逆决策缩小失败代价

理解等级:高级

蓝绿部署保留两套可切换环境,特征开关和服务路由允许局部撤回新行为,从而降低试错成本。可逆性必须基于真实状态:代码可以切回,不代表数据库或外部副作用也能自动逆转。设计时应单独明确每类变化的恢复路径。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Building Evolvable Architectures · 查看原书依据

      Many DevOps practices exist to allow reversible decisions—decisions that need to be undone. For example blue/green deployments, where operations have two identical (probably virtual) ecosystems—blue ones and green ones—are common in DevOps. If the current production system is running on blue, green is the staging area for the next release. When the green release is ready, it becomes the production system and blue temporarily shifts

    参考来源

    - 位置:《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;段落定位:If something goes awry with green) - 结论依据:原文对“可逆决策缩小失败代价”的定义或案例,支撑“蓝绿部署保留两套可切换环境,特征开关和服务路由允许局部撤回新行为,从而降低试错成本”的归纳。据其上下文,可逆性必须基于真实状态:代码可以切回,不代表数据库或外部副作用也能自动逆转。 - 原始内容:Many DevOps practices exist to allow reversible decisions—decisions that need to be undone. For example blue/green deployments, where operations have two identical (probably virtual) ecosystems—blue ones and green ones—are common in DevOps. If the current production system is running on blue, green is the staging area for the next release. When the green release is ready, it becomes the production system and blue temporarily shifts