Client requesting assets
Cloud / Knowledge library
Google Cloud CDN
Caches HTTP content at Google's global edge locations
Why learn Google Cloud CDN?
Teams use Google Cloud CDN to adopt content delivery and edge acceleration without building the complete underlying platform themselves.
The problem it solves
Caches and accelerates content through globally distributed edge locations
Where it came from
Google Cloud CDN is Google Cloud's offering for content delivery and edge acceleration. Its closest catalog counterparts are Azure Front Door and Amazon CloudFront; they address the same broad need but are not feature-for-feature identical.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Explain the main responsibility of Google Cloud CDN.
- Choose a workload that fits Google Cloud CDN.
- Identify one operational tradeoff of Google Cloud CDN.
- Compare Google Cloud CDN with Azure Front Door.
- Compare Google Cloud CDN with Amazon CloudFront.
Documentation and sources
- Google Cloud products at a glance (docs.cloud.google.com)
Connect the ideas
Alternatives
Real World Example
Global Static Asset Acceleration for Retail Portals
E-commerce retailers serving a geographically dispersed customer base who require fast loading times for product images and static site content.
The business problem
High latency and increased load on origin servers caused by serving static assets directly from a single regional data center to users globally, resulting in slow page rendering.
How this topic solves it
Cloud CDN leverages Google's global edge network to cache HTTP content at locations physically closer to the end user, reducing the round-trip time for static asset requests and offloading traffic from the origin.
- Configure a global HTTP(S) Load Balancer to act as the entry point for traffic.
- Enable Cloud CDN on the backend service associated with the load balancer.
- Define cache modes to determine how the CDN handles cache-control headers from the origin.
- Verify cache hits by inspecting the 'Age' and 'Via' headers in the HTTP response.
The path of a user request through the Google network to the origin.
Cloud CDN Cache
Global Traffic Entry
Backend Infrastructure
- User → Request → Google Edge Location
- Google Edge Location → Cache Hit → User
- Google Edge Location → Cache Miss → Load Balancer
- Load Balancer → Fetch Origin → Origin Server
Expected business outcome
Improved user experience through reduced latency for static assets and decreased infrastructure strain on the origin server.
Limitations and checks
Cloud CDN only caches content that is publicly accessible and cacheable; private or dynamic content requires careful configuration to prevent unauthorized data exposure, which can be checked by auditing cache-control headers.