What is a CDN? - Definition & Meaning

What is CDN?

A CDN (Content Delivery Network) is a distributed network of servers worldwide that serves content closer to end users. By caching files at edge locations, load times are drastically reduced and origin server load is minimized. Modern CDNs also offer edge computing, DDoS protection, and automatic image optimization, making them an essential infrastructure layer for any performant web application.

How does CDN work technically?

A CDN consists of Points of Presence (PoPs) distributed across the globe, each containing multiple edge servers. When a user requests content, the request is routed to the nearest PoP via anycast DNS. On a cache hit, content is served directly without contacting the origin server, with a Time to First Byte (TTFB) of just a few milliseconds. On a cache miss, the edge server fetches content from the origin, caches it locally, and serves it to the user, so subsequent requests from the same PoP are handled directly. Cache-control headers determine caching behavior: max-age for browser cache, s-maxage specifically for shared CDN caches, and stale-while-revalidate to serve cached content while a fresh version is fetched in the background. Vary headers ensure different versions are cached based on Accept-Encoding, Accept-Language, or other request headers. Modern CDNs like Cloudflare and Vercel Edge offer edge computing beyond static caching: serverless functions running at the edge for dynamic content with low latency. Cloudflare Workers and Vercel Edge Functions enable request/response transformations, A/B testing, geolocation-based routing, and personalization at the edge. Image optimization with automatic format conversion (WebP, AVIF), Brotli/gzip compression, and HTTP/3 (QUIC) support are standard features that save bandwidth and reduce load times. DDoS protection is built into major CDN providers and filters malicious traffic before it reaches your origin. Cache purging and cache tags provide granular control over cache invalidation per page, asset, or content type. Early hints (HTTP 103) allow CDN edges to instruct the browser to preload critical resources while the origin is still generating the full response, further reducing perceived load time. Range requests are supported by CDNs so large files such as videos and software downloads are served in segments, enabling resumable downloads without re-fetching the entire file. Tiered caching (also called origin shield) adds an intermediate cache layer between edge PoPs and the origin server, so popular content is fetched from the origin only once and then distributed from the shield node to all edges, drastically reducing origin load.

How does MG Software apply CDN in practice?

At MG Software, we deploy all web applications through Vercel, which automatically provides a global CDN via the Vercel Edge Network. Static assets are cached with content-hashed filenames and long max-age headers, so browsers and CDN edges cache files indefinitely while new deployments automatically generate fresh URLs. Images are automatically optimized and converted to WebP or AVIF. For clients with an international audience, we configure Cloudflare as an additional CDN layer for maximum performance, DDoS protection, and Web Application Firewall (WAF) capabilities. We set cache rules per content type and monitor cache hit rates through analytics to continuously optimize the configuration. For projects with dynamic pages, we use stale-while-revalidate combined with short s-maxage values so returning visitors receive cached content while the CDN fetches a fresh version in the background. We also configure Cloudflare Page Rules and Transform Rules to exclude specific routes from caching, such as authentication endpoints and shopping cart pages, ensuring personal data never lands on a shared edge node.

Why does CDN matter?

Load time is a direct factor in user experience and conversion. Google uses Core Web Vitals as a ranking signal, and the biggest gains in Largest Contentful Paint (LCP) often come from CDN caching. Without a CDN, every request must travel all the way to your origin server, which for international visitors can add seconds. A CDN reduces that latency to tens of milliseconds, protects against DDoS attacks, and lowers your bandwidth and server costs. For businesses, this means faster pages, higher Google rankings, and protection against traffic spikes. Research consistently shows that every additional second of load time reduces conversion rates by several percentage points, which for an online store with significant monthly traffic can translate to thousands of euros in lost revenue. By shifting bandwidth costs to the CDN network instead of your own servers, you also pay a fraction of the price per request.

Common mistakes with CDN

After deploys nobody purges edge caches, so users see stale JavaScript, CSS, or prices. Cache-control is set to immutable for HTML pages that do change, or s-maxage is missing for CDN-specific caching. The origin is still hit for every asset because random query strings bypass the cache. Teams cache dynamic API routes or personalized responses aggressively at the edge, leaking session data or showing wrong prices to other users. Vary headers are absent, causing compressed and uncompressed versions to be mixed. Image optimization is left disabled, so original multi-megabyte JPEG and PNG files are served when the CDN could automatically convert them to WebP or AVIF. Tiered caching or origin shield is not activated on CDN providers that support it, so the origin server still receives hundreds of cache-miss requests from individual PoPs.

What are some examples of CDN?

• A Dutch e-commerce store serving product images to customers in Asia via Cloudflare CDN, reducing load times from 3 seconds to 200 milliseconds because files come from a local edge point instead of a European server.
• A SaaS application using Vercel Edge Functions to automatically redirect users to the correct language version based on their geographic location, without the request ever reaching the origin server.
• A media website using cache-control headers and stale-while-revalidate to ensure articles load instantly while updates are processed in the background, so readers never wait for content.
• A software company using Cloudflare Workers for A/B testing at the edge, routing users to variant A or B based on a cookie with zero added server latency.
• An international e-learning platform distributing video files via a CDN with adaptive bitrate streaming, so students worldwide experience stable video quality regardless of their internet speed.

Related terms