此卡片不在当前主题的阅读序列中,可返回主题继续阅读。
知识卡片
为持续变更而设计
基础设施从投入使用到退役都要面对功能、容量、漏洞、升级和诊断变更。把“建好后不动”当作稳定目标,会让系统积压补丁和已知问题。设计的可靠标准应包括能否快速修复、恢复和安全部署,而非单纯限制变更次数。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 什么是基础设施即代码 · 查看原书依据
In reality, few systems stop changing before they are retired. Some people assume that a fast pace of change is temporary. Others create heavyweight change-request processes designed to discourage people from asking for changes. However, high-performing teams handle a continual stream of changes quickly and effectively. Consider these common examples of infrastructure changes: An essential
参考来源
- 位置:《Infrastructure As Code》第1章《什么是基础设施即代码》(来源项目 book-sources,源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch01.html)
- 结论依据:原文对该概念的定义、应用条件与作用机制直接支持上述解释。
- 原始内容:In reality, few systems stop changing before they are retired. Some people assume that a fast pace of change is temporary. Others create heavyweight change-request processes designed to discourage people from asking for changes. However, high-performing teams handle a continual stream of changes quickly and effectively. Consider these common examples of infrastructure changes: An essential