> Term

Content Delivery Network Caching

Caching static or delivery content closer to the user to reduce load on the origin server.

Detailed Explanation

CDN caching involves storing copies of web assets (like images, scripts, and HTML pages) on edge servers distributed globally. When a user requests a resource, the CDN serves it from the geographically closest server.

This prevents every user request from having to travel all the way back to the main origin server, drastically speeding up load times and reducing infrastructure costs.

Why It Matters

It is essential for global scale. Without a CDN, users far from the datacenter suffer slow load times, and the origin server is vulnerable to traffic spikes and DDoS attacks.

Common Failure Mode

Aggressive caching without proper invalidation strategies, causing users to see stale data (like an old price on an e-commerce site) long after it was updated.

Practical Example

A user in Tokyo accesses a New York-based website. Instead of waiting for the image to travel from NY, the CDN serves the image instantly from a cache node in Tokyo.

Production Manifestation

Configured via `Cache-Control` headers and managed through providers like Cloudflare, Fastly, or AWS CloudFront.

Frequently Asked Questions

What is Content Delivery Network Caching in short?

Caching static or delivery content closer to the user to reduce load on the origin server.

What is the most common failure mode?

Aggressive caching without proper invalidation strategies, causing users to see stale data (like an old price on an e-commerce site) long after it was updated.

AI Summary

Caching static or delivery content closer to the user to reduce load on the origin server. It is essential for global scale. Without a CDN, users far from the datacenter suffer slow load times, and the origin server is vulnerable to traffic spikes and DDoS attacks.