Conceptual Foundations of Elastic Load Balancing
Elastic Load Balancing (ELB) is a managed service that automatically distributes incoming traffic across multiple targets such as EC2 instances, containers, IP addresses, and Lambda functions.
At its core, a load balancer solves three architectural problems:
- Availability - Avoid single points of failure.
- Scalability - Distribute load horizontally.
- Abstraction - Decouple clients from backend infrastructure.
Without a load balancer, clients must know the exact backend server. That creates tight coupling and operational complexity. With ELB, clients connect to a stable endpoint, and the load balancer dynamically routes traffic to healthy targets.
ELB Types and Their Roles
AWS provides three main types:
- Application Load Balancer (ALB) - Layer 7 (HTTP/HTTPS). Content-based routing, host/path rules, WebSocket support.
- Network Load Balancer (NLB) - Layer 4 (TCP/UDP/TLS). Ultra-low latency, static IPs, extreme performance.
- Gateway Load Balancer (GWLB) - Designed for inserting third-party virtual appliances (e.g., firewalls) into traffic flow.
Architecturally, the type you choose depends on:
- Protocol awareness requirements
- Performance constraints
- Need for advanced routing logic
- Integration with security appliances
How ELB Works Internally
An ELB is deployed across multiple Availability Zones (AZs). Each AZ contains load balancer nodes. When you enable cross-zone load balancing, traffic is evenly distributed across all registered targets in all enabled AZs.
Key internal mechanisms:
- Listeners: Define protocol and port.
- Target Groups: Logical grouping of backend resources.
- Health Checks: Continuous monitoring of target health.
- Routing Logic: Based on listener rules.
Why this matters architecturally:
- Health checks remove unhealthy nodes automatically.
- Target groups allow gradual deployments and blue/green strategies.
- Listeners decouple protocol handling from backend implementation.
ELB Foundations Check
Question 1 of 2
At which OSI layer does an Application Load Balancer operate?
In this section, I learned:
0 of 4 completed