知识卡片
双生命周期会叠加成本
并行使用持久与临时测试阶段,原意是让持久阶段快速反馈、临时阶段提供干净结果。但更新不可靠仍要人工修持久栈,发布时通常还得等较慢阶段,可能把两者缺点叠在一起。可作为改善可靠性的过渡,或验证长期运行风险,但不应视为自动消除取舍。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 实现基础设施代码测试 · 查看原书依据
In practice, using both types of stack lifecycles often combines the disadvantages of both. If updating an existing stack is unreliable, your team will still spend time manually fixing that stage when it goes wrong. And you probably wait until the slower stage passes before
参考来源
- 位置:《Infrastructure As Code》第18章《实现基础设施代码测试》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch18.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“并行使用持久与临时测试阶段,原意是让持久阶段快速反馈、临时阶段提供干净结果”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:In practice, using both types of stack lifecycles often combines the disadvantages of both. If updating an existing stack is unreliable, your team will still spend time manually fixing that stage when it goes wrong. And you probably wait until the slower stage passes before