Networking
Cloud CDN
Content delivery network using Google's global edge network
AWS equivalent
CloudFront
AWS → GCP: Key Differences
- ▸
Cloud CDN uses the same infrastructure as Google's own properties — YouTube, Google Maps.
- ▸
Integrated with HTTP(S) Load Balancer — not a separate service you configure independently.
- ▸
Cache invalidation: instant for specific paths.
Key Concepts to Know
- 1
Enable on a backend service in the HTTP(S) LB — one checkbox.
- 2
Caches: Cloud Storage objects, Compute Engine responses, Cloud Run responses.
- 3
130+ PoPs worldwide — good coverage in SEA (Singapore, Bangkok, KL, Jakarta).
- 4
Signed URLs and signed cookies for private content.
DCE Interview Tips
- ★
For Thai e-commerce: 'Enable Cloud CDN on your load balancer — static assets are served from the nearest Google edge node in Bangkok, reducing latency from 200ms to 5ms.'
- ★
Cloud CDN is one of the easiest 'quick wins' to present in a PoC.
Common Gotchas
- !
Cache-Control headers from your origin control what gets cached — make sure your app sets these correctly.