What is a CDN and How Does it Improve Performance?
Learn what a CDN is, how cache hits/misses and TTLs work, and how edge caching cuts latency — with a DevOps interview-ready answer.
Expected Interview Answer
A CDN (Content Delivery Network) is a globally distributed network of edge servers that caches and serves content from a location physically close to each user, dramatically reducing latency compared to fetching everything from a single origin server.
When a user requests a cached asset, the CDN routes them to the nearest edge node via DNS or anycast routing, and if that edge already has the content cached, it serves it directly without ever contacting the origin — this is a cache hit. On a cache miss, the edge fetches the content from the origin once, caches it according to a TTL (time-to-live), and serves subsequent requests from that cache until it expires or is purged. Beyond static assets like images, CSS, and JS, modern CDNs also cache API responses, terminate SSL/TLS at the edge, and provide DDoS protection by absorbing malicious traffic before it reaches the origin. Cache invalidation is the hardest part in practice — deploying new content often requires purging or versioning cache keys (e.g., filename hashing) so users do not receive stale assets after a release.
- Reduces latency by serving content from geographically nearby edges
- Offloads traffic from the origin server, cutting infrastructure cost
- Improves resilience by absorbing spikes and DDoS traffic at the edge
- Speeds up page load and improves user-perceived performance globally
AI Mentor Explanation
A CDN is like a sports broadcaster setting up regional relay towers in every city instead of forcing every household to receive a signal from one distant central studio. A fan tuning in from a nearby relay tower gets a clean, fast picture instantly, which is a cache hit, while a brand-new local relay first needs one feed from the central studio before it can broadcast locally, which is a cache miss. Once that relay has the feed, every other fan nearby benefits from the same fast, cached broadcast until the match slate refreshes. This regional setup means fans in every city get near-instant coverage instead of everyone straining one central signal.
Step-by-Step Explanation
Step 1
Route to the nearest edge
DNS or anycast routing sends the user request to the geographically closest CDN edge node.
Step 2
Check the edge cache
A cache hit serves content directly from the edge with no origin round trip.
Step 3
Fetch on a miss
A cache miss triggers one fetch from the origin, which is then cached at the edge per its TTL.
Step 4
Invalidate on release
New deployments purge stale cache entries or use versioned/hashed filenames to bust the cache safely.
What Interviewer Expects
- Understanding of cache hit vs cache miss and TTL-based expiry
- Knowledge of how CDNs reduce latency via geographic proximity
- Awareness of cache invalidation strategies (purge, versioned filenames)
- Ability to mention additional CDN benefits like DDoS protection and SSL termination
Common Mistakes
- Thinking a CDN only caches images, ignoring API/edge caching use cases
- Forgetting that cache invalidation is often the hardest operational problem
- Confusing a CDN edge node with the origin server
- Not mentioning TTL as the mechanism controlling how long content stays cached
Best Answer (HR Friendly)
“A CDN puts copies of our static content on servers around the world, so users get it from a nearby location instead of waiting for it to travel from our one origin server. That makes the site feel noticeably faster for users everywhere, and it also takes a lot of load off our main servers.”
Code Example
# Serve a versioned asset with a long-lived cache header
Cache-Control: public, max-age=31536000, immutable
# Example: purge a path from a CDN via API (illustrative)
curl -X POST "https://api.cdn-provider.example/v1/zones/ZONE_ID/purge_cache" \
-H "Authorization: Bearer $CDN_API_TOKEN" \
-H "Content-Type: application/json" \
--data '{"files":["https://example.com/app.abc123.js"]}'Follow-up Questions
- What is the difference between a cache hit and a cache miss?
- How would you invalidate stale content after a deployment?
- How does a CDN help mitigate a DDoS attack?
- Can a CDN cache dynamic API responses, and when would you do that?
MCQ Practice
1. What is the primary benefit of a CDN?
A CDN reduces latency by serving content from geographically distributed edge nodes near the user.
2. What happens on a CDN cache miss?
On a miss, the edge node fetches from the origin, caches the response per its TTL, and serves future requests from cache.
3. What is a common way to avoid serving stale assets after a deployment?
Hashing filenames per build creates unique cache keys, so new deployments are never served stale cached content.
Flash Cards
What is a CDN? — A distributed network of edge servers caching content close to users.
Cache hit vs cache miss? — Hit serves from edge cache directly; miss fetches from origin once and caches it.
What controls how long content stays cached? — The TTL (time-to-live) set on the cached response.
How do you avoid stale assets after deploy? — Use versioned/hashed filenames or explicitly purge the cache.