Google Cloud’s HTTP(S) load balancing provides global load balancing for HTTP(S) requests destined for your instances. This means that your applications are available to your customers at a single anycast IP address, which simplifies your DNS setup. HTTP(S) load balancing balances HTTP and HTTPS traffic across multiple backend instances and across multiple regions. HTTP requests…

Pub/Sub is an asynchronous global messaging service. There are three terms in Pub/Sub that appear often: topics, publishing, and subscribing. A topic is a shared string that allows applications to connect with one another through a common thread. Publishers push (or publish) a message to a Pub/Sub topic. Subscribers will then make a subscription to…

Externally addressed VMs communicate with each other privately over Google’s backbone, regardless of region and Network Service Tiers. But it’s important to understand how public routing affects costs.

Anycast is a network addressing and routing method in which incoming requests can be routed to a variety of different locations or “nodes.”

HTTP(S) load balancers supports multiple SSL certificates, as well, if you wanted to serve multiple domains using the same load-balancing IP address and port.

Premium Tier delivers traffic from external systems to Google Cloud resources byusing Google’s low latency, highly reliable global network. This network consists of an extensive private fiber network with over 100 points of presence (PoPs) around the globe. This network is designed to tolerate multiple failures and disruptions while still delivering traffic. Standard Tier delivers…

Load balancers are software defined and distributed, which means they arehighly performant and not bottlenecked by a single appliance. They are tightly integrated with Compute Engine and GKE to allow for intelligent autoscaling based on various metrics, and health checks, so we can route traffic to the healthy instances and locations. Load balancers are available…

Health check probes come from addresses in the ranges 130.211.0.0/22 and 35.191.0.0/16. HTTP(S) Load Balancer uses health checks to determine if a particular backend instance should receive traffic. If all are unhealthy, clients receive message of “no healthy upstream” Managed Instance Groups also use health checks, but for a different purpose. If an instance is reported an unhealthy, it will…

Group of VMs with different configurations. Use case: Lift and shift of on-premise workloads that need a load balancer to serve traffic. No automatic elasticity or automatic healing