tencent cloud

Cloud Load Balancer

Release Notes and Announcements
CLB Release Notes
Product Announcements
Product Introduction
Overview
Strengths
Use Cases
Principles
Product Comparison
Use Limits
Service Regions and Service Providers
Purchase Guide
Billing Overview
Billing
CLB Resource Package
Purchase Methods
Payment Overdue
Product Attribute Selection
Getting Started
Getting Started with Domain Name-Based CLB
Getting Started with CLB
Getting Started with IPv6 CLB
Deploying Nginx on CentOS
Deploying Java Web on CentOS
Operation Guide
CLB Instance
CLB Listener
Real Server
Health Check
Certificate Management
Log Management
Monitoring and Alarm
Cloud Access Management
Classic CLB
Practical Tutorial
Deploy certificate to CLB (mutual authentication)
Enabling Gzip Compression & Testing
HTTPS Forwarding Configurations
Obtaining Real Client IPs
Best Practices for Configuring Load Balancing Monitoring Alerts
Implementing HA Across Multiple AZs
Load Balancing Algorithm Selection and Weight Configuration Examples
Configuring WAF protection for CLB listening domain names
Configure IAP to authenticate web access to the CLB domain and path
Configure IAP to authenticate programmatic access to CLB's domain and path
Ops Guide
Solution to Excessive Clients in TIME_WAIT Status
Load Balancer HTTPS Service Performance Test
Stress Testing FAQ
CLB Certificate Operation Permissions
Troubleshooting
UDP Health Check Exception
API Documentation
History
Introduction
API Category
Instance APIs
Listener APIs
Backend Service APIs
Target Group APIs
Redirection APIs
Other APIs
Classic CLB APIs
Load Balancing APIs
Making API Requests
Data Types
Error Codes
CLB API 2017
FAQs
Billing
CLB Configuration
Troubleshooting Health Check Issues
HTTPS
WS/WSS Protocol Support
HTTP/2 Protocol Support
Default Domain Name Blocking Prompt
Service Level Agreement
Contact Us
Glossary
DocumentationCloud Load BalancerProduct IntroductionProduct ComparisonInstance Types Comparison

Instance Types Comparison

PDF
Focus Mode
Font Size
Last updated: 2025-11-19 11:09:28
CLB offers two types of instances: CLB (formerly "application CLB") and Classic CLB.
CLB supports TCP/UDP/HTTP/HTTPS protocols to provide flexible forwarding capabilities based on domain names and URL paths.
Classic CLB does not support HTTP/HTTPS protocols on the private network but is easy to configure.
CLB has all features of Classic CLB. Given their product features and performance, we recommend that you use CLB. For a detailed comparison, please see below:
Product Type
CLB
Classic CLB
Public network
Private network
Public network
Private network
Layer-7 forwarding (HTTP/HTTPS)
✓
✓
✓
×
Layer-4 forwarding (TCP/UDP)
✓
✓
✓
✓
Encrypted Layer-4 forwarding (TCP SSL)
✓
✓
×
×
HTTP/2 and WebSocket (Secure) support
✓
✓
✓
×
Load balancing policy
IP hash (Layer-7)Weighted round-robinWeighted least-connection scheduling
IP hash (Layer-7)Weighted round-robinWeighted least-connection scheduling
IP hash (Layer-7)Weighted round-robinWeighted least-connection scheduling
Weighted round-robin
Session persistence
✓
✓
✓
✓
Health check
✓
✓
✓
✓
Custom forwarding rule (domain name/URL)
✓
✓
×
×
SNI multi-certificate support
✓
✓
×
×
Forwarding to different real ports
✓
✓
×
×
Custom Layer-7 configuration
✓
✓
×
×
Layer-7 redirect (rewrite)
✓
✓
×
×
Cross-region binding support
✓
✓
×
×
Storing Layer-7 access logs in CLS
✓
✓
✓
×
Note:
CLB instance: a CLB instance supports enabling or disabling the HTTP/2 protocol. For more information, see Configuring an HTTPS Listener.
Classic CLB instance: HTTPS listeners created for Classic CLB before April 2018 do not support the HTTP/2 protocol. HTTPS listeners created after April 2018 support but cannot disable the HTTP/2 protocol.


Previous Topic: PrinciplesNext Topic: Instance Specifications Comparison

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback