知识卡片
四种耦合的边界
内聚表示同一业务改动集中在一个组件;耦合表示组件被迫一起变化。实现耦合来自读取他方内部结构,时间耦合来自同步依赖对方此刻在线,部署耦合来自捆绑发布,领域耦合来自业务规则。前三者通常可以削减;“付款后才能发货”这类领域依赖只能通过改变业务需求消除。设计目标是高内聚与低耦合,而不是声称服务之间没有依赖。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 自治、边界与隔离 · 查看原书依据
Cohesion has to do with how code is organized and how strongly the code in each component is related. As Sam Newman puts it in his book Monolith to Microservices (O’Reilly), “the code that changes together, stays together.” The idea is that one desired change in business functionality should lead to changes in (ideally) only
参考来源
- 位置:《Practical Process Automation》第7章《自治、边界与隔离》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/ch07.xhtml)
- 结论依据:原文给出的机制、实例与边界支持本卡的解释。
- 原始内容:Cohesion has to do with how code is organized and how strongly the code in each component is related. As Sam Newman puts it in his book Monolith to Microservices (O’Reilly), “the code that changes together, stays together.” The idea is that one desired change in business functionality should lead to changes in (ideally) only