Load Balancing
Azure Load Balancer
Layer 4 load balancing for inbound and outbound flows.
Azure
Service information
Shortname: Azure LB
Huawei equivalent shortnames: ELB
Keywords: load balancer, network, traffic
Differences vs Huawei
- SKU and availability zone behavior differ.
Migration to Huawei
- Map API/workflow stages, integration points, pipeline gates, and release controls. For Azure Azure Load Balancer, the direct Huawei equivalence layer is ELB; validate feature-by-feature parity for control plane, data plane, and operational behavior before cutover.
- Use a composed Huawei migration pattern where needed: ELB + EIP + WAF. Treat ELB as the core equivalent capability and use the additional services to cover integration, security, observability, and governance gaps.
- Pricing model difference: Azure usually bills load balancer rules/data processing and related public IP usage; Huawei usually bills CodeArts/APIG/DMS runtime or request volume plus artifact/storage usage. Recalculate TCO with peak load, request volume, retention period, and cross-region/interconnect traffic before production migration.
Huawei Cloud
Huawei equivalent service
Shortname: ELB
General function: Load Balancing
Layer 4/7 load balancing service.
Keywords: load balancer, traffic, lb