Introduction to the SLB product family

更新时间:
复制 MD 格式

Server Load Balancer (SLB) distributes incoming traffic across a pool of backend servers to increase the throughput of your applications, eliminate single points of failure, and improve application availability. The SLB product family includes Application Load Balancer (ALB), Network Load Balancer (NLB), and Classic Load Balancer (CLB). You can choose the load balancing product that best fits your business requirements.

Product overview

Alibaba Cloud provides a fully managed online load balancing service that is ready to use, high-capacity, stable, reliable, and elastic. The service uses a pay-as-you-go model, making it ideal for large-scale internet applications and high-concurrency scenarios, such as online promotions, flash sales, and massive IoT applications. Unlike hardware load balancers, SLB handles massive traffic spikes without requiring a large upfront investment. Unlike self-managed open-source solutions, Alibaba Cloud SLB is stable, reliable, and supported by a professional operations team. Free, 24/7 technical support is available to help you improve O&M efficiency.

Product types

image

Alibaba Cloud SLB supports the following types of load balancers:

  • Application Load Balancer (ALB): Designed for Layer 7, ALB provides high-performance traffic processing, such as HTTPS offloading. A single instance can handle up to 1 million queries per second (QPS). ALB also offers advanced content-based routing features, such as forwarding, redirection, and rewriting based on HTTP headers, cookies, and query strings. It is the official cloud-native Ingress gateway on Alibaba Cloud. For more information, see What is Application Load Balancer (ALB).

  • Network Load Balancer (NLB) is a next-generation Layer 4 load balancer designed for the Internet of Things (IoT). It supports ultra-high performance and automatic elasticity, with a single instance capable of handling up to 100 million concurrent connections. For scenarios such as large-scale device connections, high-concurrency messaging services, and audio and video streaming, NLB offers advanced features such as TCPSSL offloading, rate limiting for new connections, and listening on all ports. It also provides tools for IoT scenarios, such as MQTTS encryption offloading. For more information, see What is Network Load Balancer (NLB).

  • Classic Load Balancer (CLB): Supports the TCP, UDP, HTTP, and HTTPS protocols. It provides robust Layer 4 and basic Layer 7 processing. For more information, see What is Classic Load Balancer (CLB).

Feature comparison

Item

ALB

NLB

CLB

Service focus

  • Layer 7 processing and advanced routing features

  • Focuses on application-layer protocols such as HTTP, HTTPS, and QUIC

  • Optimized for application delivery

  • Layer 4 processing and large-scale SSL offloading

  • Focuses on TCP, UDP, and TCPSSL protocols

  • Optimized for network delivery

  • Robust Layer 4 and basic Layer 7 processing capabilities

  • Supports TCP, UDP, HTTP, and HTTPS protocols

Architecture and performance

  • Built on a Network Functions Virtualization (NFV) platform and supports elastic scaling

  • Up to 1 million QPS per instance

  • Built on an NFV platform, independent of physical machines, and supports elastic and rapid scaling

  • Up to 100 million concurrent connections per instance

  • Built on a physical machine architecture

  • Up to 1 million concurrent connections and 50,000 QPS per instance

Forwarding capabilities

  • Rich Layer 7 features and content-based routing

  • HTTP header modification, redirection, rewriting, and rate limiting

  • Advanced Layer 4 features and TCPSSL offloading

  • Traffic surge rate limiting, connection draining, and Anyport

  • Basic Layer 4 and Layer 7 capabilities

  • Supports only domain-based or URL-based forwarding

Backend server type

  • Elastic Compute Service (ECS) instances

  • elastic network interfaces

  • elastic container instances

  • IP addresses

  • Function Compute

  • Elastic Compute Service (ECS) instances

  • elastic network interfaces

  • elastic container instances

  • IP addresses

  • Elastic Compute Service (ECS) instances

  • elastic network interfaces

  • elastic container instances

O&M capabilities

  • Automatic scaling

  • Processing capacity automatically scales with traffic, requiring no manual intervention

  • Automatic scaling

  • Processing capacity automatically scales with traffic, requiring no manual intervention

  • You must manually manage the specifications of pay-by-specification instances.

  • You must also estimate traffic peaks.

Cloud-native integration

  • Cloud-native Ingress gateway

  • Traffic splitting, traffic mirroring, canary release, and blue-green deployment

Supports integration with ACK/ASK (Version 1.24 and later)

Limited support; requires integration with Alibaba Cloud container services such as ACK or ASK

Use cases

  • High-performance, auto-scaling Layer 7 load balancing for internet applications

  • High-traffic, low-latency scenarios for audio and video applications

  • canary release and blue-green deployment for cloud-native applications

  • High-traffic, high-concurrency Layer 4 business scenarios

  • Entry points for IoT services such as Internet of Vehicles (IoV) and smart home

  • Multi-active disaster recovery and hybrid cloud ingress/egress for data centers

  • High-reliability Layer 4 traffic distribution for websites and applications

  • High-concurrency, high-performance network traffic distribution

  • Intra-city and cross-region disaster recovery

Billing comparison

The following section describes the billing for ALB, NLB, and CLB.

ALB billing

image
  • For more information about ALB resource plans, see ALB resource plans.

  • For more information about the pricing and billing of pay-as-you-go ALB instances, see ALB billing rules.

NLB billing

  • For more information about NLB resource plans, see NLB resource plans.

  • For more information about the pricing and billing of pay-as-you-go NLB instances, see NLB billing rules.

CLB billing

The following figure shows the billing components for pay-as-you-go CLB instances. For more information about the pricing and billing of pay-as-you-go CLB instances, see Pay-as-you-go.

image

Beginning 00:00:00 (UTC+8), December 1, 2024, subscription CLB instances are no longer available for purchase. For more information, see End of sale for subscription CLB instances.

Subscription CLB billing components

The following figure shows the billing components for subscription CLB instances. For more information about the pricing and billing of subscription CLB instances, see Subscription (no longer available for new purchases).

The following table compares the Load Balancer Capacity Unit (LCU) pricing and definitions for ALB, NLB, and CLB.

Service

LCU unit price

Unit: CNY/LCU/hour

LCU definition

References

Application Load Balancer ALB

0.049

One ALB LCU includes:

  • 25 new connections per second

  • 3,000 concurrent connections (sampled per minute)

  • 1 GB of request and response data transfer per hour

  • 1,000 rule evaluations per hour

    Note

    The number of forwarding rules, lines of AScript code, and additional certificates determine the number of rule evaluations. The free tier for each of these three metrics is 25.

LCU fee

Network Load Balancer NLB

0.037

For TCP traffic, one NLB LCU includes:

  • 800 new TCP connections per second

  • 100,000 concurrent TCP connections (sampled per minute)

  • 1 GB of TCP request and response data transfer per hour

For UDP traffic, one NLB LCU includes:

  • 400 new UDP connections per second

  • 50,000 concurrent UDP connections (sampled per minute)

  • 1 GB of UDP request and response data transfer per hour

For TCPSSL traffic, one NLB LCU includes:

  • 50 new TCPSSL connections per second

  • 3,000 concurrent TCPSSL connections (sampled per minute)

  • 1 GB of TCPSSL request and response data transfer per hour

LCU fee

Classic Load Balancer CLB

0.049

For TCP traffic, one CLB LCU includes:

  • 800 new TCP connections per second

  • 100,000 concurrent TCP connections (sampled per minute)

  • 1 GB of TCP request and response data transfer per hour

For UDP traffic, one CLB LCU includes:

  • 400 new UDP connections per second

  • 50,000 concurrent UDP connections (sampled per minute)

  • 1 GB of UDP request and response data transfer per hour

For HTTP(S) traffic, one CLB LCU includes:

  • 25 new HTTP(S) connections per second

  • 3,000 concurrent HTTP(S) connections (sampled per minute)

  • 1 GB of HTTP(S) request and response data transfer per hour

  • 1,000 rule evaluations per hour

    Note

    The number of rule evaluations is determined by the number of forwarding rules. The free tier is 25.

LCU & Specification fee

Benefits

Support for multiple protocols

Supports a wide range of protocols to meet diverse application needs.

  • Basic protocols: Supports Layer 4 load balancing for TCP and UDP, and Layer 7 load balancing for HTTP and HTTPS.

  • Advanced protocols:

    • ALB: Supports QUIC, which is ideal for audio, video, and mobile internet applications. It also supports gRPC for efficient API communication between microservices.

    • NLB: Supports TCPSSL, allowing for centralized management and offloading of SSL certificates, which improves the processing efficiency of backend services.

Multi-level disaster recovery

Provides multiple layers of disaster recovery and high availability.

  • Health checks periodically monitor backend servers. If a server is found to be unhealthy, SLB stops forwarding traffic to that instance to ensure service availability.

  • Multi-availability zone: SLB can be deployed across multiple availability zones within a region to implement intra-city disaster recovery.

  • Session synchronization uses a cluster deployment to synchronize sessions across servers. This design supports hot upgrades and prevents a single point of failure from disrupting your service.

Enhanced security and reliability

SLB includes built-in security features to reduce your security overhead.

  • Network-layer security: Layer 4 load balancing provides protection against DDoS, SYN Flood, UDP Flood, ACK Flood, ICMP Flood, and DNS Flood attacks.

  • Application-layer security: In addition to Layer 4 security, Layer 7 load balancing can be integrated with Web Application Firewall (WAF) with a single click for enhanced application reliability.

  • Certificate management: Provides a centralized certificate management system for HTTPS, QUIC, and TCPSSL protocols to ensure secure and reliable data transmission.

Guaranteed performance

Offers powerful traffic distribution and various routing functions to guarantee performance.

  • Performance-guaranteed instances: CLB offers performance-guaranteed instances that provide performance isolation between different instances and ensure performance based on the selected specification.

  • Elastic capacity: A single ALB instance supports up to 1 million QPS, while a single NLB instance supports up to 100 million concurrent connections and 100 Gbps of bandwidth. They handle massive traffic volumes and automatically scale to manage sudden traffic spikes.

Flexible scheduling strategies

Provides multiple scheduling algorithms and forwarding modes to increase deployment flexibility.

  • Scheduling algorithms: Supports algorithms such as weighted round-robin, weighted least connections, source IP hash, 4-tuple hash, consistent hashing, and QUIC ID hash, allowing you to choose the most suitable algorithm to distribute user traffic.

  • Forwarding rules: Supports the configuration of forwarding rules for both requests and responses, enabling traffic scheduling based on different conditions and actions to improve application flexibility.

Flexible management and payment options

Choose instance types and payment methods that fit your business needs, and easily manage your load balancers through various channels.

  • Flexible management: Create, configure, and manage load balancers through the management console, OpenAPI, and SDKs.

  • Multiple payment methods: Choose between pay-as-you-go and subscription billing models. You can pay by data transfer or by fixed bandwidth.

Related documents