What is Origin Server?
Also known as: Origin
An origin server is the authoritative source of content for a CDN, storing the original files that the CDN retrieves, caches, and delivers to end users.
An origin server is the primary repository of a website's or application's content, including HTML files, images, videos, API responses, and other assets. When a CDN edge server receives a request for content it does not have cached (a cache miss), it forwards the request to the origin server, which responds with the requested content. This process is called an origin pull. The origin server may be an on-premises web server (e.g., Apache, Nginx, IIS) or a cloud storage bucket (e.g., AWS S3, Google Cloud Storage). It must be configured to allow CDN edge servers to fetch content, typically by exposing a public endpoint or whitelisting CDN IP ranges. The origin server controls caching behavior through HTTP headers like Cache-Control and ETag, which influence how long CDNs store cached copies.
The origin server is the single source of truth for content; the CDN merely replicates it to reduce latency and offload traffic. In a typical CDN architecture, the origin resides behind the edge layer and is not directly accessed by end users except in failure scenarios (e.g., if the CDN cannot serve a cached copy). Advanced CDN features like origin shielding add an intermediate cache layer between the edge and origin, further reducing load on the origin. Proper origin configuration is critical for CDN performance, as slow or misconfigured origins can degrade the entire delivery chain.
Key facts
- Origin servers provide the authoritative copy of content for CDNs.
- CDNs pull content from the origin only on cache miss or stale cache.
- Origin servers can be physical, virtual, or cloud-based storage.
- Proper cache headers (e.g., Cache-Control) on the origin optimize CDN cache hit ratios.
- Origin servers should be configured to allow only CDN edge IP addresses for security.
How it works in practice
Related terms
References
More in CDN & Performance
Apdex Score
The Apdex Score is a standardised metric that measures user satisfaction with application performance by comparing response times against predefined target and tolerable thresholds.
Bandwidth Throttling
Bandwidth throttling is the intentional reduction of data transfer speed by a network operator or service provider to manage congestion, enforce usage policies, or control costs.
Brotli Compression
Brotli is a lossless compression algorithm developed by Google, offering higher text compression ratios than gzip, used by CDNs to reduce page load times.
Cache Hit
A cache hit occurs when a requested resource is found in a CDN edge cache and served directly to the client, bypassing the origin server entirely.
Cache Invalidation
Cache invalidation is the explicit removal of stored web objects from a cache so that new requests must revalidate or refetch them from the origin server.
Cache Miss
A cache miss occurs when a requested resource is not found in a CDN or proxy cache, forcing the request to be forwarded to the origin server and then storing the response for future requests.
CDN
A CDN (Content Delivery Network) is a geographically distributed network of proxy servers and data centers that deliver web content to users from the nearest edge location, reducing latency and offloading origin servers.
Core Web Vitals
Core Web Vitals are a set of three real-world user experience metrics (LCP, INP, CLS) defined by Google to quantify loading, interactivity, and visual stability on web pages.
Cumulative Layout Shift
Cumulative Layout Shift (CLS) is a Core Web Vital metric that measures the sum of all unexpected layout shift scores during a page's lifespan, quantifying visual stability.
Edge Computing
Edge computing is a distributed computing model that processes data and runs application logic at Points of Presence (PoPs) close to end users, minimizing round-trip latency and bandwidth usage compared to centralized cloud regions.