知识卡片
监控用于调整限流策略
限流后要观察拒绝的正常请求和突发时的保护效果。规则过严应调整阈值,算法不适配突发则重新选择机制;部署完成不能证明策略有效,算法和业务规则都需要独立观察。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
- · 第04章 限流器
原书出处 · 1 处
- 限流器 · 查看原书依据
Monitoring After the rate limiter is put in place, it is important to gather analytics data to check whether the rate limiter is effective. Primarily, we want to make sure: •The rate limiting algorithm is effective. •The rate limiting rules are effective. For example, if rate limiting rules are too strict, many valid requests are dropped. In this case, we want to relax the rules
参考来源
- 位置:《System Design Interview – An insiders guide, Second Edition》第04章《限流器》(来源项目 book-sources;源文件:extracted/System Design Interview – An insiders guide, Second Edition/_epub-src/text/part0010_split_000.html)
- 结论依据:原文在该位置给出所述对象、机制或比较,支持本卡的解释;原书未展开的实现不作为已证明结论,算式与一致性边界在正文明确限定。
- 原始内容:Monitoring After the rate limiter is put in place, it is important to gather analytics data to check whether the rate limiter is effective. Primarily, we want to make sure: •The rate limiting algorithm is effective. •The rate limiting rules are effective. For example, if rate limiting rules are too strict, many valid requests are dropped. In this case, we want to relax the rules