edge network
Servers placed in many locations close to users, which can serve cached content or run small pieces of code with low latency.
In more detail
"At the edge" means on one of these nearby servers rather than in your main data centre. Content delivery networks cache files there, and some platforms also run small functions there to answer quickly.
Example
Vercel and similar hosts can run Next.js middleware and Edge runtime routes at the edge; self-hosted Next.js runs them on your own server.Related terms
- CDN — A network of servers near users that keep copies of public content, such as images, and serve them quickly.
- Edge runtime — A lightweight Next.js runtime based on V8 isolates and standard Web APIs, which starts almost instantly but cannot use most Node.js APIs.
- origin server — The server that actually holds the content or runs the application, as opposed to a proxy or cache in front of it.
Taught in
- Dynamic Routes: Slugs & generateStaticParams — Next.js 15 & Modern App Router Architecture
- Server Actions: use server Directives & Mutations — Next.js 15 & Modern App Router Architecture
- Edge Middleware: Auth Verification & Route Matchers — Next.js 15 & Modern App Router Architecture
- Runtime Environments: Node.js vs Edge Runtime Choice — Next.js 15 & Modern App Router Architecture
- Metadata API: Dynamic OpenGraph & Head Management — Next.js 15 & Modern App Router Architecture
- Instrumentation: OpenTelemetry & Performance Spans — Next.js 15 & Modern App Router Architecture