Compared with Classic Load Balancer (CLB), Network Load Balancer (NLB) supports higher-performance Layer 4 load balancing capabilities. NLB has many advanced features, including highly concurrent connection processing, SSL offloading for TCP traffic, and connection throttling. This topic summarizes the benefits of migrating from CLB to NLB.
Benefits
If you migrate workloads from CLB to NLB, you can enjoy the following benefits:
Each NLB instance supports higher bandwidth and concurrency, with the ability to automatically scale in and scale out resources. This enables NLB to easily handle high incoming traffic over the Internet and highly concurrent connections from Internet of Things (IoT) devices.
NLB provides higher availability and elasticity. It supports assigning private IP addresses and Elastic IP addresses (EIPs) to an instance for a specified zone. This helps your application or service better respond to access requests.
NLB supports TCP/SSL listeners, which enhance security and offer encrypted communication capabilities.
NLB enables cross-region and hybrid-cloud-based load balancing for server groups of the IP type.
NLB supports cross-zone deployment, offering stronger zone-disaster recovery capabilities than CLB, including user-triggered switchover and automatic failover.
NLB has higher availability (dual-zone deployment with an availability of 99.995%).
NLB can listen for requests destined for all ports, making it ideal for scenarios where many ports or dynamically assigned ports are used.
NLB integrates virtual IP address-level (or zone-level) monitoring, allowing more precise monitoring of traffic distribution.
NLB supports various IPv6 features, including dual-stack networking, and IPv6-to-IPv4 and IPv6-to-IPv6 forwarding.
For more information about the functional differences between NLB and CLB, see Functions and features.
Reference
For a tutorial on migrating from CLB to NLB, see Best practices for manually migrating Layer 4 listeners from CLB to NLB.