An Overview of WebAssembly Engines: Architecture, Features, and Comparisons

The article introduces the core components of a WebAssembly engine, describing a conceptual model of an engine and its essential modules.

It outlines a generic engine architecture, covering program loading, linking, compilation or interpretation, thread scheduling, memory management, and external resource interfaces required for a language runtime.

The piece then surveys common WebAssembly engines—wasmtime, wasm3, WasmEdge, wasm‑micro‑runtime, and V8—highlighting their design, components, and application scenarios.

wasmtime : A high‑performance compiled engine written in Rust, part of the Bytecode Alliance. Its architecture includes compilation components (wasm‑environ, wasm‑cranelift, wasm‑jit, wasm‑obj), a runtime (wasm‑runtime with Store and InstanceHandle), and tools (wasm‑cache, wasm‑debug, wasm‑profiling). It uses Cranelift for JIT/AOT compilation and achieves performance several times higher than wasm3.

void * Operation_Whatever(pc_t pc, u64 * sp, u8 * mem, reg_t r0, f64 fp0);

wasm3 : A lightweight interpreter‑only engine written in C, employing threaded code and register‑based instruction translation (M3). It excels in cross‑platform support, especially on iOS, and remains the fastest interpreter in benchmarks. Example CLI usage:

brew install wasm3
wasm3 --func function_name_to_run your_module.wasm

WasmEdge : A Cloud‑Native Foundation‑hosted engine targeting edge and cloud‑native workloads, using LLVM for JIT/AOT compilation and offering extensive extensions such as QuickJS, Node.js compatibility, TensorFlow, and React SSR.

wasm‑micro‑runtime (WAMR) : An embedded engine supporting both interpretation and compilation (JIT/AOT) with an LLVM backend, delivering a very small binary size (~50 KB) and top performance in recent benchmarks.

V8 : The JavaScript engine that also runs WebAssembly via TurboFan or LiftOff back‑ends, providing JIT compilation and broad support for WebAssembly proposals, though lacking native WASI support.

In conclusion, the article summarizes the components needed for an engine, compares the five discussed engines in terms of execution model, performance, standards compliance, and typical application scenarios, and points readers to further material on building a WebAssembly interpreter.