4 ms·
Webassembly is also gaining steam for server workloads due to several advantages (less overhead, better capability based security, composability, ...). See Spi
by the_duke 5y ago
Webassembly is also gaining steam for server workloads due to several advantages (less overhead, better capability based security, composability, ...).
See Spin [1], Wasmcloud [2], Lunatic [3], etc.
My system is based on a distributed Webassembly runtime.
The reason for taking inspiration from Kubernetes is making deployment of distributed workloads on that runtime easy.
A nice benefit for a Kubernetes alike system is that the equivalent to operators and controllers can be much more light-weight WASM actors that are easier to develop, deploy and scale.
[1] https://github.com/fermyon/spin https://github.com/fermyon/spin
[2] https://github.com/wasmCloud/wasmCloud https://github.com/wasmCloud/wasmCloud
[3] https://github.com/lunatic-solutions/lunatic https://github.com/lunatic-solutions/lunatic
- kitd 5y agoEven better (and I expect you're aware of this already), you can run Webassembly workloads under Kubernetes control: https://krustlet.dev/ https://krustlet.dev/
- the_duke 5y agoYeah, krustlet is great for integrating into existing Kube deployments. I'm just tackling the problem from the other side.
- andrewallbright 5y agoWebassembly as a desirable server side technology... I suppose I need to recontextualize what I understand webassembly to be. Hmm.
- traverseda 5y agoIt's like the JVM but more languages can run on it and it has buy in from more companies. Imagine all the promises of Java in the 90s/2000s but the open source community is actually interested in it.
- Tostino 5y agoIs that actually true though, or is this more of an aspirational goal for WASM? The JVM runs an absolute ton of different languages.