Why must API servers be stateless to scale?
If any instance can answer any request, you can add or remove instances freely and a load balancer can route anywhere. State held in one server's memory, such as sessions or uploads in progress, pins users to that server and loses data when it dies. Move state to shared stores.
Answered in
Scaling the API Layer: Stateless Servers, Rate Limits, Caching and Async WorkThe API tier is the easy part to scale, if you keep it stateless. The practices that matter: limits, pagination, caching, queues and graceful overload.
Read the full analysisOther questions this article answers
More system design & architecture questions
- What is the architectural difference between an API Gateway and a Reverse Proxy?
- When should an architecture use Layer 4 instead of Layer 7 load balancing?
- How do edge ingress layers prevent backend cascading thundering herds?
- What algorithm is best for sticky sessions without breaking even distribution?
- How can a CDN improve performance for dynamic requests?
- What is the hardest part of operating behind a CDN?
- How can a CDN help with traffic surges or DDoS attacks?
- What is the difference between a Push CDN and a Pull CDN?
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.