Network Load Balancers (Layer 4)
What you'll learn: How network load balancers work at the TCP/UDP transport layer to deliver ultra-low latency and massive throughput.
What Makes Layer 4 Special
Unlike Layer 7 load balancers that inspect HTTP content, Network Load Balancers (NLBs) operate at the transport layer (OSI Layer 4). They make routing decisions based purely on TCP or UDP connection information—source/destination IP addresses and ports—without looking inside the packet payload.
Think of it like a highway traffic director who only reads license plates and exit numbers, never opening car trunks. This minimal inspection makes NLBs incredibly fast.
Core Characteristics
Ultra-Low Latency: Because NLBs don't parse application data, they add microseconds (not milliseconds) to connection time. They simply forward packets based on network-level information.
High Throughput: NLBs can handle millions of requests per second while maintaining static IP addresses. They're built for extreme performance scenarios like real-time gaming, financial trading platforms, or IoT device communications.
Connection-Based Routing: Once a TCP connection is established, all packets in that session flow to the same backend target. The NLB preserves the original client IP address, so your servers see the real source.
Protocol Support: NLBs work with any TCP or UDP traffic—not just HTTP/HTTPS. This includes databases, custom protocols, and non-web applications.
When to Use Network Load Balancers
Choose NLBs when you need maximum performance with minimal latency, when you're working with non-HTTP protocols, or when you require static IP addresses for whitelisting purposes. They're the speed champions of load balancing.
Key Takeaway: Network Load Balancers operate at Layer 4 (TCP/UDP), delivering ultra-low latency and millions of requests per second by routing based on connection information rather than inspecting application content.