Gateway Gus saysCDNs cache responses at edge locations near users — fast delivery and origin offload.
A Content Delivery Network caches your responses on servers worldwide, so a user in Tokyo hits a nearby edge instead of your origin in Virginia. It slashes latency and shields the origin from traffic spikes. CDNs honor your cache headers; you control freshness with Cache-Control and purge/invalidate when content changes. Great for static assets and cacheable GET APIs.
Power-ups you unlock
Edge caches near users → low latency
Offloads traffic from the origin
Honors your Cache-Control headers
Purge/invalidate on content change
Timeout Titan attacks — common mistakes
Caching user-specific data at a shared CDN
No invalidation strategy on updates
Expecting CDN caching for non-GET requests
Boss battleExplain how a CDN helps both latency and origin load.
Example code
<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#e6e0ff;font-family:monospace;padding:20px"><pre>user(Tokyo) → edge(Tokyo) cache hit ← fast
miss → edge fetches origin once, caches, serves many</pre></body></html>