Why scalability handles growing traffic in HLD - Why This Architecture

Problem Statement

When a system faces more users or requests than it can handle, it slows down or crashes. This causes poor user experience and lost business because the system cannot keep up with growing traffic.

Solution

Scalability allows a system to grow its capacity by adding more resources or optimizing existing ones. This means the system can handle more users or requests smoothly without slowing down or failing.

Architecture

User 1

↓

Load Balancer

↓

Server 1

This diagram shows multiple users sending requests to a load balancer, which distributes traffic across multiple servers to handle growing traffic.

Trade-offs

✓ Pros

→

Improves system capacity to handle more users or requests.

→

Prevents system crashes and slowdowns under high load.

→

Enables gradual resource addition without downtime.

→

Supports business growth by maintaining performance.

✗ Cons

→

Adds complexity in managing multiple servers or resources.

→

Requires investment in infrastructure or cloud resources.

→

Needs careful design to avoid bottlenecks like load balancer limits.

When user traffic or request volume grows beyond the capacity of a single server, typically above thousands of requests per second.

When the system has very low traffic (under hundreds of requests per second) and complexity overhead outweighs benefits.

Real World Examples

Netflix

Uses scalable microservices and load balancing to stream video to millions of users simultaneously without interruption.

Amazon

Scales its e-commerce platform dynamically during peak shopping seasons to handle huge spikes in traffic.

Uber

Scales its ride-matching services to support millions of concurrent users requesting rides worldwide.

Alternatives

Vertical Scaling

Increases capacity by upgrading a single server's hardware instead of adding more servers.

Use when: When the system is small and can benefit from a more powerful machine without complex distribution.

Caching

Reduces load by storing frequent responses closer to users instead of scaling servers.

Use when: When read-heavy traffic can be served from cache to reduce backend load.

Summary

Scalability prevents system failures by allowing capacity to grow with traffic.

It works by adding resources or optimizing to handle more users smoothly.

Proper scalability design supports business growth and user satisfaction.

Practice

1. What does scalability in system design primarily help with?

easy

A. Handling more users and traffic smoothly

B. Reducing the number of servers

C. Making the system slower

D. Limiting the system to one user

Solution

1. Step 1: Understand the meaning of scalability

   Scalability means the system can grow to handle more users or traffic without problems.

2. Step 2: Identify the main goal of scalability

   The main goal is to manage increasing traffic smoothly, not to reduce servers or slow down.

3. Final Answer:

   Handling more users and traffic smoothly -> Option A

4. Quick Check:

   Scalability = Handling more traffic [OK]

Hint: Scalability means growing capacity to handle more users [OK]

Common Mistakes:

• Thinking scalability reduces servers
• Confusing scalability with slowing system
• Believing scalability limits users

2. Which option correctly describes vertical scaling?

easy

A. Upgrading the hardware of a single machine

B. Distributing traffic using load balancers

C. Adding more machines to the system

D. Reducing the number of users

Solution

1. Step 1: Define vertical scaling

   Vertical scaling means improving one machine's hardware, like adding CPU or memory.

2. Step 2: Differentiate from other options

   Adding machines is horizontal scaling; load balancers distribute traffic; reducing users is unrelated.

3. Final Answer:

   Upgrading the hardware of a single machine -> Option A

4. Quick Check:

   Vertical scaling = Upgrade one machine [OK]

Hint: Vertical scaling upgrades one machine's hardware [OK]

Common Mistakes:

• Confusing vertical with horizontal scaling
• Thinking vertical scaling adds machines
• Mixing load balancers with scaling types

3. Consider a system with 3 servers behind a load balancer. If traffic doubles, what happens when horizontal scaling is applied?

medium

A. Remove servers to reduce complexity

B. Upgrade the CPU of one server only

C. Add more servers to share the load

D. Ignore traffic increase and keep same setup

Solution

1. Step 1: Understand horizontal scaling

   Horizontal scaling means adding more servers to handle increased traffic.

2. Step 2: Apply to the scenario

   With doubled traffic, adding servers helps share load; upgrading one server is vertical scaling.

3. Final Answer:

   Add more servers to share the load -> Option C

4. Quick Check:

   Horizontal scaling = Add servers [OK]

Hint: Horizontal scaling means adding servers [OK]

Common Mistakes:

• Choosing to upgrade one server (vertical scaling)
• Removing servers when traffic grows
• Ignoring traffic increase

4. A system uses a load balancer but still crashes under high traffic. What is the likely issue?

medium

A. Too many servers are added unnecessarily

B. Load balancer is not distributing traffic evenly

C. Vertical scaling was applied correctly

D. Traffic is decreasing, causing overload

Solution

1. Step 1: Analyze load balancer role

   Load balancers distribute traffic evenly to servers to prevent overload.

2. Step 2: Identify cause of crash

   If system crashes despite load balancer, it may not be distributing traffic properly, causing some servers to overload.

3. Final Answer:

   Load balancer is not distributing traffic evenly -> Option B

4. Quick Check:

   Uneven load distribution causes crashes [OK]

Hint: Check if load balancer spreads traffic evenly [OK]

Common Mistakes:

• Assuming too many servers cause crash
• Thinking vertical scaling always fixes crashes
• Believing traffic decrease causes overload

5. A web app faces sudden traffic spikes. Which combination best ensures smooth scaling?

hard

A. Only upgrade one server's CPU and RAM

B. Limit user access to reduce traffic

C. Remove load balancers and rely on a single powerful server

D. Use horizontal scaling with load balancers and auto-scaling groups

Solution

1. Step 1: Identify best scaling approach for spikes

   Horizontal scaling with load balancers allows adding/removing servers dynamically to handle spikes.

2. Step 2: Evaluate other options

   Upgrading one server limits capacity; removing load balancers causes bottlenecks; limiting users reduces usability.

3. Final Answer:

   Use horizontal scaling with load balancers and auto-scaling groups -> Option D

4. Quick Check:

   Horizontal scaling + load balancers = smooth spikes [OK]

Hint: Combine horizontal scaling and load balancers for spikes [OK]

Common Mistakes:

• Relying only on vertical scaling
• Removing load balancers causing bottlenecks
• Limiting users instead of scaling