Performance vs Scalability

Performance is about speed for a single request. If your API takes 2 seconds to respond, that's a performance problem — and it would still be 2 seconds even if only one person was using it. You fix it by optimizing code, adding indexes, using caches, or reducing I/O. Scalability is about what happens as load increases. A perfectly performant system can still be unscalable — if adding 100× more users causes it to crash or slow to a crawl, that's a scalability problem. You fix it by redesigning how the system distributes work. The "fast alone, slow together" trap The most common mistake is confusing the two. Consider a system that: Returns a query in 50ms with 1 user ✅ Returns the same query in 8 seconds with 10,000 users ❌ That's a scalability failure, not a performance failure. The code isn't slow — the architecture can't handle concurrent demand. Performance deep dive Performance optimization targets the critical path of a single request: Latency is the time from request to response.