This website uses cookies to ensure you get the best experience.
Learn more.
A public API must limit abusive traffic. Which design is appropriate?
Published
- Apply supported rate limits and monitoring, while protecting backend capacity and authorization.
- Increase the backend's timeout without any request bound.
- Assume rate limiting makes every request authorized.
- Store all API keys in a public error page.
Comments — 0
Sign in to comment