4 ms·
Congrats on the launch. Other wasm PaaS services are focused on HTTP endpoints where the wasm modules are run ephemerally, which is cool, but this gets me excit
by paulgb 3y ago
Congrats on the launch. Other wasm PaaS services are focused on HTTP endpoints where the wasm modules are run ephemerally, which is cool, but this gets me excited because it's more general. As I understand it, this could replace many of the things people containerize as network services (in a sibling comment you mention using it to serve DNS!)
If you use tokio in this, is it effectively a single-threaded tokio runtime, or do you have a way to take advantage of multiple cores?
- the_duke 3y agoWe use WASIX [1] to enable multi-threaded tokio inside Webassembly. That's actually how we have implemented static sites. For each site a a WebAssembly instance is spawned that runs a tokio static-web-server [2], which is multi-threaded and concurrently handles requests. That way the Edge serves static sites in the exact same way as you can run them locally (with `wasmer run wasmer/docs`, for example). [1] https://wasix.org/ https://wasix.org/ [2] https://github.com/wasix-org/static-web-server https://github.com/wasix-org/static-web-server