Vertical scaling vs horizontal scaling in HLD - Architecture Trade-offs

Problem Statement

When a system faces increased load, relying on a single server to handle all requests can cause slow response times and risk total failure if that server crashes. Without proper scaling, the system cannot handle growth or sudden spikes in traffic, leading to poor user experience and downtime.

Solution

Vertical scaling adds more power (CPU, RAM) to a single server to handle more load, while horizontal scaling adds more servers to share the load. Vertical scaling improves capacity by making one machine stronger, and horizontal scaling improves capacity by spreading work across many machines.

Architecture

Powerful

Powerful

↓

Server 1

↓

Load

Balancer

The diagram shows vertical scaling as upgrading a single server's resources, and horizontal scaling as adding multiple servers behind a load balancer sharing the workload.

Trade-offs

✓ Pros

→

Vertical scaling is simpler to implement since it involves upgrading one machine.

→

Horizontal scaling provides better fault tolerance because multiple servers share the load.

→

Horizontal scaling allows near unlimited growth by adding more servers.

→

Vertical scaling avoids complexity of distributed systems and data synchronization.

✗ Cons

→

Vertical scaling hits hardware limits and can be expensive beyond a point.

→

Horizontal scaling requires load balancing and data consistency mechanisms.

→

Horizontal scaling adds complexity in deployment, monitoring, and maintenance.

Use vertical scaling for small to medium workloads where simplicity is key and hardware upgrades are affordable. Use horizontal scaling when traffic exceeds single server capacity or high availability is required.

Avoid vertical scaling when expected load exceeds the maximum hardware limits or cost is prohibitive. Avoid horizontal scaling for very small systems where added complexity outweighs benefits.

Real World Examples

Netflix

Uses horizontal scaling with many servers behind load balancers to stream video reliably to millions of users worldwide.

Amazon

Employs horizontal scaling in its web services to handle massive traffic spikes during sales events.

Small business websites

Often use vertical scaling by upgrading their single server's CPU and RAM to handle moderate traffic increases.

Alternatives

Auto-scaling

Automatically adjusts the number of servers based on real-time load, combining horizontal scaling with automation.

Use when: Use when traffic fluctuates unpredictably and you want to optimize cost and performance.

Sharding

Splits data across multiple databases or servers to scale horizontally at the data layer.

Use when: Use when data size grows beyond single database capacity and needs distributed storage.

Summary

Vertical scaling increases a single server's capacity by adding more resources like CPU and RAM.

Horizontal scaling adds more servers to distribute the workload and improve fault tolerance.

Choosing between them depends on system size, expected load, cost, and complexity requirements.

Practice

1. Which of the following best describes vertical scaling in system design?

easy

A. Using caching to speed up data access

B. Adding more machines to distribute the workload

C. Splitting data across multiple databases

D. Adding more resources like CPU or RAM to a single machine

Solution

1. Step 1: Understand vertical scaling definition

   Vertical scaling means improving one machine's capacity by adding resources like CPU, RAM, or storage.

2. Step 2: Compare with other options

   Options B and C describe horizontal scaling or data partitioning, and D is about caching, not scaling.

3. Final Answer:

   Adding more resources like CPU or RAM to a single machine -> Option D

4. Quick Check:

   Vertical scaling = adding resources to one machine [OK]

Hint: Vertical scaling = beef up one machine, not add machines [OK]

Common Mistakes:

• Confusing vertical scaling with horizontal scaling
• Thinking adding machines is vertical scaling
• Mixing caching with scaling

2. Which option correctly shows horizontal scaling in a system architecture?

easy

A. Adding multiple servers behind a load balancer

B. Upgrading the CPU and RAM of a single server

C. Increasing the disk size of one database server

D. Using a faster network switch

Solution

1. Step 1: Identify horizontal scaling characteristics

   Horizontal scaling means adding more machines to share the workload, often managed by a load balancer.

2. Step 2: Eliminate other options

   Options B and C describe vertical scaling (upgrading one machine), and D is about network hardware, not scaling.

3. Final Answer:

   Adding multiple servers behind a load balancer -> Option A

4. Quick Check:

   Horizontal scaling = add machines behind load balancer [OK]

Hint: Horizontal scaling = add servers, vertical = upgrade one [OK]

Common Mistakes:

• Choosing upgrading one server as horizontal scaling
• Confusing network upgrades with scaling
• Ignoring load balancer role

3. Consider a web application initially running on a single server with 8 CPU cores and 16GB RAM. If the traffic doubles, which scaling approach will likely double the capacity most efficiently?

medium

A. Upgrade the server to 16 CPU cores and 32GB RAM (vertical scaling)

B. Add one more identical server and use a load balancer (horizontal scaling)

C. Add caching layer without changing servers

D. Increase database storage size

Solution

1. Step 1: Analyze capacity needs for doubled traffic

   Doubling traffic usually requires doubling processing power or distributing load.

2. Step 2: Compare vertical vs horizontal scaling efficiency

   Vertical scaling (Upgrade the server to 16 CPU cores and 32GB RAM (vertical scaling)) can be costly and limited by hardware max. Horizontal scaling (Add one more identical server and use a load balancer (horizontal scaling)) adds another server to share load, often more efficient and scalable.

3. Final Answer:

   Add one more identical server and use a load balancer (horizontal scaling) -> Option B

4. Quick Check:

   Doubling capacity = add server (horizontal) better than upgrade [OK]

Hint: Doubling load? Add servers horizontally, not just upgrade one [OK]

Common Mistakes:

• Assuming vertical scaling always doubles capacity easily
• Ignoring load balancer role in horizontal scaling
• Confusing storage increase with processing capacity

4. A system uses vertical scaling by upgrading a server's CPU and RAM. After some time, the server crashes under load. What is the most likely cause?

medium

A. The server reached hardware limits and cannot scale further vertically

B. The load balancer is misconfigured

C. The database storage is full

D. The network bandwidth is too high

Solution

1. Step 1: Understand vertical scaling limits

   Vertical scaling improves one machine but has physical hardware limits beyond which it cannot handle more load.

2. Step 2: Analyze crash cause

   Since the server crashes under load after upgrades, it likely hit max capacity. Other options relate to load balancer, storage, or network, which are less likely causes here.

3. Final Answer:

   The server reached hardware limits and cannot scale further vertically -> Option A

4. Quick Check:

   Vertical scaling hits hardware limits causing crashes [OK]

Hint: Vertical scaling hits max hardware limits causing failures [OK]

Common Mistakes:

• Blaming load balancer when none is used
• Confusing storage issues with CPU/RAM limits
• Ignoring hardware capacity limits

5. A startup expects rapid user growth and unpredictable traffic spikes. They want a scalable system with minimal downtime and cost efficiency. Which scaling strategy should they prioritize?

hard

A. Vertical scaling by upgrading a powerful single server

B. Relying on manual server upgrades during peak times

C. Horizontal scaling with multiple servers and auto-scaling

D. Using a single server with a large database

Solution

1. Step 1: Identify startup needs

   Rapid growth and unpredictable spikes require flexible, scalable solutions that can adjust resources quickly without downtime.

2. Step 2: Evaluate scaling options for flexibility and cost

   Vertical scaling (Vertical scaling by upgrading a powerful single server) is limited and costly for spikes. Manual upgrades (Relying on manual server upgrades during peak times) cause downtime and delay. Single server (Using a single server with a large database) risks failure. Horizontal scaling with auto-scaling (Horizontal scaling with multiple servers and auto-scaling) adds/removes servers dynamically, balancing cost and uptime.

3. Final Answer:

   Horizontal scaling with multiple servers and auto-scaling -> Option C

4. Quick Check:

   Rapid growth needs horizontal auto-scaling for cost and uptime [OK]

Hint: Rapid growth? Use horizontal auto-scaling for flexibility [OK]

Common Mistakes:

• Choosing vertical scaling for unpredictable spikes
• Ignoring downtime caused by manual upgrades
• Relying on single server risking failure