Origin Server
Definition
An origin server is whatever sits behind a CDN and can produce the real thing. A request from a visitor reaches an edge node first; if that node holds a fresh copy it answers immediately, and if it does not it forwards the request to the origin, keeps what comes back and passes it on. The origin might be a web server on a virtual machine, an object storage bucket, a serverless handler or a managed platform — the term describes where it sits, not how it is built. Response headers usually reveal which one answered: an Age value, or a vendor header such as X-Cache carrying HIT or MISS. On a well-cached static site the origin may see under 5 percent of total requests, and on a badly cached one it sees nearly all of them.
Why It Matters
The origin is the part that can be overwhelmed and the part that produces the bill. A site fronted by a cache with a 97 percent hit ratio sends three requests in a hundred home; drop the hit ratio to 60 percent by mishandling cache headers and the same traffic multiplies origin load thirteenfold, which is how a launch day takes down a machine that had coped for two years. Distance matters too. Every cache miss is a full round trip to wherever the origin lives, so a visitor in Sydney hitting a server in Frankfurt waits roughly 300 extra milliseconds for the first request of each uncached file, even though everyone after them gets it locally. And when the origin is down, the cache only protects you for as long as its copies stay fresh.
How It Works
On a miss, the edge node opens its own connection to the origin and makes the request on the visitor's behalf, then stores the response according to the Cache-Control header it came back with. Once that copy expires the node does not necessarily refetch the whole file: it sends a conditional request carrying If-None-Match with the stored ETag, and an unchanged file comes back as a 304 with no body, which is cheap. Providers add origin shield — a designated node all others fetch through — so a cold file is pulled from the origin once rather than once per location. A purge marks cached copies stale so the next request goes home again. If the origin returns a 5xx or times out, some configurations serve a stale copy instead, which is usually better than showing an error.
Real-World Example
A trade body publishes a 6 MB annual report on 99helpers at brant-report.99helpers.site and links to it from a press release. The first reader in Sydney triggers a miss: that node fetches the PDF, stores it and delivers in about 400 milliseconds. Every Sydney reader afterwards gets it in around 30, with nothing further asked of the origin all week. The publisher never sees any of this, because on 99helpers the origin is the platform's own storage — there is no machine to size, expose or keep patched.
Common Mistakes
- ✕Treating origin and edge as interchangeable — a change that is live at the origin can stay invisible for as long as the cached copy remains fresh
- ✕Sending no-store or a zero max-age on assets that never change — every request then goes home, and the cache in front of it is decorative
- ✕Sizing the origin for average traffic — it only ever has to survive the cache misses, which arrive in bursts after a deploy or a purge
- ✕Leaving the origin reachable by its own address — visitors and bots that find it bypass the cache entirely and take the protection with them
Related Terms
Web Server
The software that listens for HTTP requests and answers them with files or generated responses. Nginx, Apache and Caddy are web servers; something like them sits behind every address you have ever opened.
Static Hosting
Static hosting is a service that stores a folder of finished web files and serves them over HTTP, without running any application code of yours. You upload the folder; the host answers requests for the files in it.
CDN
A content delivery network: a set of servers spread across the world that keep copies of your files and answer each visitor from somewhere close to them. It is the service; the machines it runs on are its edge network.
Cache-Control
The HTTP response header that tells browsers and caches whether they may keep a copy of a file, for how long, and who is allowed to. It is the single biggest lever over how fast a site feels on a second visit.
Edge Network
The fleet of servers a delivery provider runs in cities around the world, positioned close to visitors rather than close to your origin. It is the machinery a CDN is built from.
Put a file online in seconds
Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.
Host a file free →