Load Balancing

Load balancing (LB) distributes inbound traffics from a VIP to a group of backend VM instances, and then automatically detects and isolates unavailable VM instances, whereby enhancing the service capability and availability of your businesses.

• Load balancing automatically distributes your inbound application traffics to the preconfigured backend VM instances, thereby providing highly concurrent and highly reliable access services.
• In your practice, you can adjust the VM instances in load balancing listeners to improve your service capability, which will not affect your normal business access.
• A load balancing listener supports four types of protocols: TCP, HTTP, HTTPS, and UDP.
• If the listener protocol is HTTPS, you need to bind a certificate. Note that you can upload a certificate or a certificate link.
• A load balancer allows you to flexibly configure multiple forwarding policies to achieve advanced forwarding controlling.
• Load balancing allows you to display real-time SLB business traffics and connections in monitoring data.

Definitions related to load balancing:

• Frontend network: In load balancing network services, a frontend network is used to provide VIP networks. Public networks, flat networks, and VPC networks can be used as frontend networks.
• Backend network: In load balancing network services, a backend network is used to create a private network for backend VM instances. Flat networks, vRouter networks, and VPC networks can be used as backend networks.
• Internet load balancing: A public network is used as the frontend network to provide Internet-facing load balancing services through routers (VPC vRouters or vRouters).
  • A VPC network can be used as a backend network to provide Internet load balancing services based on a VPC network. In this scenario, multiple backend networks can be used. However, these backend networks must be attached to the same VPC vRouter.
  • A vRouter network can be used as a backend network to provide Internet-facing load balancing services based on a vRouter network. In this scenario, make sure that the frontend network and the L3 network attached to the vRouter are the same.
  • A flat network can be used as a backend network to provide Internet-facing load balancing services based on a flat network. In this scenario, the frontend network and the L3 network attached to the vRouter must be the same.
• Intranet load balancing (VPC private network): A VPC network is used as the frontend network to provide intranet load balancing services through VPC vRouters.
  • A VPC network that shares the same VPC vRouter with a frontend network can be used as a backend network to provide intranet load balancing services based on VPC networks.
  • In this scenario, multiple backend networks can be used. However, these backend networks must be attached to the same VPC vRouter.
• Intranet load balancing (flat network): A flat network is used as the frontend network to provide intranet load balancing services through vRouters.
  • A frontend network can be also used as a backend network to provide intranet load balancing services based on flat networks. In this scenario, the L3 network specified in the vRouter offering that is attached to the frontend network can be either a public network or a flat network.
  • Other flat networks can be also used as a backend network to provide intranet load balancing services based on flat networks. In this scenario, the frontend network and the L3 network attached to the vRouter must be the same.
  Note: To use intranet load balancing (flat network) services, attach a vRouter offering to the flat network in advance.