Server Load Balancer (SLB) is a service that distributes incoming traffic across backend server groups to increase the throughput of your applications. SLB can also be used to eliminate single points of failure (SPOFs) and improve the availability of applications.
SLB is a fully managed load balancing service provided by Alibaba Cloud. It can be used out-of-the-box and provides elastic, stable, reliable, and high-throughput load balancing services. You can scale SLB resources along with the changes to your business and pay only for what you use. SLB is designed to balance the heavy loads of hyper-scale Internet applications. For example, you can use SLB to handle traffic spikes during large-scale online promotions or improve the availability of Internet of Things (IoT) applications that receive a great number of concurrent connections. Compared with self-managed hardware load balancers, SLB can handle a great number of user requests in scenarios such as large-scale promotional events without the need for large upfront investments. Compared with self-managed, open source software load balancers, SLB is maintained around the clock by an experienced and professional technical team. This ensures service stability and improves O&M efficiency.
SLB instance types
- Application Load Balancer (ALB): provides ultra-high Layer 7 processing capabilities such as SSL offloading for HTTPS traffic. Each ALB instance can serve up to one million queries per second (QPS). An ALB instance serves as a cloud-native gateway on Alibaba Cloud and provides advanced content-based routing features. ALB instances can forward, redirect, and rewrite messages based on user-defined HTTP headers, cookies, and query strings. For more information, see What is ALB?.
- Network Load Balancer (NLB): designed to connect all things to the Internet. NLB is a Layer 4 load balancing service that offers ultra-high performance and can scale in response to network load. An NLB instance serves up to 100 million concurrent connections, which is ideal for services that require high concurrency. NLB provides multiple advanced features to cater to services that need to handle massive volumes of client requests, highly concurrent message services, and audio and video services. For example, NLB can perform SSL offloading for TCP traffic, limit the number of new connections, and listen on multiple ports. In addition, NLB can offload Message Queuing Telemetry Transport Secure (MQTTS) encryption from servers that host your IoT services. NLB can also handle traffic spikes by balancing the loads of IoT services. For more information, see What is NLB?.
- Classic Load Balancer (CLB): supports TCP, UDP, HTTP, and HTTPS. CLB provides advanced Layer 4 processing capabilities and basic Layer 7 processing capabilities. For more information, see What is CLB?.
|Architecture and performance|
|Backend server type|
|Cloud-native support||Supports integrating with Container Service for Kubernetes (ACK) and Serverless Kubernetes (ASK) (1.24 and later versions)||Must be used in combination with container services such as ACK and ASK|
The following section describes the billing methods and billable items of Application Load Balancer (ALB), Network Load Balancer (NLB), and Classic Load Balancer (CLB). You can view and learn about the billing methods and billable items of each service.
- For more information about the resource plans of ALB, see Introduction to ALB resource plans.
- For more information about the pricing rules of pay-as-you-go ALB instances, see ALB billing rules.
For more information about the pricing rules of pay-as-you-go NLB instances, see NLB billable items.
For more information about the pricing rules of pay-as-you-go CLB instances, see Pay-as-you-go.
|Instance type||Price per LCU|
(Unit: USD/hour/transit router)
|Application Load Balancer (ALB)||0.007||An ALB LCU provides resources for:||ALB billing rules|
|Network Load Balancer (NLB)||0.005|
For TCP data transfer, an NLB LCU provides resources for:
For UDP data transfer, an NLB LCU provides resources for:
For SSL over TCP data transfer, an NLB LCU provides resources for:
|NLB billing rules|
|Classic Load Balancer (CLB)||0.007|
For TCP data transfer, a CLB LCU provides resources for:
For UDP data transfer, a CLB LCU provides resources for:
For HTTP or HTTPS data transfer, a CLB LCU provides resources for:
|Specification fee and LCU fee|
- Basic protocols: SLB supports Layer 4 load balancing over TCP or UDP and Layer 7 load balancing over HTTP or HTTPS.
- Advanced protocols:
- ALB supports the QUIC protocol. QUIC is an advanced protocol that ensures faster and safer transmission for audio, video, and mobile applications. In addition, ALB also supports Google Remote Procedure Call (gRPC) to implement more efficient service calls between microservices.
- NLB supports SSL over TCP and can manage SSL certificates and offload SSL processing from backend servers. This improves the performance of backend servers.
Multi-level disaster recovery
- Monitors the health status of backend servers on a regular basis. SLB does not distribute network traffic to unhealthy backend servers. This ensures the availability of your service.
- Supports multi-zone deployment in specific regions to provide zone-disaster recovery.
- Supports session synchronization. Backend servers are grouped into a cluster and sessions to these backend servers are synchronized to eliminate SPOFs. In addition, hot upgrades are also supported to prevent service disruptions.
Higher security and reliability
- Network layer security: Layer 4 SLB protects your service from DDoS, SYN flood, UDP flood, ACK flood, ICMP flood, and DNS flood attacks.
- Application layer security: Layer 7 SLB protects your service from attacks at Layer 4 and Layer 7, and can be integrated with Web Application Firewall (WAF) to protect your service at the application layer.
- Certificate management: SLB provides certificate management for HTTPS, QUIC, and SSL over TCP to ensure the stability and security of data transmission.
- High performance: Alibaba Cloud offers a wide range of specifications for high-performance CLB instances to cater to various business requirements.
- High elasticity: An ALB instance supports up to one million QPS. An NLB instance supports up to 100 million concurrent connections, 100 Gbit/s throughput, and one million QPS. Both types of instances can handle massive amounts of client requests and scale along with your business.
- Supports multiple scheduling algorithms, such as weighted round-robin, weighted least connections, and consistent hashing based on source IP addresses, the combination of four elements, and QUIC IDs. You can select the most suitable scheduling algorithms based on your business requirements.
- Supports configuring inbound and outbound forwarding rules. SLB distributes network traffic across backend servers based on forwarding rules. This allows SLB to route network traffic to applications in a more flexible manner.
Flexible management and billing
- Flexible management: You can create, configure, and manage SLB instances in the console, by calling API operations in OpenAPI Explorer, or by using Alibaba Cloud SDKs.
- Flexible billing: SLB supports the subscription and pay-as-you-go billing methods, and the pay-by-data-transfer and pay-by-bandwidth metering methods.