Notices by Robin Whittleton (robinwhittleton@front-end.social)

@sil the goal of Compute@Edge isn’t to quickly serve some static files (they’ve got a CDN for that) but to process your data on the edge servers to personalise to users. The classic example they give is shipping a podcast episode with ads in: Fastly’s servers can geoloc the user, split the audio at defined points, insert up-to-date country-specific ads, splice the audio, and serve the file, all from the same URL. WASM (theoretically) gets them super-quick spin-up times on each request.