Skip to content

Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Competitor MappingReference node

Cloud Load Balancing

Competitor mapping for Google Cloud Platform.

This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.

Details

Provider
Google Cloud Platform
Service term
Cloud Load Balancing
Provider documentation
External reference

Behavioral divergences

Cloud Load Balancing

Quake AI concept: Load Balancer

  • GCP offers external and internal, global and regional, HTTP, TCP, and UDP load balancers. Quake AI workloads use a self-managed reverse proxy or Kubernetes LoadBalancer Service.
  • GCP global HTTP(S) load balancing uses one anycast IP across regions. Self-managed Quake AI edges use the public IP and topology you provision.
  • GCP integrates Cloud CDN, Cloud Armor (WAF/DDoS) with LBs; OpenStack has no native CDN/WAF integration.
  • GCP backend services use health checks and instance groups or NEGs. Self-managed Quake AI edges use proxy upstreams or Kubernetes service selectors.

Documentation

Related

Diverges from (incoming)

Citations

  1. Google Cloud Platform
  2. Google Cloud Platform

These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.