WASM in the Wild West: A Practical Application Tale
summary
Krustlet runs WASM modules as Kubernetes nodes, and the team ships Bindle (aggregate object storage) and WAGI (HTTP handler) implemented mainly in Rust; runtimes include wasm3 (interpreter), Wasmtime/Wasmer (JIT/AOT), and tooling like wasm-opt and Wizer. A Swift-compiled module shrinks from 9.8MB → 4.3MB with wasm-opt, Wizer pre-initializes modules for nanosecond startup, and WASI still lacks stable streaming/networking and polished developer toolchains, so portability works but ops and APIs need standardization.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:05References
- 2:17How we got there
- 5:35What weve learned
- 6:30Java VM
- 7:52Containers
- 8:52Runtimes
- 10:52Language choice
- 12:45Optimization
- 15:25Different ways to execute
- 17:21WAI
- 18:27Keep your butt in the saddle
- 18:49Community fracturing
- 20:38The developer experience
- 23:49Wazi
- 25:57Guest Languages
- 26:41OCI
