知识卡片

普通读书笔记卡 · 1976.ah.6

调用链会抵消拆分收益

理解等级:高级

多个服务每次请求都需同步协作时,任一下游故障可能经传递依赖让全部请求失败;网络安全延迟也逐跳累积。判断是否合并,应看跨服务请求占比及关键请求时延,不能只看平均比例。即使多数请求独立,只要核心请求需要极快响应,也可能应合并或重新设计流程。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 服务粒度 · 查看原书依据

      A good rule of thumb is to take into consideration the number of requests that require multiple services to communicate with one another, also taking into account the criticality of those requests requiring interservice communication.

    参考来源

    - 位置:《Software Architecture: The Hard Parts》第07章《服务粒度》(来源项目: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/ch07.xhtml) - 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。 - 原始内容:A good rule of thumb is to take into consideration the number of requests that require multiple services to communicate with one another, also taking into account the criticality of those requests requiring interservice communication.