3 ms·
Slightly OT, we have several different kinds of services that need rate limiting, written in different stacks. We would like to have one solution for rate limi
by netcraft 6y ago
Slightly OT, we have several different kinds of services that need rate limiting, written in different stacks. We would like to have one solution for rate limiting, ideally that we could put in front of any service, that was light weight, but also could work with AWS target groups that are already splitting traffic across nodes inside a service - so I believe that means some sort of clustered solution or at least communication. Is haproxy a good fit for this? Maybe nginx (paid)?
- social_quotient 6y agoWe use HAproxy for similar reasons you describe if I’m understanding correctly. As one of the other posts kinda suggested you can get a ton done with a few hours, it might be worth just standing up a box real quick and trying it out. As a note when we try stuff like this we put behind a AWS LB so we can push partial traffic to our experiment and aren’t betting the farm whilst testing in prod. Good luck!
- nine_k 6y agoI wonder why Envoy is not mentioned.