知识卡片
部署检验架构决定
架构方案在生产中的效果及到达生产的可行性,才让预期收益得以检验。若一个运行平台使测试和发布困难,其构建阻力也是显著影响。应尽早把适当切片交付并观察反馈;这不是要求绕过安全或发布约束,而是避免把尚未运行的构想当作已经实现的成果。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- To Practice Architecture Is to Decide · 查看原书依据
This might seem arbitrary, so let me explain. Recall the example of the developer who added a new GPL-licensed dependency that reached production. Imagine now, that before they updated their dependencies, the developer added a dependency scanner to the pipeline (which undertook the build, validation, and deployment). This scanner would catch the license violation and
参考来源
- 位置:《Facilitating Software Architecture》第02章《To Practice Architecture Is to Decide》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch02.html)
- 结论依据:原文以依赖扫描器和领域代码隔离说明path to production与运行品质都影响显著性。
- 原始内容:This might seem arbitrary, so let me explain. Recall the example of the developer who added a new GPL-licensed dependency that reached production. Imagine now, that before they updated their dependencies, the developer added a dependency scanner to the pipeline (which undertook the build, validation, and deployment). This scanner would catch the license violation and