Edge Computing
Definition & meaning
Definition
Edge computing is a distributed computing paradigm that processes data closer to the source of generation rather than relying on a centralized data center. By running computations at the network edge — in locations geographically near users — edge computing reduces latency, improves performance, and enables real-time processing. Platforms like Vercel Edge Functions and Cloudflare Workers are popular edge computing solutions for web applications.
How It Works
Edge computing moves computation from centralized data centers to locations physically closer to end users — typically CDN edge nodes distributed across dozens or hundreds of global Points of Presence. Instead of every request traveling to an origin server in a single region, code executes at the nearest edge location, often within 50ms of the user. Edge functions run in lightweight runtimes — typically V8 isolates (the same JavaScript engine as Chrome) rather than full containers. These isolates cold-start in under 5 milliseconds, compared to 100-500ms for serverless containers. Edge computing sits between the client and the origin, enabling request/response manipulation, authentication checks, A/B testing, geolocation-based routing, and personalization without round-tripping to a distant server. The trade-off is a constrained runtime: limited CPU time (typically 10-50ms), restricted APIs (no filesystem access, limited Node.js compatibility), and small memory limits. Data locality is the main challenge — edge functions are fast, but the database is usually still centralized.
Why It Matters
Edge computing eliminates the latency tax of centralized infrastructure. A user in Sydney hitting a server in Virginia adds 200-300ms of network latency per round trip — edge computing reduces this to under 30ms. For real-time applications, authentication flows, and personalized content, this difference is transformative. Edge functions also reduce origin server load because requests are handled before they reach your infrastructure. The technology enables new patterns: serving different content by country without client-side JavaScript, running A/B tests without layout shift, validating authentication tokens without hitting an API, and transforming responses on the fly. As databases like Turso, Neon, and DynamoDB Global Tables add edge-aware replication, the full-stack edge becomes increasingly viable.
Real-World Examples
Cloudflare Workers is the most mature edge computing platform, running on over 300 cities worldwide with a free tier of 100,000 requests per day. Vercel Edge Functions power Next.js middleware for authentication, redirects, and feature flags at the edge. Deno Deploy runs TypeScript at edge locations using the Deno runtime. AWS Lambda@Edge and CloudFront Functions execute code at Amazon's CDN edge locations. Fastly Compute runs WebAssembly at the edge for maximum performance. Practical use cases include: running Next.js middleware for geolocation-based pricing, Cloudflare Workers handling API rate limiting, Vercel Edge Middleware rewriting URLs for internationalization, and edge-side A/B testing that avoids the content flash problem. Turso (libSQL) and Neon Postgres offer database read replicas at edge locations.