知识卡片
限流规则独立发布
规则描述限流维度、时间单位和阈值,可由配置文件维护并加载到缓存。将规则从请求判断逻辑分离便于调整;实际发布时仍须考虑实例何时拿到规则,不能把磁盘文件更新等同于所有节点同步生效。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
- · 第04章 限流器
原书出处 · 1 处
- 限流器 · 查看原书依据
Rate limiting rules Lyft open-sourced their rate-limiting component [12]. We will peek inside of the component and look at some examples of rate limiting rules: domain: messaging descriptors: - key: message_type Value: marketing rate_limit: unit: day requests_per_unit: 5 In the above example, the system is configured to allow a maximum of 5 marketing messages per day. Here is another example: domain: auth descriptors: - key:
参考来源
- 位置:《System Design Interview – An insiders guide, Second Edition》第04章《限流器》(来源项目 book-sources;源文件:extracted/System Design Interview – An insiders guide, Second Edition/_epub-src/text/part0009_split_003.html)
- 结论依据:原文在该位置给出所述对象、机制或比较,支持本卡的解释;原书未展开的实现不作为已证明结论,算式与一致性边界在正文明确限定。
- 原始内容:Rate limiting rules Lyft open-sourced their rate-limiting component [12]. We will peek inside of the component and look at some examples of rate limiting rules: domain: messaging descriptors: - key: message_type Value: marketing rate_limit: unit: day requests_per_unit: 5 In the above example, the system is configured to allow a maximum of 5 marketing messages per day. Here is another example: domain: auth descriptors: - key: