Google Cloud Networking & Content Delivery

Cloud Load Balancing

Global and regional load balancing behind a single IP address, with autoscaling backends.

What is Cloud Load Balancing?

Cloud Load Balancing distributes traffic to your backends from a single anycast IP. Global application load balancers route users to the nearest healthy region and integrate with Cloud CDN and Cloud Armor.

Key features

  • Global and regional load balancers
  • Single anycast IP
  • Managed SSL certificates
  • Integration with Cloud CDN and Cloud Armor
  • Autoscaling backends

What it is used for

  • High-availability web apps
  • Global traffic distribution
  • HTTPS termination

When to use it

  • Multi-region or high-traffic apps
  • HTTPS for many backends
  • Protected public endpoints

When something else fits better

  • A single small server or a Cloud Run app that only needs its default URL

How pricing works

Charged per forwarding rule and for data processed. Prices change and differ by region; we confirm current costs for your setup before you commit.

Equivalent on AWS

The closest AWS service is Elastic Load Balancing: distributes incoming traffic across servers, containers and functions (Application, Network and Gateway load balancers).

How DomainHostly helps with Cloud Load Balancing

  • Plan: choose the right setup, size and region for your workload and budget.
  • Set up securely: configure Cloud Load Balancing with least-privilege access, encryption and backups where they apply.
  • Migrate: move from shared hosting, your own servers or the other cloud with minimal downtime.
  • Run and optimise: monitoring, updates and regular cost reviews so you only pay for what you use.

Networking & Content Delivery: Private networks, DNS, load balancing, CDN and connectivity between your sites and the cloud.

What to consider: Networking & Content Delivery

  • Plan IP ranges up front so networks can connect to your offices and each other later without overlaps.
  • Put databases and internal services in private subnets; expose only load balancers or CDNs publicly.
  • Watch data-transfer (egress) charges; a CDN often reduces both cost and latency.

Related services: Networking & Content Delivery