知识卡片
代码定义的三种收益
把资源定义成代码带来可复用、一致与可见三种收益:同一定义可重建多个实例,重复构建降低不可解释差异,公开代码支持审查、审计与故障分析。只有实际从代码构建和更新,才能兑现这些收益;单纯保留一份与运行环境脱节的脚本并不足够。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 什么是基础设施即代码 · 查看原书依据
Defining everything “as code” is a core practice for making changes rapidly and reliably. There are a few reasons that this helps: Reusability If we define a thing as code, we can create many instances of it. We can repair and rebuild things quickly, and other people can build identical instances of the thing. Consistency
参考来源
- 位置:《Infrastructure As Code》第1章《什么是基础设施即代码》(来源项目 book-sources,源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch01.html)
- 结论依据:原文对该概念的定义、应用条件与作用机制直接支持上述解释。
- 原始内容:Defining everything “as code” is a core practice for making changes rapidly and reliably. There are a few reasons that this helps: Reusability If we define a thing as code, we can create many instances of it. We can repair and rebuild things quickly, and other people can build identical instances of the thing. Consistency