Practice WebAssembly ecosystem vocabulary: WASI, component model, wasmtime, WasmEdge, WASM Component Model composition, and serverless WASM use cases.
0 / 5 completed
1 / 5
What is WASI (WebAssembly System Interface)?
WASI is a standardised system interface for WebAssembly running outside the browser. Without WASI, a WASM module compiled to run outside a browser has no standard way to access files, network, or other OS resources. WASI provides these as portable, capability-based APIs — you explicitly grant access to specific directories or resources, unlike traditional Unix permissions. This makes WASM programs portable across any WASI-compliant runtime.
2 / 5
'Wasmtime runs WASM outside the browser.' What is wasmtime?
Wasmtime is a production-grade, standalone WASM runtime from the Bytecode Alliance. It supports WASI and is designed to be embedded in applications or used as a command-line tool. Wasmtime compiles WASM to native code at runtime (JIT or AOT) and is used in server-side WASM execution, plugin systems, and serverless platforms. It's one of several WASM runtimes alongside wasmer, wasm3, and V8.
3 / 5
'WasmEdge for edge computing.' What makes WebAssembly well-suited for edge computing?
WASM is attractive for edge computing (CDN edge nodes, IoT, Cloudflare Workers) because: (1) tiny binaries load and start in microseconds — much faster than container cold starts; (2) the sandbox provides strong security isolation between workloads without container overhead; (3) portability — one WASM binary runs on any hardware architecture at the edge. WasmEdge, Fastly Compute@Edge, and Cloudflare Workers all use WASM for these reasons.
4 / 5
'The WASM Component Model enables composition.' What is the WASM Component Model?
The WASM Component Model (a W3C standardisation effort) builds on core WASM to provide: rich interface types (strings, lists, records — not just numbers), a standard interface definition language (WIT — WebAssembly Interface Types), and a composition model for linking components. This means a Rust WASM component can call a Python WASM component's exported functions directly, with the runtime handling type conversion.
5 / 5
'The serverless function is compiled to WASM.' What advantages does WASM provide in serverless environments?
WASM in serverless (Cloudflare Workers, Fastly Compute@Edge, Fermyon Spin, WasmEdge) solves the cold start problem that plagues container-based serverless — WASM instances start in microseconds. The sandboxed isolation means thousands of untrusted tenant functions can run in the same process safely. And language portability means the platform can support functions written in Rust, C, Go, or Python all compiled to the same WASM target.