A content delivery network (CDN) uses geographically distributed edge servers to cache static assets and cacheable dynamic content near end users. It reduces latency and offloads work from the origin server, provided expiration and purging rules prevent stale responses. section 6.4
Evaluate a CDN through these practical concerns:
- Cache images, scripts, and other static files at edge nodes; computed data such as generated image thumbnails can also be reused for later visitors. section 6.4
- Control freshness with Cache-Control, ETag, and Expires headers, alongside explicit expiration and purging policies. section 6.4
- Place the CDN within a multi-tier cache path: client, CDN, application, and database, increasing scalability and fault tolerance while adding observability and tuning complexity. section 6.4





