Why distributed patterns solve common challenges in HLD - Architecture Impact

System Overview - Why distributed patterns solve common challenges

This system demonstrates how distributed architectural patterns help solve common challenges like scalability, fault tolerance, and latency. It shows how splitting work across multiple services and using components like load balancers, caches, and message queues improves reliability and performance.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  +-------------------+
  |                   |
  v                   v
Service A           Service B
  |                   |
  v                   v
Cache A             Cache B
  |                   |
  v                   v
Database A          Database B
  |
  v
Message Queue
  |
  v
Worker Service

Components

User

client

Initiates requests to the system

Load Balancer

load_balancer

Distributes incoming requests evenly to API Gateway instances

API Gateway

api_gateway

Routes requests to appropriate backend services and handles authentication

Service A

service

Handles a subset of business logic and data processing

Service B

service

Handles another subset of business logic and data processing

Cache A

cache

Stores frequently accessed data for Service A to reduce database load

Cache B

cache

Stores frequently accessed data for Service B to reduce database load

Database A

database

Stores persistent data for Service A

Database B

database

Stores persistent data for Service B

Message Queue

message_queue

Queues asynchronous tasks to be processed by worker services

Worker Service

service

Processes background tasks asynchronously from the message queue

Request Flow - 14 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Service A

Service A → Cache A

Cache A → Service A

Service A → Database A

Database A → Service A

Service A → Cache A

Service A → API Gateway

API Gateway → Load Balancer

Load Balancer → User

Service A → Message Queue

Message Queue → Worker Service

Worker Service → Database A

Failure Scenario

Component Fails:Database A

Impact:Service A cannot write or read fresh data; cache may serve stale data

Mitigation:Reads served from cache if available; database replication and failover can restore availability

Architecture Quiz - 3 Questions

Why does the system use a load balancer before the API Gateway?

A To evenly distribute incoming requests and avoid overloading a single API Gateway instance

B To store frequently accessed data for faster responses

C To queue background tasks for asynchronous processing

D To directly connect users to the database

Design Principle

This architecture shows how distributing responsibilities across multiple components like load balancers, API gateways, caches, databases, and message queues helps solve challenges of scalability, fault tolerance, and latency. Each component focuses on a specific role, enabling the system to handle more users, recover from failures, and respond faster.

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