知识卡片
部署与发布相分离
特征开关根据配置或上下文选择是否暴露新行为,使代码可以先进入生产环境,用户再按计划看到功能。简单实现可以是配置控制的条件分支,更复杂实现支持运行时切换与定向用户。开关需要有清晰管理边界,隐藏界面本身不证明功能副作用被隔离。
进一步联系:[[开关必须有退出机制]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 部署与发布相分离
原书出处 · 1 处
- Engineering Incremental Change · 查看原书依据
Another common issue with continuous deployment is business impact. Users don’t want a barrage of new features showing up on a regular basis and would rather have them staged in a more traditional way, such as in a “Big Bang” deployment. A common way to accommodate both continuous deployment and staged releases is to use feature toggles. A feature toggle is typically a condition in
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第03章《Engineering Incremental Change》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch03.html;段落定位:A feature toggle is typically a condition)
- 结论依据:原文对“部署与发布相分离”的定义或案例,支撑“特征开关根据配置或上下文选择是否暴露新行为,使代码可以先进入生产环境,用户再按计划看到功能”的归纳。据其上下文,简单实现可以是配置控制的条件分支,更复杂实现支持运行时切换与定向用户。
- 原始内容:Another common issue with continuous deployment is business impact. Users don’t want a barrage of new features showing up on a regular basis and would rather have them staged in a more traditional way, such as in a “Big Bang” deployment. A common way to accommodate both continuous deployment and staged releases is to use feature toggles. A feature toggle is typically a condition in