An edge handler can shorten one network hop, but it does not move authoritative data, permissions, or durable writes by itself. This track follows private permit requests through canonical routing, bounded upstream work, location-bound caches, and committed origin state. Each lesson asks what evidence the browser can rely on after a failure.
Topics in this track
- Edge Request Normalization and Origin Trust — Define which request metadata an edge layer may trust before forwarding to the application origin.
- Edge Compute Budgets and Upstream Fanout — Bound CPU, memory, upstream calls, and deadlines before moving request work closer to users.
- Edge Cache Locality, Invalidation, and Private Scope — Treat cache entries as location-bound copies with explicit key dimensions and invalidation limits.
- Edge-to-Origin Write Routing and Consistency — Keep writes authoritative and define read-after-write behavior when edge locations and replicas lag.
Prerequisite paths
HTTP Delivery and Cache Ownership; Multi-Region Web State and Recovery; Authorization and Tenant Boundaries.
Practice and check
Build Project: edge permit case delivery and review Web Development: edge and origin contracts quiz.