WebAssembly beyond the browser
summary
WebAssembly runs outside the browser by compiling to wasm32-wasi and running on runtimes like Wasmtime, WasmEdge or Wasmer; a Rust example uses wasm32-wasi and Wasmtime with --map-directory to grant sandboxed file access and starts near‑instantly. Container tooling (runi + containerd, Docker runtime flag) lets images shrink dramatically—benchmarks show 3 to 20 times smaller images (examples: native 7 MB vs wasm 2.6 MB, full image 123 MB vs 5 MB). Major limits remain: WASI lacks sockets and GC, so projects like wagi (HTTP via stdin/stdout) and Spin fill gaps today.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 1:03Google Cloud Innovators Program
- 2:25What is WebAssembly and its origins
- 4:55Running WebAssembly outside the browser
- 9:30Key use cases for WebAssembly
- 12:21WASI and WebAssembly runtimes
- 17:38Demo: Compiling Rust to WASI
- 21:31Why run WebAssembly in Docker
- 27:43Demo: WebAssembly in Docker
- 29:53HTTP services with WAGI
- 35:12Frameworks for WebAssembly services
- 36:59Language support in WebAssembly
- 39:49Future of WebAssembly and conclusions
- 40:54Q&A session
related talks
38mWebAssembly beyond the browser
48mWebAssembly Beyond the Browser
35mWebAssembly beyond the browser
33mWebAssembly: The Next Frontier of Cloud Computing
31mWebAssembly & Containers: The Power Couple
37mBeyond the browser: Moving forward with a more Declarative Future with WebAssembly
50mWeb Assembly
19mWebAssembly's Journey Beyond the Browser