Content Delivery Networks (CDN) in Computer Networks - Step-by-Step Execution

Concept Flow - Content Delivery Networks (CDN)

Start: User requests content

↓

DNS resolves domain name

↓

DNS returns nearest CDN edge IP

Not configured→Request goes to origin

↓

Request hits CDN edge server

↓

Is content in edge cache?

Yes→Return cached content

No↓

Edge fetches content from origin server

↓

Edge caches content and returns to user

↓

End

This flow shows how a CDN intercepts user requests through DNS, checks its edge cache, and either serves cached content or fetches from the origin server.

Execution Sample

Computer Networks

User requests www.example.com/image.png
DNS resolves to CDN edge server IP
Edge server checks local cache
Cache MISS: edge fetches from origin
Origin returns image.png
Edge caches image.png with TTL 86400s
Edge returns image.png to user

This sequence shows a first-time request where the CDN edge has no cached copy, so it fetches from origin, caches the response, and serves the user.

Analysis Table

Step	Action	Condition/Check	Result/Decision	Next Step
1	User requests image.png	N/A	HTTP request initiated	DNS resolution
2	DNS resolves domain	Is CDN configured?	Yes, CNAME points to CDN	Route to nearest edge
3	Request reaches edge server	Is content in cache?	No (cache MISS)	Fetch from origin
4	Edge fetches from origin	N/A	Origin returns content with headers	Cache the response
5	Edge caches content	Cache-Control: public, max-age=86400	Stored with 24-hour TTL	Return to user
6	Edge returns content to user	N/A	User receives image.png	End
7	Next user requests same content	Is content in cache?	Yes (cache HIT)	Return cached content directly

💡 Subsequent requests for the same content are served directly from the edge cache without contacting the origin server.

State Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
request_url	www.example.com/image.png	Resolved to edge IP	Checked at edge	Served from cache	Delivered to user
cache_status	Unknown	Unknown	MISS	Stored (TTL: 86400s)	HIT for next request
origin_contacted	No	No	No	Yes (fetched content)	No (for cached requests)
user_latency	N/A	DNS: 5ms	Edge check: 1ms	Origin fetch: 200ms	Cache HIT: ~10ms total

Key Insights - 3 Insights

Why does DNS resolve to the CDN edge server instead of the origin?

The domain uses a CNAME record pointing to the CDN provider. The CDN's DNS uses anycast or geolocation to return the IP of the nearest edge server, as shown in step 2 of the execution_table.

What determines how long the edge server keeps the cached content?

The Cache-Control header from the origin server sets the TTL. In step 5, max-age=86400 tells the edge to cache for 24 hours before the content is considered stale.

Why is the second request so much faster than the first?

The first request (cache MISS) requires fetching from the origin server. The second request (cache HIT) is served directly from the nearby edge server, eliminating the origin round-trip as shown in step 7.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What happens when the edge server does not have the content cached?

A The request is rejected

B The edge fetches the content from the origin server

C The user is redirected to the origin directly

D The edge waits until the content appears

💡 Hint

Check the 'Next Step' column when the cache check results in a MISS.

According to the variable_tracker, what is the cache_status after step 5?

A MISS

B Expired

C Stored with TTL 86400s

D Empty

💡 Hint

Look at the cache_status row in the 'After Step 5' column.

What is the main reason a CDN reduces latency for users far from the origin server?

A It compresses all content to smaller sizes

B It serves cached content from a geographically closer edge server

C It increases the origin server's processing speed

D It uses a faster version of HTTP

💡 Hint

Think about the physical distance between the user and the server responding to the request.

Concept Snapshot

CDNs distribute cached content across edge servers worldwide.
DNS routes users to the nearest edge server using anycast or geolocation.
Edge servers check their cache: HIT serves instantly, MISS fetches from origin.
Cache-Control headers determine how long content stays cached.
Result: dramatically lower latency and reduced origin server load.

Full Transcript

This visual execution shows how Content Delivery Networks reduce latency by caching content at edge servers close to users. When a user requests content, DNS resolves the domain to the nearest CDN edge server instead of the origin. The edge server checks its local cache. On a cache miss, it fetches from the origin server, stores the response according to Cache-Control headers, and returns it to the user. On subsequent requests, the edge serves the cached content directly without contacting the origin. This turns a 500ms origin fetch into a 10ms edge response, which is why CDNs are essential for serving content to users around the world.