Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As someone who cares about latency, why would I add an additional HTTP request to the request my users are making? I can just use an in-memory store to achieve the same thing under 1ms.

10ms is an eternity, and 100ms added on to every request is insane.



It helps your DDoSer bring down your services with fewer requests.


I think this is for a different kind of rate limiting. E.g. you have a website with a couple of servers, and you want to limit the number of chatGPT requests those servers are making per day. 10ms is meaningless to the chatGPT 12s p50.

You could spend an hour making your own persistence/coordination solution - or spend a minute and 5 bucks to call this service.


So... redis?


yep, you could spend the time to do that - and if you don't have a cache set up spend the time to set one up.

Or, you could pay 5 bucks.

I won't be using it, but I think there are some people, in some situations where the time savings are actually worth it. Kind of a funny niche


In the time it takes you to research and vet this solution, you’d have already written or installed a rate limiter package in your language of choice.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: