How is elasticity different from scalability?
Scalability describes whether a system's characteristics hold up as load increases, in principle. Elasticity describes how automatically and quickly the system's actual infrastructure adapts to demand changes in practice — auto-scaling groups adding servers during a traffic spike and removing them afterward. A system can be scalable in design but not elastic (it can handle more load if you manually provision more servers) or elastic but not scalable (it adds servers automatically, but the architecture has a bottleneck no amount of added servers fixes).
Answered in
Scalability, Performance, and Elasticity Are Not the Same ProblemA fast system can still fail to scale, and an elastic system can still be slow. Confusing the three leads to fixing the wrong bottleneck.
Read the full analysisOther questions this article answers
More system design & architecture questions
- How much spare capacity should a gateway keep?
- Why are bounded queues important for availability?
- Should a load balancer always move requests away from an unhealthy server?
- Can a circuit breaker prevent every cascading failure?
- Why does pagination improve API performance beyond just 'smaller responses'?
- Why is asynchronous logging faster than writing logs synchronously?
- When does caching actually help API performance, and when doesn't it?
- Why does payload compression trade CPU time for network time, and when is that worth it?
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.