Uptime monitoring from outside your own infrastructure that alerts you the minute your site goes down — upordown.online
Rate limiting looks like a ten-minute job. Pick a number, put it in front of the API, done. Then on Monday morning a customer with 300 employees behind one office NAT gets blocked as a single "abusive client", your own mobile app retries every 429 immediately and makes things worse, and your uptime monitor starts reporting an outage that's really your own limiter.
None of that is a reason not to rate limit. It's a reason to treat the limiter like any other piece of production infrastructure. Here's the checklist I'd go through before turning one on.
Before you pick a number
1. Measure current traffic per client first
Don't guess the limit. Pull a week of access logs and compute requests per minute per key (API key, user ID or IP) at the 99th percentile and the maximum.…