知识卡片
单一代码基线支持多环境发布
一个服务以明确的版本控制代码基线生成多个环境的发布,避免每个环境各自维护一份代码。共享功能宜成为有版本的依赖,减少服务边界被共享代码模糊。原书把此作为十二要素原则解释;它强调可追溯来源,不应把“一个代码基线”机械理解为所有组织必须使用相同仓库布局。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- It’s All About Dependability · 查看原书依据
For any given service, there should be exactly one codebase that is used to produce any number of immutable releases for multiple deployments to multiple environments. This is typically a production site, and one or more staging and development sites. Having multiple services that sharing the same code tends to lead to a blurring of
参考来源
- 位置:《Cloud Native Go》第06章《It’s All About Dependability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch06.xhtml)
- 结论依据:一个服务以明确的版本控制代码基线生成多个环境的发布,避免每个环境各自维护一份代码。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:For any given service, there should be exactly one codebase that is used to produce any number of immutable releases for multiple deployments to multiple environments. This is typically a production site, and one or more staging and development sites. Having multiple services that sharing the same code tends to lead to a blurring of