With WasmEdge to New Shores
summary
Claims that WasmEdge runs WebAssembly modules alongside containers in Kubernetes, boots modules ~100× faster with footprints of 2–4 MB versus gigabyte images, and preserves existing tooling. Demonstrations build a Rust echo and an HTTP server with cargo targeting wasm32-wasi, run them with WasmEdge, package them into Docker images annotated image.variant=wasm.compat, push to Docker Hub and deploy on a local Kubernetes runtime, all responding correctly. Notes limits: extra build toolchain and incomplete language/runtime support.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:31Container & Kubernetes Both together has changed and influenced the ICT world massively
- 4:15What is WebAssembly (WASM)?
- 8:51Example implementations
- 10:35Let's think about the WASM potentials based on WasmEdge
- 24:56WasmEdge Solution Approach
- 29:18Containers for lifting, WASM for re-creating
related talks
25mManaging WebAssembly apps with Kubernetes
31mCloud Native WASM: What's All the Hype?
34mManaging WebAssembly Applications Using Docker and k8s Tooling
31mHow We Can Create a Thriving Wasm Ecosystem
38mCloud-Native WebAssembly: Containerization On the Edge
48mWebAssembly Beyond the Browser
38mWebAssembly beyond the browser
07mBeyond The Browser: Wasm in Your Cloud Development Workflow