Wasm Whiplash: WasmCloud's Wild Ride To Standards
Talkat KubeCon + CloudNativeCon Europe 2025 · on Thursday, 2025-04-03· at 11:45· Level 3 | ICC Capital Suite 7-9·
summary
Started in 2019 with a proprietary FFI, IDL and codegen stack that forced writing SDKs for Rust Go TypeScript Zig and Swift, the project spends four years on a homegrown binary protocol (WPC) and then rewrites to align with standards, launching wasmCloud 1.0 (2024) after adopting WASI 0.2 and the WebAssembly interface types and component model. Uses NATS for a flattened distributed runtime, cuts platform lock-in, and reframes tradeoffs as limited innovation tokens so teams focus on what truly differentiates.
AI-written summary · about
chapters (14)
- 0:00WasmCloud's standards journey
- 1:03What is WasmCloud
- 2:31Microservices pain and Waxo Suit
- 4:57WebAssembly pros and cons 2019
- 7:07WebAssembly as VM guest
- 9:16Need for WASI
- 12:42Custom SDKs for complex types
- 15:32WasmCloud's distributed features
- 18:21WebAssembly Component Model
- 21:14WasmCloud 1.0 and standards
- 22:37Early standards contribution
- 24:22Innovation tokens and focus
- 25:28WasmCloud's mission and future
- 25:51Acknowledgements
related talks
29mwasi-cloud: The Future of Cloud Computing with WebAssembly
33mWASI and the Cloud: A Game-Changing Duo
33mWebAssembly: The Next Frontier of Cloud Computing
30mDemystifying the WASM Landscape: A Primer
12mThe Wasm Wilderness: Technological Peaks We've Reached with WebAssembly
18mCloud Native & WebAssembly: Better Together
19mWebAssembly's Journey Beyond the Browser
30mWASM in the Wild West: A Practical Application Tale