Classic/Legacy Load Balancers
What You'll Learn
You'll understand what Classic Load Balancers are, why they're called "legacy," and how they differ from modern load balancers.
What Are Classic Load Balancers?
Classic Load Balancers (CLBs) are the first generation of cloud load balancers, predating the specialized Network Load Balancers (Layer 4) and Application Load Balancers (Layer 7) you just learned about. Think of them as the "Swiss Army knife" approach—they tried to do everything but weren't optimized for any specific use case.
How They Work
Unlike modern load balancers that focus on either Layer 4 (transport) or Layer 7 (application), Classic Load Balancers operate at both layers simultaneously, but with basic functionality:
- Layer 4 capabilities: Route TCP and SSL/TLS traffic based on IP and port
- Layer 7 capabilities: Perform basic HTTP/HTTPS routing and sticky sessions
- Limited features: Basic health checks, simple routing (no content-based rules)
Analogy: If modern load balancers are specialized tools (a precision screwdriver for Layer 4, a laser level for Layer 7), Classic Load Balancers are like an adjustable wrench—workable for many jobs but not ideal for any.
Why "Legacy"?
Cloud providers introduced specialized Layer 4 and Layer 7 load balancers because applications needed more advanced features like:
- Content-based routing (path, host, headers)
- WebSocket support
- Better performance and lower latency
- More flexible health checking
Classic Load Balancers remain available for backward compatibility with older applications but are rarely recommended for new deployments.
Key Takeaway: Classic Load Balancers are older, general-purpose load balancers that work at both Layer 4 and 7 with basic features—superseded by specialized Network and Application Load Balancers for modern workloads.