Open nathanpalmer opened 7 years ago
If your API service support busting up to 30 requests per 60s, it make senses to add a new request-per-minutes rate limit control :) @nathanpalmer
But the "rpm" solution means that I can burst 30 requests in 1 second, and then spend the other 59 seconds of the current minute waiting.
What if I really want to limit my requests to one request per 2 seconds? The decimal solution seems necessary as well.
I made a pull request for a fork that addresses this issue:
We're looking for a solution to limit requests to an external API to slow down our requests (from multiple backend services) to conform with their rate limits. They have set a 30 request per minute limit which is going to be roughly ½ requests per second.
This doesn't seem to fit in with cuttle's configuration as anything under 0 is throwing an exception. I would essentially need to set a
rate: .5
in the configuration I believe.