An Edge KV store built with Wasm Components
summary
Fastly builds an edge KV service using Virtual Platform Layering and Wasm Components so user code links to platform features without gaining private host access. Implementation uses WIT interfaces and WIT bindgen glue to replace ~1,000-line SDKs with ~100-line wrappers, and migration uses a core-to-component adapter (P1→P2) plus wasm OCI distribution. Removing one HTTP hop saves about 3 ms HTTP hop saved on a 6 ms cached read (roughly a 50% latency win) and the component deployment and iteration flow works in production.
AI-written summary · about
chapters (13)
- 0:00Edge KV store intro
- 2:26Current infra and caching
- 3:49Native host challenges
- 6:37Wasm Components layering
- 9:44Component isolation benefits
- 10:04Performance with component integration
- 11:11Faster feature iteration
- 11:54Migrating apps to Wasm Components
- 13:58Component instantiation
- 14:20Dev experience with WIT
- 19:41SDKs with auto-generated glue
- 20:03Distributing components
- 21:16Q&A
related talks
31mWith WasmEdge to New Shores
33mKubernetes on the edge: running low-latency workloads with WebAssembly
31mHow We Can Create a Thriving Wasm Ecosystem
33mLeveling Up Wasm Support in Kubernetes
42mElevating Serverless Platforms with Wasm Components
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
19mWebAssembly's Journey Beyond the Browser
28mWasm + Kubernetes: Beyond Containers