Horizontal vs vertical scaling — what's the difference and which comes first?
My app is slowing down as users grow. Do I get a bigger server or more servers? How do real companies decide?
136
2 answers2.9K views2 Answers
Accepted answer
Vertical = bigger machine (more CPU/RAM). Horizontal = more machines behind a load balancer.
Go vertical first. It's one dashboard click, requires zero code changes, and modern cloud machines go absurdly big. Most apps never outgrow a well-sized single server plus a separate database.
Horizontal comes when vertical gets expensive or you need redundancy — but it demands your app be stateless: no sessions in memory, no files on local disk, everything shared (Redis, S3, database). That's a real refactor, so architects say 'design stateless from day one, scale vertically until it hurts'.
Before either: check it's not just a missing database index. 'Slow at 500 users' is almost never a scaling problem — it's an unoptimized query problem.
78
Real numbers for perspective: a $40/month VPS with Postgres tuned properly handles thousands of requests per second for a typical CRUD app. Most 'we need to scale' conversations at small startups are actually 'we need an index on that column' conversations.
10
Related questions
- Best free resources to learn system design in 2026?1 answer
- Monolith vs microservices for a small team — what's the honest answer?1 answer
- What is a load balancer and when do you actually need one?2 answers
- How does caching work and what should I cache first?1 answer
- What is the difference between SQL and NoSQL databases, and when do I choose each?1 answer
- How do I start learning system design as a fresher?1 answer