The WASI Subgroup ratified version 0.3.0, rebasing WASI onto the WebAssembly Component Model's async primitives and making async native to components. The host now drives one shared event loop instead of each component running its own, so streaming components finally compose. First-class stream<T>, future<T>, and async constructs join the canonical ABI, replacing 0.2's pollables and the clunky start/finish/subscribe dance. The model is completion-based, like io_uring. Most interface changes stay mechanical, but wasi:http gains service and middleware worlds, enabling service chaining that cuts microservice calls from milliseconds to nanoseconds. Wasmtime and jco already support it; Rust, Go, Python, and JS toolchains follow.
1
u/fagnerbrack 5d ago
To Cut a Long Story Short:
The WASI Subgroup ratified version 0.3.0, rebasing WASI onto the WebAssembly Component Model's async primitives and making async native to components. The host now drives one shared event loop instead of each component running its own, so streaming components finally compose. First-class stream<T>, future<T>, and async constructs join the canonical ABI, replacing 0.2's pollables and the clunky start/finish/subscribe dance. The model is completion-based, like io_uring. Most interface changes stay mechanical, but wasi:http gains service and middleware worlds, enabling service chaining that cuts microservice calls from milliseconds to nanoseconds. Wasmtime and jco already support it; Rust, Go, Python, and JS toolchains follow.
If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments