Skip to content

5_What_Why_Load_Balancing.md

Latest commit

 

History

History
152 lines (118 loc) · 7.54 KB

5_What_Why_Load_Balancing.md

File metadata and controls

152 lines (118 loc) · 7.54 KB
+-------------------------------------------------------+
|                      LOAD BALANCER                     |
|                                                       |
|  +--------------------+      +--------------------+    |
|  |     Client 1       |----->|                    |    |
|  +--------------------+      |                    |    |
|                              |    Load Balancer    |    |
|  +--------------------+      |                    |    |
|  |     Client 2       |----->|                    |    |
|  +--------------------+      +--------------------+    |
|                                                       |
+------------------+---------+---------+-----------------+
                   |                   |
+------------------v---------+ +--------v----------------+
|       Server 1 (Active)    | |   Server 2 (Active)      |
|   - Processes requests     | | - Processes requests     |
|   - Responds to clients    | | - Responds to clients    |
+----------------------------+ +--------------------------+
                   |                   |
+------------------v---------+ +--------v----------------+
|       Server 3 (Backup)    | |   Server 4 (Backup)      |
|   - Stays idle unless      | | - Activates on failure   |
|     primary server fails   | | - Takes over traffic     |
+----------------------------+ +--------------------------+

                 Traffic Distribution Techniques:
+---------------------------------------------------------+
| Round Robin | Least Connections | Least Response Time    |
| Hashing     | DNS-Based         | Health Checks & Failover|
+---------------------------------------------------------+

                 Backup Strategies:
+---------------------------------------------------------+
| Active-Active: All servers handle traffic simultaneously |
| Active-Passive: Backup server takes over on failure      |
+---------------------------------------------------------+

What and Why of Load Balancing

Explanation

What is Load Balancing?

Load balancing is a technique used to distribute incoming network traffic across multiple servers. It helps prevent any single server from becoming overwhelmed, thereby enhancing both system performance and availability.

Why Use Load Balancing?

  1. Increase Throughput:

    • By distributing the workload among several servers, the system can handle a higher number of requests simultaneously.
    • Example: A website experiencing a surge in visitors can continue operating smoothly as the load is shared across multiple servers.

  2. Increase Availability:

    • Load balancing ensures that if one server fails, others can take over, maintaining continuous availability.
    • Example: In a microservice architecture, even if one instance of a service crashes, the load balancer redirects traffic to healthy instances.

How Does Load Balancing Work?

  1. Health Check:

    • Load balancers constantly monitor servers to ensure they are online and responsive.
    • They perform periodic checks, such as sending pings or HTTP requests, to determine server health.

  2. Traffic Distribution:

    • Requests are distributed based on different algorithms to ensure efficient utilization of resources.

  3. Passive Backup:

    • A secondary (backup) load balancer that remains on standby.
    • Activates when the primary load balancer fails, ensuring fault tolerance.

  4. DNS-Based Load Balancing:

    • Uses DNS to route traffic to the most appropriate server, based on proximity or availability.
    • Often used when servers are spread across multiple geographic locations.

Common Load Balancing Algorithms:

  • Round Robin or Random:

    • Sequentially or randomly distributes requests among servers.
    • Simple but effective when servers have similar capabilities.

  • Least Connections or Least Response Time:

    • Routes traffic to the server with the fewest active connections or the fastest response time.
    • Suitable for applications where traffic varies significantly.

  • Hashing:

    • Uses a hash function to consistently route similar requests to the same server.
    • Helps maintain session persistence.

Fun Analogy:

Imagine you are at a busy pizza parlor with multiple chefs. You don't want one chef to make all the pizzas while others stand idle.

  • Round Robin: Each chef takes turns making the next pizza.
  • Least Connections: You give the next pizza order to the chef who has the fewest pizzas being made.
  • Hashing: You always ask the same chef for your favorite pizza (e.g., Margherita) because they make it best.
  • Passive Backup: One chef only starts cooking if the main chef gets overwhelmed or leaves.
    This way, no single chef gets overwhelmed, and the guests are happy! 🍕

Mnemonic:

"Big Pizzas Always Have Tasty Cheese"

  • B - Balance Traffic: Distribute requests evenly.
  • P - Performance Boost: Improve system throughput.
  • A - Availability: Keep the system running even if some servers fail.
  • H - Health Monitoring: Regularly check server health to ensure uptime.
  • T - Traffic Management: Use algorithms to optimize distribution.
  • C - Continuity: Use passive backups to maintain service.

Interview Questions with Answers:

1. What is load balancing, and why is it important in system design?

Answer:
Load balancing is a technique to distribute incoming traffic across multiple servers, improving availability and performance. It prevents any single server from being overwhelmed, allowing the system to handle higher volumes of traffic.

2. What are the primary reasons to implement load balancing in a system?

Answer:

  1. Increase Throughput: Handle more requests concurrently.
  2. Increase Availability: Ensure the system remains online even if some servers fail.
  3. Traffic Distribution: Efficiently spread the workload using algorithms.
  4. Health Monitoring: Continuously check server status to prevent routing traffic to failed servers.

3. Explain DNS-based load balancing and when it is useful.

Answer:
DNS-based load balancing routes user requests to the most appropriate server based on location or server health. It is useful when you need to distribute traffic across geographically dispersed data centers.

4. What are the drawbacks of load balancing?

Answer:

  • Single Point of Failure: If the load balancer itself fails, the entire system may become unavailable (unless redundancy is configured).
  • Configuration Complexity: Setting up algorithms and health checks can be complex.
  • Cost: Additional hardware or managed services may increase costs.

5. How do health checks help in load balancing?

Answer:
Health checks continuously monitor the availability and performance of backend servers. They help ensure that only healthy servers receive incoming traffic, maintaining a seamless user experience even if some servers fail.

Additional Teaching:

Load balancing is essential in microservices architectures, where multiple instances of the same service run concurrently. By balancing traffic, the system can scale horizontally, adding more instances as needed without impacting performance.
Load balancers are commonly used with technologies like Nginx, HAProxy, and AWS ELB (Elastic Load Balancer). Understanding how to configure load balancing properly is crucial for maintaining system resilience and scalability.