知识卡片
限流与熔断保护不同风险
限流约束进入的请求速率,避免健康服务因过量负载崩溃;熔断依据下游失败暂时阻止调用,限制持续失败和重试放大。两者可组合,拒绝与降级也必须遵守业务正确性。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Traffic Routing Strategies · 查看原书依据
Rate limiting prevents service degradation by controlling request rates commonly implemented using tools like Istio’s adaptive throttling or token-bucket algorithms in NGINX. Circuit breakers halt cascading failures by blocking requests to unhealthy services popularized by libraries like Netflix Hystrix (now deprecated) and its modern successor Resilience4j, or infrastructure-layer solutions like Envoy’s circuit breaking.
参考来源
- 位置:《Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…》第07章《Traffic Routing Strategies》(来源项目book-sources;源文件:extracted/Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…/_epub-src/OPS/ch07.xhtml)
- 结论依据:原文的机制或对比支持以下核心判断:限流约束进入的请求速率,避免健康服务因过量负载崩溃;熔断依据下游失败暂时阻止调用,限制持续失败和重试放大。 本卡将相邻说明中的适用限制保留为解释。
- 原始内容:Rate limiting prevents service degradation by controlling request rates commonly implemented using tools like Istio’s adaptive throttling or token-bucket algorithms in NGINX. Circuit breakers halt cascading failures by blocking requests to unhealthy services popularized by libraries like Netflix Hystrix (now deprecated) and its modern successor Resilience4j, or infrastructure-layer solutions like Envoy’s circuit breaking.