How We Can Create a Thriving Wasm Ecosystem
summary
Overview of concrete tooling and results: Wasmtime runs WASI modules with ahead‑of‑time caching and experimental preinit that cuts startup to microseconds; WasmEdge appears as a CNCF JIT for mid‑tier devices while Wasm3 targets tiny interpreters for constrained hardware. Krustlet implements a kubelet that runs zero containers by scheduling WASM pods. Bindle provides immutable, signed multi‑module artifact storage; waggy exposes WASM as HTTP handlers via waggy (CGI‑style). Hippo PaaS demo scaffolds, builds and pushes an app to a URL; wasmCloud runs a 21-line module scaled to 15 actors with pluggable key‑value and HTTP providers.
AI-written summary · about
chapters (17)
- 0:00WebAssembly ecosystem intro
- 1:32Why WebAssembly is unique
- 4:17Wasm for cloud and servers
- 7:02Key Wasm projects and tools
- 8:05Wasmtime runtime features
- 9:10YoWasm easy setup
- 10:54Waggy: Wasm Gateway Interface
- 11:55Bindle: Wasm artifact storage
- 14:24Hippo: Wasm PaaS demo
- 17:17Alternative Wasm runtimes
- 17:37Crestlet: Kubernetes integration with WebAssembly
- 18:40Atmo: Wasm module chaining
- 19:42WasmCloud: actor model
- 25:39Reusable Wasm modules
- 26:21Edge Wasm runtimes
- 27:45Wasm in Node.js/SpiderMonkey
- 28:05Future of WebAssembly
related talks
30mWASM in the Wild West: A Practical Application Tale
19mWebAssembly's Journey Beyond the Browser
31mWith WasmEdge to New Shores
35mMicroservices and WASM, Are We There Yet?
38mWebAssembly beyond the browser
48mWebAssembly Beyond the Browser
42mWebAssembly beyond the browser
25mManaging WebAssembly apps with Kubernetes