The nuts and bolts of WebAssembly's component model
summary
Explains that a WebAssembly component is a collection of modules with a defined world (inputs/exports described in wit), plus how runtimes execute components and Docker now builds and runs wasm workloads. Describes tooling: a componentizer API converts language artifacts into components, a component registry (federated namespace) provides package transparency via a cryptographic verifiable log, and a composer wires components together — enabling language-agnostic reuse, small binaries, fast startup, and server-side deployment.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:34What is WebAssembly
- 2:38Success in Browser
- 3:45Serverless Ecosystem
- 4:20Server Side
- 7:48Leftovers
- 9:22Component
- 10:20World
- 11:12Type
- 11:39Component Registry
- 12:40Componentizer Composer
- 13:41Benefits
- 15:01Wrap up
related talks
18mAn introduction to the WebAssembly component model
52mWhat is a WebAssembly component (and why?)
34mWasm Components for Every Language
01h 01mAn introduction to WebAssembly components
39mThe WebAssembly Component Model - Rocketfuel for WebDevelopment and APIs
30mComponents, WebAssembly’s Docker’s Moment
30mKeynote: What is a Component (and Why)?
31mWebAssembly Component Model: Enhancing Security, Productivity, and...