01
Processes as Wasm instances
Each process is an isolated Wasm instance — own stack, heap, syscalls, and permissions. One crash can never corrupt another.
// erlang-inspired · webassembly · rust
Isolated lightweight processes, fault tolerance, per-actor sandboxing, and secure clusters you can hook into live — on WebAssembly.
Each process is an isolated Wasm instance — own stack, heap, syscalls, and permissions. One crash can never corrupt another.
Wasmtime fibers suspend a guest’s “blocking” call while the host awaits. Millions can wait for almost nothing.
Tokio tasks multiplexed over a few threads, with epoch interruption for BEAM-like fairness. ~2.4M spawns/sec.
Traps become process exits; links and monitors propagate failure so supervisors restart exactly what broke.
Processes, mailboxes, links, and supervisors — implemented as a runtime-agnostic core.
Every process gets nothing unless granted — capabilities are explicit, scoped, revocable.