# Edge computing

> Running code on the CDN's edge servers — close to the user — instead of one origin far away; personalization without the round trip.

A CDN caches files; edge computing runs functions on the same boxes — routing, A/B bucketing, geolocation headers, auth checks — in milliseconds from the user. The request never travels home, so the response never pays for the distance.

The constraint is the runtime: edge functions are short-lived, small, and limited in what they can touch — no long connections, no giant dependencies. Right-sized work belongs there: a geo-redirect, a header rewrite, a light personalization. The heavy lifting still lives at the origin, where the data is.

## Related terms

- https://dfieldsolutions.com/en/glossary/cdn.md
- https://dfieldsolutions.com/en/glossary/ssr.md
- https://dfieldsolutions.com/en/glossary/lcp.md

---

Source: https://dfieldsolutions.com/en/glossary/edge-computing
DField Solutions — Dunakeszi, Hungary — dezso@dfieldsolutions.com
Booking: see https://dfieldsolutions.com/en/contact