A question has come up concerning how rate limiting might function, or what is best practice if I'd like to rate limit on the following example.

Problem = I would like to rate limit all junction requests through URL - https://test.rate.org/ - with a capacity of 10, in a 60 second interval.
     I would also like to rate limit junction requests for URL - http://test.rate.org/junction1 - with a stricter capacity of 5, in a 30 second interval.
     Thirdly, I would also like to rate limit junction requests for URL - http://test.rate.org/junction2 - with an even stricter capacity of 2, in a 10 second interval.

Would this be achieved by implementing 3 rate limiting config/YAML files? Or can multiple URLs, methods, and intervals/capacities be placed in a sole rate limiting config?

Secondly, when a request is parsed for rate limiting, I'm figuring it's going to wind up in a bucket for the first rule/pattern it matches. So would I list these rules above from least-strict to most-strict to be able to achieve this functionality? 

I'm just curious what best practice would be here. 

Thanks and regards,
Bayless Rutherford

------------------------------
Bayless Rutherford
------------------------------