知识卡片
服务组件与耦合
服务是一组有凝聚力、独立部署的可执行功能;组件是执行业务或基础设施职责的架构构件,常体现为包、命名空间或文件目录;两者粒度不能互换。耦合的判断是:一方变化是否可能迫使另一方变化以维持正确性,而非只看是否存在网络调用。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 没有最佳实践时如何决策 · 查看原书依据
Two artifacts (including services) are coupled if a change in one might require a change in the other to maintain proper functionality. Component An architectural building block of the application that does some sort of business or infrastructure function, usually manifested through a package structure (Java), namespace (C#), or a physical grouping of source code files within some sort of directory structure.
参考来源
- 位置:《Software Architecture: The Hard Parts》第1章《没有最佳实践时如何决策》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch01.xhtml)
- 结论依据:原文的定义、比较或案例支持“服务是一组有凝聚力、独立部署的可执行功能;组件是执行业务或基础设施职责的架构构件,常体现为包、命名空间或文件目录;两者粒度不能互换”;正文据此解释其用途与适用边界。
- 原始内容:Two artifacts (including services) are coupled if a change in one might require a change in the other to maintain proper functionality. Component An architectural building block of the application that does some sort of business or infrastructure function, usually manifested through a package structure (Java), namespace (C#), or a physical grouping of source code files within some sort of directory structure.