The WebAssembly Component Model - Rocketfuel for WebDevelopment and APIs
summary
Explains how a WIT file becomes a runnable service: define an interface on wa.def, generate Rust bindings with cargo component new then cargo component build (bindings generate on first build), implement hello() returning "hello Bob", publish both component and WIT, compose them with wack plug into service.wasm, and run on Wasmtime (or Spin, nginx unit). Demo composes two real components, serves HTTP on :8080 and returns "hello Bob", proving the component model, registry flow and toolchain end-to-end.
AI-written summary · about
chapters (18)
- 0:00WebAssembly Component Model intro
- 1:02Speaker background
- 3:09WebAssembly history
- 4:14WebAssembly basics
- 6:41Core modules vs components
- 9:32WebAssembly System Interface and components
- 11:00Components as containers
- 13:10WIT fundamentals
- 16:00Tooling overview
- 17:26Demo setup
- 20:37WIT package creation
- 21:45Rust component building
- 24:58Bindings and logic
- 27:25HTTP component
- 30:18Component composition
- 33:12Testing composed component
- 36:23Key takeaways
- 38:10Q&A
related talks
18mAn introduction to the WebAssembly component model
01h 01mAn introduction to WebAssembly components
16mThe nuts and bolts of WebAssembly's component model
34mWasm Components for Every Language
34mWasm Components: The Interchangeable Parts of Software
30mWasm Component Composition: A New Era of Language Interoperability
50mAn Introduction to WebAssembly
52mWhat is a WebAssembly component (and why?)