Backend Server Overview

Updated on 2025-01-20 GMT+08:00

View PDF

Backend servers receive and process requests from the associated load balancer.

If the incoming traffic increases, you can add more backend servers to ensure the stability and reliability of applications and eliminate SPOFs. If the incoming traffic decreases, you can remove some backend servers to reduce the cost.

If the load balancer is associated with an AS group, instances are automatically added to or removed from the load balancer.

Different types of backend servers can be added to different types of backend server groups as described in Table 1.

**Table 1** Backend server group and backend server types
Backend Server Group Type	Backend Server Types	Reference
Hybrid	Cloud servers or supplementary network interfaces that are in the same VPC as the load balancer, if IP as a Backend is disabled IP addresses of servers in other VPCs or in your on-premises data center, if IP as a Backend is enabled NOTE: When you create a hybrid backend server group, you must specify a VPC and associate the backend server group with a load balancer in this VPC.	Adding Backend Servers in the Same VPC as a Load Balancer Adding Backend Servers in a Different VPC from a Load Balancer
IP as a backend server	IP addresses of cloud or on-premises servers NOTE: IP as a Backend must have been enabled for the load balancer.	Adding Backend Servers in a Different VPC from a Load Balancer

Precautions

It is recommended that you select backend servers running the same OS for easier management and maintenance.

The load balancer checks the health of each server added to the associated backend server group if you have configured health check for the backend server group. If the backend server responds normally, the load balancer will consider it healthy. If the backend server does not respond normally, the load balancer will periodically check its health until the backend server is considered healthy.
If a backend server is stopped or restarted, connections established with the server will be disconnected, and data being transmitted over these connections will be lost. To avoid this from happening, configure the retry function on the clients to prevent data loss.
If you enable sticky sessions, traffic to backend servers may be unbalanced. If this happens, disable sticky sessions and check the requests received by each backend server.
You can adjust the number of backend servers associated with a load balancer at any time. You can also change the type of backend servers according to your service needs. To ensure service stability, ensure that the load balancer can perform health checks normally, and at least one backend server that is running properly has been added to the load balancer.

Notes and Constraints

A maximum of 500 backend servers can be added to a backend server group.
Inbound security group rules must be configured to allow traffic over the port of each backend server and health check port. For details, see Security Group and Network ACL Rules.
If you select only network load balancing, a server cannot serve as both a backend server and a client.

Backend Server Weights

You need to set a weight for each backend server in a backend server group to receive requests. The higher the weight you have configured for a backend server, the more requests the backend server receives.

You can set an integer from 0 to 100. If you set the weight of a backend server to 0, new requests will not be routed to this server.

Three load balancing algorithms allow you to set weights to backend servers, as shown in the following table. For more information about load balancing algorithms, see Load Balancing Algorithms.

**Table 2** Server weights in different load balancing algorithms
Load Balancing Algorithm	Weight Setting
Weighted round robin	If none of the backend servers have a weight of 0, the load balancer routes requests to backend servers based on their weights. Backend servers with higher weights receive proportionately more requests. If two backend servers have the same weights, they receive the same number of requests.
Weighted least connections	If none of the backend servers have a weight of 0, the load balancer calculates the load of each backend server using the formula (Overhead = Number of current connections/Backend server weight). The load balancer routes requests to the backend server with the lowest overhead.
Source IP hash	If none of the backend servers have a weight of 0, requests from the same client are routed to the same backend server within a period of time. If the weight of a backend server is 0, no requests are routed to this backend server.

Parent Topic: Backend Server

Previous topic: Backend Server

Next topic: Security Group and Network ACL Rules

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot