هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Using a Dedicated Load Balancer

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

If you are using a dedicated load balancer for the first time, you can start from this section.

ELB automatically distributes incoming traffic across multiple backend servers based on the routing policies you configure. It expands the service capabilities of your applications and improves their availability by eliminating single points of failure (SPOFs).

ELB Architecture

Figure 1 ELB architecture
Table 1 ELB components

Component

Description

Reference

Load balancer

Distributes incoming traffic across backend servers in one or more AZs.

Before using a load balancer, you need to add at least one listener to it.

Dedicated Load Balancer Overview

Listener

Works as the minimum service unit. It uses a protocol and port (for example, TCP port 80) you have specified to check requests from clients and route the requests to associated backend servers.

Each load balancer must have at least one listener to check and distribute traffic. You can add different types of listeners to distribute traffic using different protocols and ports.

Network listeners forward traffic to the default backend server group, while application listeners forward traffic based on the forwarding policies you configure.

Listener Overview

Forwarding policy

Determines how application load balancers distribute traffic across one or more backend server groups. Forwarding policies can be only configured for application listeners.

Application load balancers distribute Layer 7 requests more efficiently. They support various protocols and forwarding policies to suit your service needs.

Advanced Forwarding

Backend server group

Contains one or more backend servers to process requests distributed by load balancers.

A backend server group can be created independently. A backend server group can be associated with one or more load balancers.

Backend Server Group Overview

Backend server

Processes client requests. A backend server can be an ECS, BMS, supplementary network interface, or IP address. If a supplementary network interface or an IP address is added as a backend server, the server with the supplementary network interface attached or using the IP address processes client requests.

ELB periodically sends requests to backend servers to check whether they can process requests. This process is called health check. If a backend server is identified as unhealthy, the load balancer will stop routing requests to it.

Backend Server Overview

Procedure for Using a Dedicated Load Balancer

The following describes how to quickly create and use a dedicated load balancer.

Figure 2 Procedure for using a dedicated load balancer

Procedure

What to Do

Creating a Dedicated Load Balancer

Create a dedicated load balancer and be careful with the following configurations:

  • Basic information: type, billing mode, region, and AZ.
  • Specifications: elastic or fixed specifications; network or application load balancing, or both.
  • Network configuration: network type (private IPv4 or IPv6), VPC, and subnet planning.

Creating a Backend Server Group

Create a backend server group and add backend servers to the group for easier management and scheduling.

You can create a backend server group first and select it when creating a dedicated load balancer. Plan the backend protocol appropriately because the backend protocol of each backend server group must match the frontend protocol of the associated listeners.

Add listeners and choose the protocols and ports based on service requirements.

  • Application listeners (HTTP/HTTPS/QUIC): work well for workloads that require high performance at Layer 7, such as real-time audio and video, interactive livestreaming, and game applications.
  • Networking listeners (TCP/UDP/TLS): are good for heavy-traffic and high-concurrency workloads at Layer 4, such as file transfer, instant messaging, and online video applications.

Advanced Forwarding

Configure advanced forwarding policies for application listeners to forward traffic to specified backend server groups based on the domain name, path, HTTP request method, HTTP header, query string, and CIDR block.

Backend Server Group and Listener Protocols

You can associate a backend server group with different listeners or different dedicated load balancers under the same enterprise project.

The backend protocol of each backend server group must match the frontend protocol of the associated listeners as described in Table 2.

Table 2 The frontend and backend protocol

Load Balancer Specification

Frontend Protocol

Backend Protocol

Network load balancing

TCP

TCP

Network load balancing

UDP

  • UDP
  • QUIC

Network load balancing

TLS

  • TLS
  • TCP

Application load balancing

HTTP

HTTP

Application load balancing

HTTPS

  • HTTP
  • HTTPS
  • gRPC

Application load balancing

QUIC

  • HTTP
  • HTTPS
  • gRPC
NOTE:

TLS, gRPC, and QUIC will be available in more regions. You can see which regions support them on the console.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback