Server-side Wasm Applications: Replacing Docker with WASI
summary
Argues that server‑side WebAssembly (WASI) can replace Docker for many stateless microservices by rebuilding a Java image as a Rust WASM module and running it with wasmtime/Spin/wasmCloud. Concrete results: a Java Docker image shows 672 vulnerabilities and needs 100 seconds startup with a 3 GB heap and 296 MB artifact, while the Rust WASM rebuild produces a 3 MB artifact and runs background‑removal demos in 25 ms end‑to‑end. Works for image processing and ~100 MB ML inference (~1s); current limits include no outbound networking, no threads and GC challenges.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 4:43WebAssembly in the browser
- 8:44Defining WebAssembly terms
- 11:09Docker vs. WASI
- 13:23Wasm language support
- 15:06Wasm platforms
- 16:33Replacing Docker
- 20:00Live demo: background removal
- 23:56Q&A: networking and scaling
- 27:21C++ on the server
- 28:54Collaborative editing
- 32:41Machine learning on the edge
- 36:03Live demo: ML fingerprinting
- 38:35Q&A: Kubernetes and embedding
- 46:10Leipzig to container host
- 55:46Concluding remarks
related talks
31mWebAssembly & Containers: The Power Couple
37mDevelop Wasm Applications with Docker
30mThe Future of the Cloud is WebAssembly
42mWebAssembly beyond the browser
38mWebAssembly beyond the browser
31mCloud Native WASM: What's All the Hype?
48mWebAssembly Beyond the Browser
33mWebAssembly: The Next Frontier of Cloud Computing
