Features

Govardhana Miriyala Kannaiah Govardhana Miriyala Kannaiah

๐Ÿญ. ๐—™๐—ฎ๐—ถ๐—น๐˜‚๐—ฟ๐—ฒ ๐—›๐—ฎ๐—ป๐—ฑ๐—น๐—ถ๐—ป๐—ด: Auto-rerouting away from failed components for high availability and minimal downtime

๐Ÿฎ. ๐—œ๐—ป๐˜€๐˜๐—ฎ๐—ป๐—ฐ๐—ฒ ๐—›๐—ฒ๐—ฎ๐—น๐˜๐—ต ๐—–๐—ต๐—ฒ๐—ฐ๐—ธ๐˜€: Regularly monitors and verifies the instances health, ensuring incoming traffic solely to operational, healthy instances

๐Ÿฏ. ๐—ฃ๐—น๐—ฎ๐˜๐—ณ๐—ผ๐—ฟ๐—บ ๐—ฆ๐—ฝ๐—ฒ๐—ฐ๐—ถ๐—ณ๐—ถ๐—ฐ ๐—ฅ๐—ผ๐˜‚๐˜๐—ถ๐—ป๐—ด: Directs platform-specific (mobile, desktop etc.,) requests to separate backend servers for tailored responses

๐Ÿฐ. ๐—ฆ๐—ฆ๐—Ÿ ๐—ง๐—ฒ๐—ฟ๐—บ๐—ถ๐—ป๐—ฎ๐˜๐—ถ๐—ผ๐—ป: Offloads SSL encryption/decryption, easing backend server load

๐Ÿฑ. ๐—–๐—ฟ๐—ผ๐˜€๐˜€ ๐—ญ๐—ผ๐—ป๐—ฒ ๐—Ÿ๐—ผ๐—ฎ๐—ฑ ๐—•๐—ฎ๐—น๐—ฎ๐—ป๐—ฐ๐—ถ๐—ป๐—ด: Evenly distribute traffic across multiple availability zones, enhancing fault tolerance and scalability

๐Ÿฒ. ๐—จ๐˜€๐—ฒ๐—ฟ ๐—ฆ๐˜๐—ถ๐—ฐ๐—ธ๐—ถ๐—ป๐—ฒ๐˜€๐˜€: Ensures session continuity and personalized experiences by connecting users to specific backend servers



Strategies

Leo Coelho Leo Coelho

The primary responsibility of a Load Balancer is to evenly distribute incoming network traffic across multiple servers or containers.

  1. The Load Balancer applies its load balancing strategy to select an available container to handle the request.

  2. The Load Balancer routes the request to the chosen container running the application.

  3. The container processes the request, generates a response, and sends it back to the client (via the Load Balancer and API Gateway).

Here are some common load-balancing strategies.

Round Robin

  1. Round Robin: distributes sequentially across the available containers.

Least Connection

  1. Least Connection: forwards to the container with the fewest active connections.

IP Hash

  1. IP Hash: use the clientโ€™s IP address to determine the container to handle the request. It ensures that a given client always reaches the same container.

Weighted Round Robin

  1. Weighted Round Robin: Each container is assigned a weight, and requests are distributed based on the assigned weights. Containers with higher weights receive a proportionally larger share of requests.est. It ensures that a given client always reaches the same container.