Microservices and WASM, Are We There Yet?
summary
Tried to build a Kubernetes operator that loads polyglot WASM modules as sandboxed hooks and ran demos using Spin, WASI/WAGI, WasmEdge, Wasmtime, Wasmer, Go and Rust tooling plus Deno for runtime; compiled Go WASM runs in Deno and returns strings in the demo but many modules require manual pointer arithmetic and the host launches a VM per run. Major failure points: strings require pointer arithmetic, native C extensions and dynamic linking don’t port, threading breaks event loop. Core tech is promising but implementations and DX remain immature.
AI-written summary · about
related talks
30mWASM in the Wild West: A Practical Application Tale
31mHow We Can Create a Thriving Wasm Ecosystem
49mWasmer Things: An Upside-Down Guide to WebAssembly
48mWebAssembly Beyond the Browser
50mWeb Assembly
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
30mAre We Enterprise-Ready Yet?
53mWASM Wonders Decoding WebAssembly's Inner Workings