~/talk

Server-side Wasm Applications: Replacing Docker with WASI

links:none on file
slides:none on file

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

  1. 0:00Introduction
  2. 4:43WebAssembly in the browser
  3. 8:44Defining WebAssembly terms
  4. 11:09Docker vs. WASI
  5. 13:23Wasm language support
  6. 15:06Wasm platforms
  7. 16:33Replacing Docker
  8. 20:00Live demo: background removal
  9. 23:56Q&A: networking and scaling
  10. 27:21C++ on the server
  11. 28:54Collaborative editing
  12. 32:41Machine learning on the edge
  13. 36:03Live demo: ML fingerprinting
  14. 38:35Q&A: Kubernetes and embedding
  15. 46:10Leipzig to container host
  16. 55:46Concluding remarks
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.