wRPC: Distributed Components, No Assembly Required
summary
wRPC (WIT‑RPC) implements WIT-defined RPC so WebAssembly components call across networks or IPC without recompiling hosts; demos show a browser JS app talking to a server plugin that proxies to Redis, a native Go plugin over TCP, NATS, WebTransport, and a Rust plugin, all running and serving invocations. The runtime auto‑polyfills imports/exports (wpc-wasiime), supports streaming async multiplexing, opaque resource handles (secrets), canonical compact encoding, and is already used inside wasmCloud.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 1:03Agenda and motivation
- 3:51New protocol for components
- 10:13WIT interfaces power
- 12:22Live demo
- 16:55Transports and multiplexing
- 19:21Async and streaming
- 21:10Wire protocol and encoding
- 22:15Building components
- 26:29Key takeaways
- 29:18Q&A
related talks
18mAn introduction to the WebAssembly component model
34mWasm Components: The Interchangeable Parts of Software
50mWeb Assembly
38mWebAssembly for the backend
29mwasi-cloud: The Future of Cloud Computing with WebAssembly
35mWebAssembly beyond the browser
40mWebAssembly - The Future of Distributed Computing
52mWhat is a WebAssembly component (and why?)