Choosing Customizability and Distributing Dependencies with Wasm Components
summary
Shows how the wasm component model and CNCF wasmCloud run the same component in multiple hosts by composing providers and virtualizing imports. Builds an HTTP component and a key‑value counter, links a Redis provider in wasmCloud, then composes a mock file‑backed KV with whack and runs the identical component on wasmtime; responses are “hello from rust” and an incrementing counter. Adds a custom pingpong interface, virtualizes CLI env with wasi‑virt/wyvert, and demonstrates the composed component runs and returns “pong wasm day.”
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:05Component model overview
- 3:53Virtual platform layering
- 7:02Simple HTTP server demo
- 12:42Adding database dependency
- 18:43Custom interfaces and WYVert
- 24:50Summary & Q&A
related talks
34mWasm Components: The Interchangeable Parts of Software
01h 17mChoose Your Own Adventure: Wasm Edition
08mKeynote: WASI Standards and the Component Model: Transforming Application Development Forever
37mExploring C# Wasm Components
01h 01mAn introduction to WebAssembly components
18mAn introduction to the WebAssembly component model
34mWasm Components for Every Language
52mCross-cloud App Splitting With WebAssembly Components