Re:Testing a new rate-limiting service – feedback welcome
by 0megion on Friday September 19, 2025 @10:02AM
(#45301798)
It's already too late if requests are hitting your service. What happens when a customer sends x100 traffic all of a sudden, your Rails backend needs to scale or crash to handle the rate limiting.
[ Parent
| on HN ]
Re:Testing a new rate-limiting service – feedback welcome
by nik736 on Friday September 19, 2025 @10:09AM
(#45301858)
For me it's not a big deal, my app autoscales and rate limit details are stored in Redis, so it's super fast. For x100 the traffic it wouldn't even need to scale since it's simply hitting Redis.
Re:Testing a new rate-limiting service – feedback welcome
by 0megion on Saturday September 20, 2025 @04:34AM
(#45311553)
Interesting, but still your Rail app needs to apply the rate limit logic working with Redis, maybe your DB will be protected, but you will still receive the traffic through your network, meaning more ingress cost, along with CPU to process all the incoming requests.
Re:Testing a new rate-limiting service – feedback welcome
by nik736 on Saturday September 20, 2025 @03:52PM
(#45316750)
Ingress is free with most providers. Yes, of course it adds a bit pressure on the cpu, but yours would add latency, might add peering issues, additional costs, etc. and I have no control.