Business challenges
-Traffic surges by 10 to 100 times during large‑scale promotional events, which cannot be handled by fixed‑capacity resources.
-Static/dynamic resources are mixed, causing immense pressure on the origin server.
-A single-AZ failure makes the entire site unavailable, resulting in severe losses.
- A single instance can handle millions of QPS and tens of millions of concurrent connections, coping with sudden traffic spikes with ease. Combined with AS, it achieves automatic scaling.
- Intelligent traffic distribution: Requests are precisely and evenly distributed to multiple real servers based on domain names/paths, reducing response latency caused by single-point overload.
- Health check+fault isolation: Abnormal nodes are automatically identified and traffic is quickly shifted away, reducing manual intervention.
- Cross-AZ disaster recovery: It is recommended to bind cross-AZ real server groups to achieve AZ-level disaster recovery and ensure business continuity.
- Traffic ratios between new and earlier versions are precisely controlled based on target group weight allocation (for example, 5% → 20% → 50% → 100%)
- Forwarding rules based on Header/Cookie are supported to direct specific users to the new version. X-Version (example): The canary rule routes 5% of traffic to the new version for validation and observation
- In case of exceptions, rules can be adjusted within seconds to roll back to an earlier version, with almost no perception by end users throughout the process
- The progressive release mechanism significantly reduces version iteration risks, making it suitable for production environments with frequent updates
GWLB is a CLB service that runs at the network layer. GWLB instances help you deploy, scale up, and manage third-party virtual appliances such as firewalls, intrusion detection and prevention systems, and analytics and visibility tools, with simpler operations and higher security.
By associating an EIP with an endpoint, you can use the private link to connect access from the public network to the VPC network where the GWLB instance resides, so as to directly deploy third-party virtual appliances, such as firewalls, in the path of the network data. In this way, all data packets will be checked and processed by the firewall to prevent malicious data from entering the network, protecting internal resources from attacks.
GWLB is a CLB service that runs at the network layer. GWLB instances help you deploy, scale up, and manage third-party virtual appliances such as firewalls, intrusion detection and prevention systems, and analytics and visibility tools, with simpler operations and higher security.
GWLB works with third-party virtual appliances such as firewalls to inspect inbound and outbound traffic while ensuring high availability across AZs. GWLB uses the GENEVE protocol to communicate with firewalls, forwards received traffic to a group of backend firewalls, and provides management features such as health checks and load balancing.
