知识卡片

普通读书笔记卡 · 3351

单体好坏取决于边界

理解等级:高级

单体不是天然失败的架构。若需求要求能力紧密协作,集中部署可以减少部署单元;若本应独立变化的能力被强行绑在一起,变更成本会上升。评价单体要依据需求和边界,而非只看是否拆成服务。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    原书出处

    参考来源

    - 位置:《Principles of Software Architecture Modernization》第1章《What’s Wrong with Monoliths?》(源文件:`_epub-src/OPS/ch01.xhtml`,归一化正文 [50093:54239)) - 结论依据:原文否定“所有单体都差”,并把集中或拆分的选择系于需求与权衡。 - 原始内容:Monoliths are not always bad. In fact, sometimes, the right solution is to design something centralized from the outset. To reduce the number of deployment units, regardless of the inevitable size of the codebase, because of the nature of the problem you are solving. Software architecture and software design are essentially about trade-offs. When modeling something and deciding which capabilities should go on each service, we often face a big dilemma: together, or apart? Centralized, or distributed?