Re:WASM-Native Orchestration
by jcmfernandes on Thursday February 13, 2025 @01:19PM
(#43039299)
You use k8s to manage the machines where wasmCloud runs, and wasmCloud to manage the WASM apps that run on top of it. That's at least my understanding.
Re:WASM-Native Orchestration
by magicalhippo on Thursday February 13, 2025 @05:57PM
(#43042549)
And then you run QEMU-WASM[1] on that so you can run your Docker containers safely inside a Linux VM...
Re:WASM-Native Orchestration
by jcmfernandes on Thursday February 13, 2025 @06:48PM
(#43042956)
Gary was a visionary: https://www.destroyallsoftware.com/talks/the-birth-and-death...
As one of the co-founders of CNCF wasmCloud, I can say this talk was ABSOLUTELY an inspiration for what we've been working towards!
Re:WASM-Native Orchestration
by brooksmtownsend on Friday February 14, 2025 @09:48AM
(#43048871)
That's what people do in enterprises because they have security controls and processes around k8s with too much investment. It's a no-go telling people to "just run this binary on this VM/baremetal machine", understandably.
We've got a few examples on our website from users that (in my opinion) use wasmCloud more for its strengths as a distributed computing platform. Often there's central k8s infrastructure where wasmCloud runs and connects to wasmCloud hosts running on edge devices. https://wasmcloud.com/blog/2024-10-22-webassembly-adoption-t....
Me personally, I run all my side projects off of a wasmCloud binary on Oracle's always free tier instance and it's been pretty awesome.
Why would you want to run a orchestrator (wasmCloud) on top of another orchestrator (Kubernetes)? Are they competitors? No, then it wouldn't make sense to run it on Kubernetes, so that makes them complements?