知识卡片
同步服务的耦合成本
同步调用使一个请求的完成依赖下游响应,依赖继续扇出后,容量、故障处理、API版本和集成测试都可能跨服务协调,形成分布式单体。但即时认证、用户响应和第三方API仍适合请求响应。应逐项判断延迟与数据需求,避免把企业成功当作架构优越性的证据,也不把事件驱动视为所有交互的替代。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Why Event-Driven Microservices · 查看原书依据
Synchronous microservices rely on other services to help them perform their business tasks. Those services, in turn, have their own dependent services, which have their own dependent services, and so on. This can lead to excessive fanout and difficultly in tracing which services are responsible for fulfilling specific parts of the business logic. The number of connections between services can become staggeringly high, which further entrenches the existing communication structures
参考来源
- 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第01章《Why Event-Driven Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch01.xhtml;规范化段落起句:Synchronous microservices rely on other services)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:同步调用使一个请求的完成依赖下游响应,依赖继续扇出后,容量、故障处理、API版本和集成测试都可能跨服务协调,形成分布式单体。本卡同时保留其适用条件与失败边界。
- 原始内容:Synchronous microservices rely on other services to help them perform their business tasks. Those services, in turn, have their own dependent services, which have their own dependent services, and so on. This can lead to excessive fanout and difficultly in tracing which services are responsible for fulfilling specific parts of the business logic. The number of connections between services can become staggeringly high, which further entrenches the existing communication structures