-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[request] Throttling Control #234
Comments
Isn't the rejecting requests from consumers already available via ratelimting plugin? |
@tamizhgeek there could be significant difference between a traditional rate limiting behaviour and throttling. there also overlap in certain aspects. in this case, throttling is dynamic over a range of time, vs. with rate limiting it's a fixed limit to a time unit. e.g. you can have BOTH rules working together: rate limiting: throttle: also, since this would be a separate plugin would need it's own logic for rejecting requests... |
+1 for a throttling plugin. One of the missing features compared to alternative solutions. |
I was searching for a plugging like this. This issue is closed now and I don't see a throttle plugin on the kong website. Are there any alternatives that implement this behaviour? |
Kong Enterprise Edition (EE) includes https://docs.konghq.com/enterprise/latest/plugins/rate-limiting-advanced/ plugin which offers a sliding window option. Using a sliding window has the effect of limiting the rate of requests - requests occurring at a consistently excessive rate will be rejected. More details are available here https://docs.konghq.com/enterprise/latest/rate-limiting/ and here https://konghq.com/blog/how-to-design-a-scalable-rate-limiting-algorithm/ Going forward, please move the discussion of features to Kong Nation https://discuss.konghq.com/ - Github Issues are reserved for bug reports. Thanks! |
Definition:
Thoughts / Ideas:
The text was updated successfully, but these errors were encountered: