← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1980.z.7.d

持续交付与部署的区别

理解等级:中级

CI自动集成、构建和验证,产出可部署版本。持续交付保持版本可随时部署,但上线仍由人触发;持续部署把通过验证的版本自动上线。状态服务的重建和下游输出使自动上线更复杂,需将schema、权限、恢复与SLA纳入条件,不能只因构建成功就判定安全。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Deploying Event-Driven Microservices · 查看原书依据

      Continuous delivery is the practice of keeping your codebase deployable. Microservices that adhere to continuous delivery principles use a CI pipeline to validate that the build is ready for deployment. The deployment itself is not automated, however, and requires some manual intervention on the service owner’s part.

    参考来源

    - 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第16章《Deploying Event-Driven Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch16.xhtml;规范化段落起句:Continuous delivery is the practice) - 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:CI自动集成、构建和验证,产出可部署版本。本卡同时保留其适用条件与失败边界。 - 原始内容:Continuous delivery is the practice of keeping your codebase deployable. Microservices that adhere to continuous delivery principles use a CI pipeline to validate that the build is ready for deployment. The deployment itself is not automated, however, and requires some manual intervention on the service owner’s part.