เครือข่ายส่งเนื้อหาและการขยายที่ขอบเครือข่าย

Load balancing, caching, and database scaling all improve the origin. A CDN goes further: it serves responses from servers physically close to the user, before traffic ever reaches your origin.

A Content Delivery Network is a global network of edge servers. Users connect to the nearest one (a point of presence), cutting round-trip distance dramatically.

When the edge has a fresh copy of a response, it returns it directly — a cache hit. Your origin never sees the request, which offloads enormous load.

You tell the CDN how to cache via headers:

• max-age — seconds the response stays fresh
• s-maxage — overrides max-age for shared caches like CDNs
• private — never cache at the edge

Even API JSON can be cached if it is the same for many users. Use short TTLs and vary the cache key by query string or auth scope to keep responses correct.

Stale data is the hard part. Strategies:

• TTL expiry — let it age out
• Purge — explicitly evict a URL after a write
• Versioned URLs — change the path so the old one is irrelevant

During a flash of traffic, a CDN serves cached responses to most users so the origin sees only a trickle. This is a key defense against both viral spikes and certain DDoS patterns.

Modern CDNs run code at the edge — edge functions. You can do auth checks, A/B routing, or response shaping near the user without a trip to the origin, shaving latency further.

A designated shield POP sits between all edges and your origin. Cache misses funnel through it, so the origin is hit at most once per object rather than once per region.

Track the cache hit ratio — the fraction of requests served from the edge. A high ratio means low origin load and fast responses. Low ratios point to poor caching headers or highly personalized content.

The stale-while-revalidate directive lets the edge serve a slightly stale response instantly while it fetches a fresh copy in the background. Users never wait on the origin, and content stays current.

You learned how the edge scales APIs:

• CDNs serve responses from nearby POPs
• Cache-Control headers govern freshness
• Invalidation via TTL, purge, or versioning
• Edge compute and origin shielding cut origin load further