知识卡片
开发运行共同负责服务结果
当开发只被功能速度激励、运维只承担稳定责任时,交接容易形成冲突。基础设施代码化与容器等抽象让两方的工作更加接近,要求设计者、实现者和维护者共同对可依赖性负责。工具可支持协作,却不自动消除责任与激励的断层。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- It’s All About Dependability · 查看原书依据
the rapid production of dependable, high-quality services is a fully collaborative effort of all of its designers, implementors, and maintainers. Achieving Dependability This is where the rubber meets the road. If you’ve made it this far, congratulations. So far we’ve discussed Laprie’s definition of “dependability”, which can be (very) loosely paraphrased as “happy users”, and
参考来源
- 位置:《Cloud Native Go》第06章《It’s All About Dependability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch06.xhtml)
- 结论依据:当开发只被功能速度激励、运维只承担稳定责任时,交接容易形成冲突。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:the rapid production of dependable, high-quality services is a fully collaborative effort of all of its designers, implementors, and maintainers. Achieving Dependability This is where the rubber meets the road. If you’ve made it this far, congratulations. So far we’ve discussed Laprie’s definition of “dependability”, which can be (very) loosely paraphrased as “happy users”, and