Cloud Load Balancing
High performance, scalable load balancing on Google Cloud.
Global with single anycast IP
Provides cross-region load balancing, including automatic multi-region failover. Cloud Load Balancing reacts instantaneously to changes in users, traffic, network, backend health, and other related conditions.
Software-defined with flexibility
Cloud Load Balancing is a fully distributed, software-defined, managed service for all your traffic. Apply Cloud Load Balancing to all of your traffic: HTTP(S), TCP/SSL, and UDP.
Scale as your users and traffic grow. Easily handles huge, unexpected, and instantaneous spikes by diverting traffic to other regions in the world that can take traffic. Zero to full throttle in seconds.
"Google Cloud's Load Balancing simplifies our deployment and seamlessly delivers the scale and high-availability we need. We can easily handle 150,000 requests per second with no warmup time and no preparation needed on our end. Having this peace of mind has made a dramatic difference compared with our days configuring specialized load balancing hardware."
Arnaud Granal, CTO, Adcash
Set Up Network and HTTP Load Balancers
You'll learn the differences between a network load balancer and an HTTP load balancer and how to set them up for your applications running on Compute Engine VMs.
HTTPS Content-Based Load Balancer with Terraform
In this lab, you will create an HTTPS load balancer to forward traffic to a custom URL map.
HTTP Load Balancer with Cloud Armor
In this lab, you configure an HTTP Load Balancer with global backends and stress test the Load Balancer and denylist the stress test IP with Cloud Armor.
|HTTP(S) load balancing||HTTP(S) load balancing can balance HTTP and HTTPS traffic across multiple backend instances, across multiple regions. Your entire app is available via a single global IP address, resulting in a simplified DNS setup. HTTP(S) load balancing is scalable, fault-tolerant, requires no pre-warming, and is content-based. For HTTPS traffic, it provides SSL termination and load balancing.|
|Cloud Logging||Cloud Logging for load balancing logs all the load balancing requests sent to your load balancer. These logs can be used for debugging as well as analyzing your user traffic. You can view request logs and export them to Cloud Storage, BigQuery, or Pub/Sub for analysis.|
|TCP/SSL load balancing||TCP load balancing can spread TCP traffic over a pool of instances within a Compute Engine region. It is scalable, does not require pre-warming, and health checks help ensure only healthy instances receive traffic. SSL proxy provides SSL termination for your non-HTTPS traffic with load balancing.|
|Seamless autoscaling||Autoscaling helps your applications gracefully handle increases in traffic and reduces cost when the need for resources is lower. You just define the autoscaling policy and the autoscaler performs automatic scaling based on the measured load. No pre warming required—go from zero to full throttle in seconds.|
|SSL offload||SSL offload enables you to centrally manage SSL certificates and decryption. You can enable encryption between your load balancing layer and backends to ensure the highest level of security, with some additional overhead for processing on backends.|
|High fidelity health checks||Health checks ensure that new connections are only load balanced to healthy backends that are up and ready to receive them. High fidelity health checks ensure that the probes mimic actual traffic to backends.|
|Advanced feature support||Cloud Load Balancing also includes advanced support features, such as IPv6 global load balancing, WebSockets, user-defined request headers, and protocol forwarding for private VIPs.|
|Affinity||Cloud Load Balancing affinity provides the ability to direct and stick user traffic to specific backend instances.|
|Cloud CDN integration||Enable Cloud CDN for HTTP(S) load balancing for optimizing application delivery for your users with a single checkbox.|
|UDP load balancing||UDP load balancing can spread UDP traffic over a pool of instances within a Compute Engine region. It is scalable, does not require pre-warming, and health checks help ensure only healthy instances receive traffic.|
|Cloud Armor||Google Cloud Armor security policies enable you to rate-limit or redirect requests to your HTTP(S) Load Balancing, TCP Proxy Load Balancing, or SSL Proxy Load Balancing at the Google Cloud edge, as close as possible to the source of incoming traffic.|