The Application Load Balancer (Application Load Balancer (ALB)) service provided by Alibaba Cloud is intended for load balancing at the application layer and supports protocols such as HTTP, HTTPS, and Quick UDP Internet Connections (QUIC). ALB offers high elasticity and can process a heavy load of network traffic at the application layer. As a cloud-native ingress gateway for Alibaba Cloud, ALB is deeply integrated with other cloud-native services and can route complex workloads.
Why Application Load Balancer (ALB)?
As a cloud-native ingress gateway for Alibaba Cloud, Application Load Balancer (ALB) is intended for Layer 7 load balancing over HTTP, HTTPS, and QUIC and provides advanced routing features.
High elasticity at Layer 7ALB is intended for Layer 7 load balancing and provides domain names and virtual IP addresses to handle large amounts of network traffic at multiple levels. ALB distributes network traffic across groups of backend servers and can automatically scale on demand to improve the service availability of your applications. You can use ALB to prevent service interruptions caused by single points of failure (SPOFs). ALB supports customized cross-zone deployment and elastic scaling across zones to remove resource bottlenecks in individual zones.
Advanced protocolsALB supports HTTP, HTTPS, and QUIC and can process a heavy load of network traffic. You can use ALB to accelerate and secure the access to mobile Internet applications such as real-time audio and video applications, interactive streaming applications, and online game applications. ALB supports Google Remote Procedure Call (gRPC) to facilitate efficient communication among microservices through APIs.
Content-based routingALB can route network traffic to different backend servers based on the request content such as the path, HTTP header, query string, HTTP request method, cookie, and source IP address. ALB also supports advanced configurations such as redirects, rewrites, and custom HTTPS headers.
Security and reliabilityALB supports DDoS mitigation and can be integrated with Web Application Firewall (WAF) to provide more security features. In addition, ALB supports end-to-end data transfer over HTTPS and cryptographic protocols such as TLS 1.3 to accelerate content delivery, protect your business-critical services, and comply with the Zero Trust security framework. You can also customize security policies as needed.
Cloud-nativeUsers in the Internet, finance, and enterprise sectors want to deploy their applications in the cloud or migrate their existing business systems to the cloud. As a cloud-native gateway for Alibaba Cloud, ALB is deeply integrated with Container Service for Kubernetes (ACK), Serverless App Engine (SAE), Function Compute, and Kubernetes (K8s).
Flexible billingALB uses elastic IP addresses (EIPs) and EIP bandwidth plans to provide Internet-facing services and supports flexible billing for Internet data transfer. ALB also supports the pay-by-LCU metering method, which allows you to pay on demand and reduces the cost of resource usage.
|Instance||Provides ultra-high Layer 7 processing capabilities and can increase the service capacity of your applications by distributing network traffic across different backend servers. Each ALB instance supports up to one million queries per second (QPS).|
|Listener||The smallest unit of ALB. You must specify the protocol and port for each listener to process different requests. For example, you can configure a listener of ALB to process HTTP requests on port 80. You must add at least one listener to each ALB instance before the ALB instance can distribute network traffic. You can add up to 50 listeners to each ALB instance to distribute network traffic for different workloads.|
|Forwarding rule||ALB distributes requests to one or more backend servers in server groups based on forwarding rules. ALB provides advanced routing features. In addition to the basic routing features, you can specify conditions such as the HTTP header, cookie, and HTTP method in a forwarding rule to route different network traffic to different backend servers.|
|Server group||Backend servers that are used to receive requests are specified in logical groups, which are referred to as server groups. Each server group contains one or more backend servers that process requests distributed by ALB. Server groups of ALB are independent from ALB. You can associate a server group with different ALB instances. You can specify up to 1,000 backend servers in each server group. ALB supports multiple types of backend servers. For example, you can specify Elastic Compute Service (ECS) instances, Elastic Container Instances (ECIs), and elastic network interfaces (ENIs) as backend servers.|
|Health check||ALB checks the availability of backend servers by performing health checks. If a backend server is declared unhealthy, ALB does not forward requests to the backend server until the backend server recovers. ALB supports flexible health check configurations. For example, you can specify the protocol, port, and thresholds for health checks. ALB provides health check templates that can be applied to different server groups.|
Alibaba Cloud provides Internet-facing and internal-facing ALB instances. You can specify the type of ALB instance based on your business requirements. Whether EIPs and EIP bandwidth plans are used is based on the specified type.
|EIP bandwidth plan||EIP bandwidth plans provide bandwidth sharing and transferring for resources that are created in the same region. EIP bandwidth plans support multiple metering methods such as pay-by-bandwidth and pay-by-enhanced-95th-percentile. You can use EIP bandwidth plans to reduce the costs of public bandwidth. Internet-facing ALB instances use EIPs and EIP bandwidth plans that support the pay-by-bandwidth and pay-by-enhanced-95th-percentile metering methods to provide Internet-facing services.|
|Domain name||A domain name that can be accessed over the Internet or private networks and can be resolved to the virtual IP address (VIP) of an ALB instance. You can also create a CNAME record to resolve a readable domain name to the domain name of ALB. For more information, see Configure a CNAME record.|
|EIP||EIPs are required only for Internet-facing ALB instances. You do not need to associate EIPs with internal-facing ALB instances. An EIP is an IP address that ALB uses to provide services over the Internet. You can associate multiple EIPs with an Internet-facing ALB instance. To ensure high availability, Internet-facing ALB must use at least two EIPs in different zones to provide services.|
|VIP||VIPs of ALB are used to receive requests. Each VIP is a private IP address that belongs to a virtual private cloud (VPC).|
Click the following button to navigate to the ALB buy page.