WebAssembly at the IoT Edge
summary
Argues WebAssembly can let IoT firmware remain stable while shipping business logic as tiny, signed modules: a Rust pricing function compiles to wasm binary ~300 bytes and runs inside a host using Wasmtime runtime with a deny-by-default sandbox. Demonstration shows swapping pricing logic (off‑peak and happy‑hour discounts) by replacing the .wasm without firmware changes. Tradeoffs: actor images can reach ~1 MB, runtimes need heavy scrutiny (fuzzing, cargo vet, formal checks), and hosts must enforce strict IO and version tracking.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:09Edge computing challenges
- 3:58Cloud computing challenges
- 10:34What is WebAssembly
- 15:28Motivating example
- 20:25Distributing WebAssembly binaries
- 22:13WebAssembly objections
- 28:18Docker versus binaries
- 29:40Summary and future
- 30:42Q&A
related talks
26mWebAssembly for a Reactive Internet of Things
37mBuilding a better web with WebAssembly at the edge
38mWebAssembly beyond the browser
40mWebAssembly - The Future of Distributed Computing
25mFrom Cloud to Edge computing - Unleashing the power of WebAssembly at the edge
48mWebAssembly Beyond the Browser
33mWebAssembly: The Next Frontier of Cloud Computing
20mKeynote: When Wasm Meets Cyber-Physical Systems: A Discussion of WebAssembly in Real-Time, Safety-Critical Systems
