知识卡片
模块化单体仍是单体
把大栈的代码拆成模块,可能改善阅读,却不会缩短整栈部署时间,也不会隔离变更风险或加快跨环境反馈。运行和发布边界未改变,单体问题仍然存在。需要独立演进时,应划出可分别发布和部署的小栈,而不只整理文件依赖。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 设计基础设施代码库 · 查看原书依据
Splitting a monolithic stack’s code into libraries may help make the code easier to understand and to change. However, this approach doesn’t solve the core problems of a monolith. Deploying the stack still takes too long, changes to one part risk impacting everything else in the stack, and the feedback loop for testing and delivering
参考来源
- 位置:《Infrastructure As Code》第10章《设计基础设施代码库》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch10.html)
- 结论依据:原文说明把大栈的代码拆成模块,可能改善阅读,却不会缩短整栈部署时间,也不会隔离变更风险或加快跨环境反馈;本卡据此解释其用途及适用边界。
- 原始内容:Splitting a monolithic stack’s code into libraries may help make the code easier to understand and to change. However, this approach doesn’t solve the core problems of a monolith. Deploying the stack still takes too long, changes to one part risk impacting everything else in the stack, and the feedback loop for testing and delivering