Computing near the user
Edge computing runs computation at locations close to users rather than only in a few central data centers. By shortening the physical distance data travels, it cuts latency and reduces load on the origin.
A content delivery network is a familiar edge example, caching static files near users. Modern edge platforms also run code at these locations.
Why it matters
- Lower latency responses are served from a nearby point of presence.
- Bandwidth savings filter or aggregate data near the source instead of shipping it all to the core.
- Resilience local processing can continue during a network or origin disruption.
Tradeoffs
- Limited resources edge nodes are smaller than central data centers.
- Consistency keeping data in sync across many edge locations is hard.
- Operations deploying and observing code across many sites adds complexity.
Common uses
Edge suits latency sensitive and high volume scenarios: real time personalization, request routing and auth at the edge, IoT data filtering, and serving cached or computed responses without a round trip to the origin.
Key idea
Edge computing pushes work to nodes near users to cut latency and offload the origin, trading limited per node resources and harder consistency for speed and resilience.