知识卡片
外部依赖使用拉取边界
将第三方组件置于受控内部仓库,把外界更新视为待审核变更,再通过构建与冒烟验证引入。这样上游删除或破坏性更新不直接改变已有构建基础。收益是稳定与可重复,代价是额外维护;还需主动处理安全更新,不能永久冻结版本。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Building Evolvable Architectures · 查看原书依据
We recommend that developers take a more proactive approach to dependency management. A good start on dependency management models external dependencies using a pull model. For example, set up an internal version-control repository to act as a third-party component store, and treat changes from the outside world as pull requests to that repository. If a beneficial change occurs, allow it into the ecosystem. However, if
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第07章《Building Evolvable Architectures》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch07.html;段落定位:treat changes from the outside world as pull requests)
- 结论依据:原文对“外部依赖使用拉取边界”的定义或案例,支撑“将第三方组件置于受控内部仓库,把外界更新视为待审核变更,再通过构建与冒烟验证引入”的归纳。据其上下文,这样上游删除或破坏性更新不直接改变已有构建基础。
- 原始内容:We recommend that developers take a more proactive approach to dependency management. A good start on dependency management models external dependencies using a pull model. For example, set up an internal version-control repository to act as a third-party component store, and treat changes from the outside world as pull requests to that repository. If a beneficial change occurs, allow it into the ecosystem. However, if