3 ms·
so this is like WSGI? The almost 30 year old design pattern that blocks on requests waiting for a response from the downstream app and really isn't scalabe?
by fnord77 5y ago
so this is like WSGI? The almost 30 year old design pattern that blocks on requests waiting for a response from the downstream app and really isn't scalabe?
- supermatt 5y agowsgi isnt inherently blocking. it is a protocol and it is up to the implementation on both sides if the interface as to how it is handled. that said, according to the docs this seems to be cgi 1.1 which equates to a process per request, which afaik isnt so scalable.
- zozbot234 5y agoWASM "processes" need not be the same as OS-level processes. So I don't think this would have the scalability issues of plain CGI.
- supermatt 5y agointeresting! i will have to have a look into this
- Matthias247 5y agoRight. And the Wasm runtime could run multiple Wasm processes on one OS thread. If one program blocks on stdin/stdput it gets descheduled and the next one can run. Which basically provides the same M:N scheduling that highly scalable Webservers would use.
- formerly_proven 5y agoIt’s not, this is a CGI implementation. WSGI is an in-process API and can support multiple requests in flight. Kind of weird to call this a gateway interface instead of something like wasm_cgi. > Wagi is an implementation of CGI for WebAssembly.
- giancarlostoro 5y agoASGI is the replacement for WSGI. Honestly I never noticed insane latency with WSGI.