知识卡片
部署与发布是两个动作
部署让新代码在生产环境运行,发布才让用户请求实际触发新功能。把两者分开,可先验证环境和依赖,再按范围开放流量或功能,降低一次性切换风险。若多个服务仍需同步上线,应检查接口兼容与发布顺序。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
Deployment involves taking a feature all the way into production, because you now have a running process in your system. Although deployed, the new feature is not active or executed by interactions with the production system. There are different ways to achieve this separation and you will explore these shortly. The release involves activating the new feature in a controlled manner, allowing you to control the risk of introducing the new feature.
参考来源
- 位置:《Mastering API Architecture》第5章《Deploying and Releasing APIs》之《Separating Deployment and Release》(源文件:_epub-src/OEBPS/ch05.xhtml)
- 结论依据:原文分别定义部署为生产中存在运行进程、发布为受控激活新功能,并指出不分离会使多服务发布互相牵连。
- 原始内容:Deployment involves taking a feature all the way into production, because you now have a running process in your system. Although deployed, the new feature is not active or executed by interactions with the production system. There are different ways to achieve this separation and you will explore these shortly. The release involves activating the new feature in a controlled manner, allowing you to control the risk of introducing the new feature.