WebAssembly at the Edge¶
7-minute read. Assumes you've read Edge computing explained.
The one-line answer¶
WebAssembly (Wasm) is a compact, sandboxed binary format that many languages compile to. Edge platforms use it to run small pieces of customer code safely and quickly, in languages other than JavaScript.
What Wasm is¶
The WebAssembly project defines it as "a binary instruction format for a stack-based virtual machine," designed as a portable compilation target for programming languages. Its stated goals are fast (native speed), safe (memory-safe, sandboxed) and portable. It was built for browsers but also supports non-web embeddings, which is where edge platforms come in.
📖 WebAssembly - the project home page
Why it suits the edge¶
Edge functions run untrusted code from many customers on the same machines, and start on demand. That needs a sandbox and a small, fast-loading unit. A Wasm module is both. You compile Rust, Go, C or another language once and run it anywhere a Wasm runtime exists.
flowchart LR
Src[Rust, Go or C source] --> Comp[Compile to Wasm]
Comp --> Mod[.wasm module]
Mod --> Edge[Edge runtime sandbox]
Edge --> Req[Handles each request]You build once to a portable module; the platform's runtime runs it in a sandbox on every edge location.
A real platform: Cloudflare Workers¶
Cloudflare's docs say most languages can compile to Wasm, with support varying by language and compiler (they name Rust, Go and C). You can call non-JavaScript code from a JavaScript Worker, or write a whole Worker in Rust. Modules load through WebAssembly.instantiate(), which supports only pre-compiled modules.
Limits stated in the same docs:
- No threads. Each Worker runs in a single thread; the Web Worker API is not supported.
- Size and startup. Wasm usually needs extra runtime dependencies, so Workers using it tend to be larger than JavaScript ones and may start slower. They recommend
wasm-optto shrink binaries. - WASI is experimental, with only some system calls implemented.
- Workers generally supports the WebAssembly features available in Google Chrome; SIMD is supported.
📖 Cloudflare Workers WebAssembly - languages, loading, limits
Other providers offer Wasm-based edge runtimes too; check each one's docs, as support differs. This page only verifies Cloudflare.
Wasm versus containers and JavaScript¶
| Wasm module | Container | JavaScript at the edge | |
|---|---|---|---|
| Isolation | Sandbox in the runtime | OS-level, needs more setup | Runtime sandbox |
| Language choice | Anything that compiles to Wasm | Anything | JavaScript or TypeScript |
| Typical use | Small per-request logic | Whole services | Small per-request logic |
The first two rows describe the design intent; compare startup and size on your own workload before choosing.
When to use it¶
- Reusing existing Rust, Go or C code (parsers, image or crypto routines) at the edge.
- Running customer-supplied plug-ins safely.
- Not for ordinary header edits or redirects: plain JavaScript edge functions are simpler.
Common mistakes¶
- Assuming full Linux behaviour: no threads and limited WASI mean many libraries will not compile or run.
- Shipping a large module and then wondering about cold start.
- Using Wasm where a ten-line JavaScript function would do.
How exams test it¶
Cloud certs seldom ask about Wasm. You may meet it in edge and CDN scenario discussions; the exam answer is usually the provider's edge function product. See Edge computing explained.