3 ms·

I don't see the advantage of this over simply using kubernetes and the Kwasm Operator which adds WebAssembly support to Kubernetes nodes. No need for yet anoth

I don't see the advantage of this over simply using kubernetes and the Kwasm Operator which adds WebAssembly support to Kubernetes nodes. No need for yet another flimsy later of abstraction. Maybe after 5-10 years it will be mature enough to support many k8s features out of the box and can then replace k8s itself. But it is very far from that currently.

williamstein 2y ago
I’ve never used wasmcloud, but they claim the following advantage over k8s on this page: “Leverage WebAssembly components to extend Kubernetes and distribute applications across clouds, regions, clusters, and edges.” I think they use NATS.io to include “edge” services, which is something that is challenging to do in a single k8s cluster. I don’t think they are trying to replace k8s, but instead are solving a slightly different problem, which is attempting to build something somewhat like k8s, but with very different networking and security constraints.
joonas 2y ago
One of the principles we do our best to follow as we build wasmCloud is the idea of "compatible with, but not dependent upon", and to that end we do in fact integrate very nicely with Kubernetes. A recent blog post highlighted some of the work we’ve done to provide a Kubernetes Operator for wasmCloud: https://wasmcloud.com/blog/2025-01-09-wasmcloud-operator-bringing-the-benefits-of-wasm-to-kubernetes/ https://wasmcloud.com/blog/2025-01-09-wasmcloud-operator-bri... This will provide you an equivalent experience to what you might expect from Kwasm, with the major difference being that you will not need to change the underlying Kubelet in any way while still getting the benefit of being able to deploy WebAssembly components natively on Kubernetes.