[Question] Can you use Kratos to implement the implementation of the outbound traffic when requesting downstream services based on custom indicators?

[tommycat96]

你好，我目前想在多个实例上使用限流组件，通过定期检查下游资源的负载情况，动态调整当前周期的限流。

而且因为这多个实例启动的时间不一致，因此会存在这种情况：实例A正在以最大限流运行，此时实例B启动，实例A需要降低限流上限，而实例B需要从最小的限流值开始，逐步增加到实例A与实例B都能平稳运行的限流值。

从目前Kratos文档看的话，似乎没有关于基于自定义指标的自适应限流，想咨询一下，Kratos是否支持这种case。

[kratos-ci-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Hello, I currently want to use the current limiting component on multiple instances, dynamically adjust the current limit of the current period by regularly checking the load status of downstream resources.

Moreover, because the start time of these multiple instances is inconsistent, this situation exists: Instance A is running at the maximum current limit, and at this time, Instance B starts, Instance A needs to lower the current limit limit, while Instance B needs to start from the minimum current limit value and gradually increase to the current limit value that can operate smoothly between Instance A and Instance B.

Judging from the current Kratos documentation, there seems to be no adaptive current limit based on custom indicators. I would like to ask whether Kratos supports this case.

[dosubot]

Hi @tommycat96! I'm Dosu and I’m helping the kratos team.

Kratos 本身没有内置基于自定义指标或下游负载的自适应限流，也没有分布式多实例动态协同的限流实现。Kratos 的限流中间件（middleware/ratelimit）默认用的是本地 BBR 算法，但支持通过接口自定义限流器（Limiter），你可以实现自己的逻辑，比如根据下游负载、实例数量、启动顺序等动态调整限流策略，然后通过 WithLimiter 注入到中间件中使用。相关代码和接口设计可以参考 ratelimit.go。

目前文档和社区没有现成的自适应或分布式限流方案示例，这类需求需要你自定义实现限流器，并结合外部协调机制（如 Redis、etcd、服务发现等）来实现多实例间的动态协同。Kratos 的扩展性可以满足你的场景，但需要自行开发相关逻辑。

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[tommycat96]

好的，非常感谢

[kratos-ci-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

OK, thank you very much