LearnViz CompSci
Home / Learn / Distributed Systems & Cloud / Vertical vs Horizontal Scaling

Beginner Topic 5 of 51 Distributed Systems & Cloud

Vertical vs Horizontal Scaling

Bigger machines versus more machines.

How it works

Vertical scaling, scaling up, adds more power such as CPU, memory and faster disks to a single machine, which is simple and needs no application changes but hits hardware limits, costs rise steeply and one machine remains a single point of failure. Horizontal scaling, scaling out, adds more machines and distributes work across them, offering near-unlimited growth and fault tolerance but requiring stateless design or partitioning, load balancing and handling of distributed consistency.

Where it is used

Databases often start with vertical scaling and add read replicas and sharding later, while web and application tiers scale horizontally behind load balancers, often with auto scaling groups.

Common pitfall

Horizontal scaling fails when state is stored in server memory or sessions are sticky. Shared databases become the bottleneck. Costs of coordination and data movement erode gains. Vertical scaling is often the cheapest first step and perfectly adequate for many workloads. Design stateless services, externalize state and test scale-out behavior early.

Where it fits in the course

Vertical vs Horizontal Scaling is topic 5 of 51 in Distributed Systems & Cloud, rated Beginner. It follows Scalability. The next topic is Latency vs Throughput.

Practice and explore

How to study this topic

  1. Read the explanation above and restate the definition in your own words.
  2. Open the interactive lesson and answer its mini quiz.
  3. Read the common pitfall, then write a short example that avoids it.
  4. Check your understanding in the Distributed Systems & Cloud quiz, and revisit the topic if you miss a question.

Frequently asked questions

What is Vertical vs Horizontal Scaling?
Bigger machines versus more machines. It belongs to Distributed Systems & Cloud and is a beginner-level topic.
Where do people use Vertical vs Horizontal Scaling?
Databases often start with vertical scaling and add read replicas and sharding later, while web and application tiers scale horizontally behind load balancers, often with auto scaling groups.
What is the most common mistake with Vertical vs Horizontal Scaling?
Horizontal scaling fails when state is stored in server memory or sessions are sticky.
What should I learn before this topic?
Start with Scalability, the topic just before it in Distributed Systems & Cloud.
How can I practice it?
Answer the mini quiz in the interactive lesson, then take the Distributed Systems & Cloud quiz.
Is Vertical vs Horizontal Scaling hard to learn?
It is a Beginner topic, so it works as an entry point. If the terms are new, read the explanation twice and try the visualizer before the quiz.
How long does it take to learn Vertical vs Horizontal Scaling?
Most learners can read the explanation and finish the interactive lesson in under an hour. Fluency comes from applying the idea, so plan a few short practice sessions with the quiz.
Which topics are related to Vertical vs Horizontal Scaling?
Scalability, Latency vs Throughput, Peer-to-Peer Systems are closely connected. The full list is in the related topics section of this page.
What should I study after Vertical vs Horizontal Scaling?
Continue with Latency vs Throughput, the next topic in Distributed Systems & Cloud.

Related topics