知识卡片
增量包含部署边界
开发时的小步修改与运行时的渐进部署是两个不同问题。前者缩小代码变更范围,后者要求模块和契约允许新旧行为共存。星级服务增加半星时,消费者逐步迁移,旧版在无人调用后退出;只把提交拆小而仍要求所有服务一起发布,不足以实现运行层面的增量。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 增量包含部署边界
原书出处 · 1 处
- Evolving Software Architecture · 查看原书依据
Incremental change describes two aspects of software architecture: how teams build software incrementally and how they deploy it. During development, an architecture that allows small, incremental changes is easier to evolve because developers have a smaller scope of change. For deployment, incremental change refers to the level of modularity and decoupling for business features and how they map to architecture. An example is in order.
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第01章《Evolving Software Architecture》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch01.html;段落定位:Incremental change describes two aspects)
- 结论依据:原文对“增量包含部署边界”的定义或案例,支撑“开发时的小步修改与运行时的渐进部署是两个不同问题”的归纳。据其上下文,前者缩小代码变更范围,后者要求模块和契约允许新旧行为共存。
- 原始内容:Incremental change describes two aspects of software architecture: how teams build software incrementally and how they deploy it. During development, an architecture that allows small, incremental changes is easier to evolve because developers have a smaller scope of change. For deployment, incremental change refers to the level of modularity and decoupling for business features and how they map to architecture. An example is in order.