origin server
The server that actually holds the content or runs the application, as opposed to a proxy or cache in front of it.
In more detail
A reverse proxy selects an origin for each request. Reachability, TLS and health must be checked separately for the proxy and for each origin before assigning blame.
Related terms
- reverse proxy — A server that receives requests on behalf of other servers and forwards them, returning their responses as if they were its own.
- backend pool — The set of servers a load balancer can send traffic to, each marked eligible or not by health checks.
- CDN — A network of servers near users that keep copies of public content, such as images, and serve them quickly.
- edge network — Servers placed in many locations close to users, which can serve cached content or run small pieces of code with low latency.
- cache — A store of earlier answers kept close to where they are needed so they can be reused instead of fetched or computed again.
- miss rate — The share of requests a cache cannot answer, which all go on to the origin.
- cold cache — A cache that is empty or nearly empty, so almost every request misses and goes to the origin.
Taught in
- What HTTPS Adds, And What It Does Not — Linux Fundamentals & Systems Administration
- Forward And Reverse Proxies — Linux Fundamentals & Systems Administration
- Edge Middleware: Auth Verification & Route Matchers — Next.js 15 & Modern App Router Architecture
- Image & Font Optimization: Zero Layout Shift Assets — Next.js 15 & Modern App Router Architecture
- Back Of The Envelope Estimation: Storage And Bandwidth — Scalable System Design & Distributed Architecture
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
- Cache Invalidation And The Three Hard Cases — Scalable System Design & Distributed Architecture