---
answer: direct
beat: system-design
source: 1 article · updated: November 14, 2026
---

How should an API respond when it is overloaded?

Fail fast and visibly: return 429 for a client over its limit and 503 with Retry-After when the service is saturated. Rejecting excess work quickly protects the requests already in flight, whereas queueing everything indefinitely makes all of them slow and eventually time out.

Answered in

Scaling the API Layer: Stateless Servers, Rate Limits, Caching and Async Work

The API tier is the easy part to scale, if you keep it stateless. The practices that matter: limits, pagination, caching, queues and graceful overload.

Crashtech Editorial November 14, 2026 System Design & Architecture

Read the full analysis

Other questions this article answers

More system design & architecture questions

Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.