CDN77 has launched its Edge Computing platform in beta, allowing clients to run custom WebAssembly code and handle HTTP request transformations directly on edge servers. The system integrates Wasmtime into their existing Nginx and OpenResty architecture to execute code with minimal latency overhead.
By moving beyond simple API-based rule sets to a full WebAssembly runtime, CDN77 provides streaming engineers with the precision needed for complex authentication, A/B testing, and manifest manipulation without the latency penalties of centralized processing. This shift aligns them with industry leaders like Cloudflare and Fastly, who have pivoted from simple caching to programmable edge services to capture higher-margin developer workflows. For the streaming ecosystem, this means more efficient per-request decision-making closer to the viewer. Watch for the release of persistent distributed storage, which will be the critical signal for whether this can support stateful video personalization at scale.
CDN77's WebAssembly-based edge computing launch places it in direct competition with established programmable CDN platforms. Cloudflare Workers, which has been generally available since 2018, processes requests across its global network using V8 isolates, while Fastly Compute, built on Wasmtime, creates and destroys a sandbox for each request flowing through its platform in microseconds, eliminating an entire class of side-channel vulnerabilities. CDN77's decision to embed Wasmtime into its existing Nginx and OpenResty stack mirrors Fastly's per-request isolation model, though CDN77 has not yet published comparable cold-start benchmarks.
The business case for programmable edge services has been validated by Cloudflare's financial trajectory, with its developer platform segment growing faster than its core CDN business. Fastly has continued expanding Compute's capabilities to capture developer mindshare. In July 2021, Fastly added JavaScript support to Compute by running the JavaScript virtual machine inside a WebAssembly sandbox, achieving zero-millisecond cold starts while maintaining per-request isolation. This language-agnostic approach, where code compiles to Wasm regardless of source language, is the same architectural bet CDN77 is making with its Wasmtime integration, and streaming engineers evaluating CDN77's beta will likely compare cold-start latency and language support against Fastly's published figures.
On the technical side, CDN77's architecture differs from both major competitors in a meaningful way. Cloudflare uses V8 isolates, which historically suffer from approximately 5 milliseconds of startup latency, while Fastly and now CDN77 use Wasmtime-based runtimes that avoid that overhead. Fastly's Compute platform runs request handlers in WebAssembly sandboxes, with each request starting a new sandbox by default for fast startup and per-request isolation, and also supports reusable sandboxes as an opt-in mode to reduce repeated initialization overhead. CDN77 will need to demonstrate whether its Nginx-embedded approach can match Fastly's microsecond-level instantiation while handling the concurrent connection volumes typical of live streaming and VOD delivery workloads.
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source
