Keynote: WASI - A new kind of system interface & what it means for cloud native
summary
WASI defines a modular system interface for WebAssembly that replaces file-centric APIs with primitive I/O types so binaries run portably across OSes while keeping sandboxing. It proposes three migration paths (legacy FS, per-module virtualized FS, or direct WASI I/O types), moves metadata handling to the host, and claims dramatic IPC wins: eliminating repeated syscall/serialization copies that consume two thirds of same-host steps and enabling nanosecond calls between sandboxes.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:07create a very modular set of system interfaces
- 7:15building a backup application
- 7:36push as much of the meta compute out to the edges
- 10:47compile a module
- 11:18link your code against a version of libc
- 12:26providing a compatibility layer
- 13:59eliminating the overhead of the per module virtualized file
- 15:37move these details out to the edges
- 19:33allowing for various network failure failure modes and supporting non-blocking
related talks
05mKeynote: Wasm: A Revolution for Browsers, Containers, and the Cloud
24mWASI and the Cloud
28mThe WASI OS - Isolation with Communication, Wasm style
08mKeynote: WASI Standards and the Component Model: Transforming Application Development Forever
08mKeynote: WebAssembly in a Containerized World
33mWASI and the Cloud: A Game-Changing Duo
25mKeynote: View from Above: A Birds-eye View of the Wasm Landscape and Where It's Heading
29mwasi-cloud: The Future of Cloud Computing with WebAssembly
