知识卡片
依赖图深度需要折中
把服务作为节点、使用其他服务数据作为有向边,可得到依赖图。任意相互调用容易形成深链、超时和难排障;所有调用都强制经过单层协调器,又把业务逻辑和参数搬运集中到协调层。可用简单、较浅的图在二者间折中,深度应由业务与证据决定;本章两三层是建议而非全局硬上限。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 宏观架构中的微服务决策 · 查看原书依据
One option is to freely invoke other microservices whenever it is needed. That creates a spaghetti architecture from the pre-ESB era. I am not a fan of that model. It can lead to deep invocation paths, creating complexity.
参考来源
- 位置:《Software Architecture and Decision-Making》第10章《Macro Architecture: Microservices Considerations》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch10.xhtml)
- 结论依据:摘录说明把服务作为节点、使用其他服务数据作为有向边,可得到依赖图。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。
- 原始内容:One option is to freely invoke other microservices whenever it is needed. That creates a spaghetti architecture from the pre-ESB era. I am not a fan of that model. It can lead to deep invocation paths, creating complexity.