AWS ALB vs NLB: Choosing the Right ELB for SAA-C03
The Application Load Balancer (ALB) operates at OSI Layer 7, ideal for HTTP/HTTPS traffic with advanced routing like path-based rules. The Network Load Balancer (NLB) operates at Layer 4, designed for ultra-high performance, TCP/UDP traffic, and static IP requirements. Choose ALB for flexibility and NLB for extreme scale and low latency.
What is the core difference between Layer 7 and Layer 4 load balancing?
When you're studying for the SAA-C03, the first thing you need to wrap your head around is the OSI model. The Application Load Balancer (ALB) lives at Layer 7. This means it's 'intelligent'—it can actually see the content of the HTTP request, including headers, cookies, and the URL path. It makes routing decisions based on this data, which is why it's the gold standard for modern web applications.
On the flip side, the Network Load Balancer (NLB) operates at Layer 4. It doesn't care about the content of your packet; it only looks at the IP protocol, source/destination IP, and port. Because it skips the heavy lifting of inspecting the application layer, it's incredibly fast. If your scenario requires handling millions of requests per second with ultra-low latency, you're looking at an NLB.
When should you choose ALB for advanced routing?
You'll see plenty of SAA-C03 questions where a company wants to route traffic to different microservices based on the URL. This is where the ALB shines with path-based and host-based routing. For example, you can send requests for 'example.com/orders' to one target group and 'example.com/images' to another. This allows you to decouple your services and scale them independently.
ALB also handles HTTPS termination and supports WebSockets, making it the go-to for interactive web apps. If the exam prompt mentions 'URL paths,' 'HTTP headers,' or 'microservices architecture,' your brain should immediately jump to ALB. Just remember that while it's flexible, the overhead of Layer 7 processing means it won't match the raw speed of a Layer 4 balancer.
Why is NLB the go-to for static IP requirements?
Here is a classic SAA-C03 'gotcha': the need for a static IP. ALBs provide a DNS name, and the underlying IP addresses can change. If your client has a strict firewall that only allows traffic from a specific, unchanging IP address, an ALB won't cut it. The NLB allows you to assign an Elastic IP (EIP) to each Availability Zone, giving you a fixed entry point that never changes.
Beyond static IPs, the NLB is designed for TCP, UDP, and TLS traffic. If you're building a gaming server, a financial trading platform, or any application where every millisecond counts, the NLB is your best bet. It handles sudden, volatile traffic spikes much more gracefully than the ALB, which requires a brief 'warming' period for massive surges.
How do latency and throughput impact your ELB choice?
In the real world—and on the exam—performance metrics drive the architecture. The NLB is built for extreme scale. We're talking about handling millions of requests per second while maintaining microsecond latency. It's a lean machine that passes traffic through with minimal interference, making it ideal for high-throughput scenarios where the application logic handles the routing.
ALB, while highly performant, introduces slightly more latency because it has to terminate the connection, inspect the packet, and then forward it. For 95% of web apps, this is negligible. However, if the exam scenario emphasizes 'ultra-low latency' or 'extreme throughput' for non-HTTP protocols, the NLB is the only correct answer. Always look for those specific keywords to avoid the distractors.
How do you tackle these concepts for the SAA-C03 exam?
Understanding the theory is one thing, but applying it under exam pressure is another. The SAA-C03 doesn't just ask 'What is an ALB?'; it gives you a complex scenario and asks you to choose the most cost-effective and performant solution. You need to practice recognizing the patterns that trigger an NLB vs. an ALB choice.
This is exactly why we built Cert Sensei. We offer 1,000 expert-curated AWS Solutions Architect Associate (SAA-C03) practice questions that mirror the actual exam's difficulty. Instead of just giving you a correct letter, we provide detailed expert reasoning for every answer, helping you understand the 'why' behind the architecture. Plus, our domain-level analytics show you exactly where you're weak—whether it's Networking or Storage—so you can stop wasting time on what you already know.
❓ Frequently Asked Questions
Can I put an NLB in front of an ALB to get a static IP?
Yes, this is a common architectural pattern. You use the NLB to provide a static IP entry point and then route that traffic to an ALB to take advantage of Layer 7 path-based routing. It gives you the best of both worlds: fixed IPs and intelligent routing.
Does the ALB support non-HTTP traffic like MQTT or SSH?
No, the ALB is strictly for HTTP, HTTPS, and gRPC. If you need to load balance SSH (Port 22), RDP, or any other raw TCP/UDP traffic, you must use a Network Load Balancer (NLB).
Which load balancer is better for handling sudden, massive traffic spikes?
The NLB is superior for sudden spikes because it is designed to handle millions of requests per second instantly. ALBs can scale, but they may require a 'warm-up' period if the traffic increase is instantaneous and massive.