Why distributed patterns solve common challenges in HLD - Why This Architecture

Problem Statement

When a system runs on a single machine, it can become slow or stop working if too many users try to use it at once. Also, if that one machine breaks, the whole system stops, causing downtime and lost data.

Solution

Distributed patterns split the system into multiple parts that run on different machines. This way, the system can handle more users by sharing the work, and if one machine fails, others keep the system running without interruption.

Architecture

Client 1

↓

Load Balancer

Load Balancer

↓

Server 1

↓

Database 1

This diagram shows clients sending requests to a load balancer, which distributes the requests to multiple servers. Each server connects to its own database, illustrating how distributed components share the workload and data.

Trade-offs

✓ Pros

→

Improves system capacity by spreading work across multiple machines.

→

Increases reliability since failure of one machine doesn't stop the whole system.

→

Allows scaling by adding more machines as demand grows.

✗ Cons

→

More complex to design and maintain than a single machine system.

→

Requires handling data consistency and communication between machines.

→

Can introduce network delays and partial failures that need special handling.

Use distributed patterns when your system has more than 1,000 users or requests per second, or when uptime and fault tolerance are critical.

Avoid distributed patterns if your system has low traffic (under 100 requests per second) or if simplicity and fast development are more important than scalability.

Real World Examples

Netflix

Uses distributed microservices to handle millions of streaming requests simultaneously, ensuring no single point of failure.

Amazon

Distributes its e-commerce platform across many servers worldwide to handle huge traffic spikes during sales events.

Uber

Uses distributed services to process real-time ride requests and driver locations across many regions.

Alternatives

Monolithic Architecture

Runs the entire system as a single unit on one machine without splitting into parts.

Use when: Choose when the system is small, has low traffic, and rapid development is needed.

Vertical Scaling

Improves capacity by upgrading a single machine's hardware instead of adding more machines.

Use when: Choose when scaling needs are moderate and the cost of hardware upgrade is lower than managing multiple machines.

Summary

Distributed patterns split system work across multiple machines to handle more users and improve reliability.

They prevent single points of failure and allow scaling by adding machines.

However, they add complexity and require careful design to handle data and communication.

Practice

1. Which of the following best explains why distributed patterns are used in system design?

easy

A. They split work across machines to improve speed and reliability.

B. They reduce the number of users a system can handle.

C. They make systems more complex without benefits.

D. They centralize data to a single machine for simplicity.

Solution

1. Step 1: Understand the purpose of distributed patterns

   Distributed patterns divide tasks among multiple machines to improve performance and fault tolerance.

2. Step 2: Compare options with this understanding

   Only They split work across machines to improve speed and reliability. correctly states the benefit of splitting work to improve speed and reliability.

3. Final Answer:

   They split work across machines to improve speed and reliability. -> Option A

4. Quick Check:

   Distributed patterns improve speed and reliability = A [OK]

Hint: Distributed means spreading work to improve speed and reliability [OK]

Common Mistakes:

• Thinking distributed means fewer users can be handled
• Assuming distributed patterns add complexity without benefits
• Believing data is centralized in distributed systems

2. Which of the following is a correct example of a distributed pattern used to balance user requests?

easy

A. Load balancing

B. Single-threading

C. Monolithic deployment

D. Local caching only

Solution

1. Step 1: Identify patterns that distribute user requests

   Load balancing distributes incoming requests across multiple servers to avoid overload.

2. Step 2: Eliminate incorrect options

   Single-threading and monolithic deployment do not distribute load; local caching helps speed but not load distribution.

3. Final Answer:

   Load balancing -> Option A

4. Quick Check:

   Load balancing distributes requests = B [OK]

Hint: Load balancing spreads requests evenly across servers [OK]

Common Mistakes:

• Confusing single-threading with load distribution
• Thinking monolithic means distributed
• Assuming caching balances load

3. Consider a system using sharding to split a database into parts. What is the main benefit of this approach?

medium

A. It reduces the total data stored.

B. It duplicates all data on every server.

C. It centralizes data for easier management.

D. It improves query speed by parallelizing data access.

Solution

1. Step 1: Understand sharding in distributed systems

   Sharding splits data into smaller parts stored on different servers to allow parallel access.

2. Step 2: Analyze options based on sharding benefits

   Sharding does not reduce total data or centralize it; it improves speed by parallel queries.

3. Final Answer:

   It improves query speed by parallelizing data access. -> Option D

4. Quick Check:

   Sharding speeds queries by splitting data = D [OK]

Hint: Sharding splits data to speed up queries by parallel access [OK]

Common Mistakes:

• Thinking sharding reduces total data stored
• Believing sharding centralizes data
• Confusing sharding with replication

4. A system uses replication to copy data across servers. If one server fails, users still experience downtime. What is the likely problem?

medium

A. Replication slows down the system.

B. Replication duplicates data too many times.

C. Replication is not configured for failover.

D. Replication centralizes data on one server.

Solution

1. Step 1: Understand replication and failover

   Replication copies data to multiple servers to provide backup if one fails, but failover must be configured to switch users automatically.

2. Step 2: Identify why downtime occurs despite replication

   If users face downtime, failover is likely missing or misconfigured, so traffic doesn't switch to healthy servers.

3. Final Answer:

   Replication is not configured for failover. -> Option C

4. Quick Check:

   Failover missing causes downtime despite replication = C [OK]

Hint: Replication needs failover setup to avoid downtime [OK]

Common Mistakes:

• Assuming replication alone prevents downtime
• Thinking too many copies cause downtime
• Believing replication centralizes data

5. You design a global e-commerce platform expecting millions of users. Which combination of distributed patterns best solves challenges of speed, reliability, and data consistency?

hard

A. Single server for all data, caching only, no replication.

B. Load balancing for requests, replication for reliability, sharding for data scaling.

C. Replication only without load balancing or sharding.

D. Sharding only without replication or load balancing.

Solution

1. Step 1: Identify challenges in a global platform

   Speed requires spreading requests (load balancing), reliability needs data copies (replication), and scaling needs data partitioning (sharding).

2. Step 2: Match patterns to challenges

   Load balancing for requests, replication for reliability, sharding for data scaling. combines all three patterns to address speed, reliability, and scaling effectively.

3. Step 3: Eliminate incomplete options

   Options B, C, and D miss one or more key patterns, risking bottlenecks or failures.

4. Final Answer:

   Load balancing for requests, replication for reliability, sharding for data scaling. -> Option B

5. Quick Check:

   Combine load balancing, replication, sharding = A [OK]

Hint: Use load balancing, replication, and sharding together for big systems [OK]

Common Mistakes:

• Relying on single server for millions of users
• Using only one pattern and ignoring others
• Confusing replication with sharding roles