Help & DocumentationCloud Load BalancerProduct IntroductionApplication and Conventional CLB comparison

Application and Conventional CLB comparison

Last updated: 2019-08-06 19:21:10

PDF

Prices and Product Positioning of Cloud Load Balancer Instances

Cloud Load Balancer Product Positioning

When selecting products, you can refer to the following product positioning of application and conventional cloud load balancer products:

Product Type Application Cloud Load Balancer Conventional Cloud Load Balancer
Public Network Private Network Public Network Private Network
Layer-7 forwarding (HTTP/HTTPS)
Layer-4 forwarding (TCP/UDP)
HTTP/2 and websocket (secure) supported
Cloud Load Balance Policy ip hash (Layer-7)
Weighted Round-Robin Scheduling
Weighted Least Connections Scheduling
ip hash (Layer-7)
Weighted Round-Robin Scheduling
Weighted Least Connections Scheduling
ip hash (Layer-7)
Weighted Round-Robin Scheduling
Weighted Least Connections Scheduling
Weighted Round-Robin Scheduling
Session Persistence
Health Check
Custom Forwarding Rules (Domain Name/URL)
Forwarding to Different Backend Ports
Redirection (rewrite)
Cross-region binding
Logs storage in COS ✔ (Layer-7) Available soon ✔ (Layer-7)

Note: When a user cancels cloud load balance service in advance, the corresponding charges will be deducted from blocked balance in the user account according to the actual usage period. The remaining balance will be returned to the account.

Cloud Load Balance Bandwidth Fee

Bandwidth Fee Billing Scenario

1) CVM is paid by bandwidth: Consumed bandwidth is public network bandwidth already contained in the CVM. No additional bandwidth fee will be charged;
2) CVM is paid by traffic: Public network cloud load balancer used by the user will cause traffic, which will incur a corresponding cost.

Bandwidth Fee Billing Standard

In the above mentioned scenario 2), the actual bandwidth fee for using CLB refers to the network fee incurred by backend CVMs. For more information on the billing mode, please see Network Billing.