Application Load Balancers (Layer 7)
You'll learn: How Application Load Balancers inspect HTTP/HTTPS content to make intelligent routing decisions beyond simple network connections.
What Makes ALBs "Application-Aware"
While Network Load Balancers (Layer 4) route traffic based solely on IP addresses and ports, Application Load Balancers operate at Layer 7 of the OSI model—the application layer. This means they can actually read and understand HTTP/HTTPS requests before deciding where to send them.
Think of it like a restaurant host who doesn't just count people (Layer 4) but actually reads your reservation details: "Party of four? VIP guest? Allergy requirements?" The host routes you to the perfect table based on specific details, not just availability.
Content-Based Routing Decisions
ALBs examine the actual content of each HTTP/HTTPS request, including:
- URL paths: Route
/api/*requests to API servers,/images/*to media servers - Hostnames: Direct
api.example.comandwww.example.comto different target groups - HTTP headers: Route mobile users (detected via User-Agent header) to mobile-optimized backends
- HTTP methods: Send GET requests to read-only servers, POST/PUT to write-enabled servers
- Query strings: Route requests with
?version=2to new application versions
Why This Matters
This intelligent routing enables powerful patterns: you can run multiple applications behind a single load balancer, perform A/B testing, implement blue-green deployments, or gradually migrate to new services—all by configuring rules that inspect request content rather than managing complex network configurations.
Key Takeaway: Application Load Balancers read HTTP/HTTPS request details (URLs, headers, methods) to make smart routing decisions, enabling sophisticated traffic management patterns impossible with Layer 4 load balancing alone.