Edge Computing

Edge runtimes move logic closer to users—with strict CPU/time limits, different APIs than full Node, and tenant isolation requirements.

When to Offer This Workflow

Trigger conditions:

• Auth, redirects, or personalization at the CDN layer
• HTML rewriting, A/B assignment, or bot mitigation at the edge
• Global latency SLOs for read-heavy paths

Initial offer:

Use six stages: (1) workload fit, (2) edge vs origin split, (3) data & state, (4) security & tenancy, (5) limits & cost, (6) testing & rollout). Confirm platform (Workers, Lambda@Edge, Fastly Compute, etc.).

Stage 1: Workload Fit