What's the actual difference between performance and scalability?
Performance asks how fast the system responds under a fixed, known load — a question of latency and throughput at one point in time. Scalability asks what happens to those same numbers as load grows — does latency stay flat, or does it degrade as more users, data, or requests arrive? A system can have excellent performance at today's load and terrible scalability, meaning that same good performance collapses the moment load doubles.
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.