 |
| Scaling your API with rate limiters (stripe.com) | ||
| recommended by 2 users | 2017 | 351 points by edwinwee | distributed systems | original thread | | ||
| 2 users recommended this thread. What they said: |
| jdmichal Apr 12, 2017 | on: An Alternative Approach to Rate Limiting | context |
|
chatmasta May 29, 2018 | on: Show HN: Golimit – Ringpop-based distributed and… | context
If I’m reading this right, is it possible to use the sidecar technique to install this along keep my existing load balancer architecture? For example, if every server has an haproxy frontend, and I install this sidecar on each server, how do I interact with it from haproxy? Also, there was an HN thread last year from stripe with a good discussion of distributed rate limiting: https://news.ycombinator.com/item?id=13997029 |
| Also recommended by people who recommended this: | ||
| 1. | Stripe: instant payment processing for developers (stripe.com) | |
| recommended by 3 users | 2011 | 1249 points by pc | original thread | | ||
Once you start getting into quality-of-service, basic rate limiting like the discussed is not enough. I think Stripe did a better job of covering such concerns in their rate limiter post. They specifically talk about being lenient to "bursty" traffic, as that was a legitimate use-case for clients.
https://stripe.com/blog/rate-limiters
https://news.ycombinator.com/item?id=13997029