WASM-Native Orchestration
wasmcloud.com
WASM-Native Orchestration
1–10 of 64 posts
Re: WASM-Native Orchestration
#2What are some real life use cases for this, instead of let's say edge functions or durable objects etc?
Re: WASM-Native Orchestration
#3I feel like this landing page has so many buzzwords I don't quite understand what the application/project itself is, but I do understand it's universal, runs everywhere and can run anything anywhere.
Could someone who knows what it is, give a simpler description? Is it a OS/kernel? Runtime? Orchestrator? Self-hosted platform? Cloud platform?
Re: WASM-Native Orchestration
#4Mh... I would be most interested in how this could be used for running a local-first software infrastructure cloud. Does anyone has maybe some infos in how it could be used in that way ?
Re: WASM-Native Orchestration
#5I feel like this landing page has so many buzzwords I don't quite understand what the application/project itself is, but I do understand it's universal, runs everywhere and can run anything anywhere. Could someone who knows what it is, give a simpler description? Is it a OS/kernel? Runtime? Orchestrator? Self-hosted platform? Cloud platform?
k8s is for docker containers, this thing is like k8s but for wasm (and even uses similar apis).
Re: WASM-Native Orchestration
#6I feel like this landing page has so many buzzwords I don't quite understand what the application/project itself is, but I do understand it's universal, runs everywhere and can run anything anywhere. Could someone who knows what it is, give a simpler description? Is it a OS/kernel? Runtime? Orchestrator? Self-hosted platform? Cloud platform?
k8s is for docker containers, this thing is like k8s but for wasm (and even uses similar apis).
Ok, so wasmCloud is like Kubernetes, but then I don't understand their tagline: "Build, manage, and scale Wasm apps across any cloud, K8s, or edge" or the "Run wasmCloud standalone or on Kubernetes" part.
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?
Re: WASM-Native Orchestration
#7Earlier quoted context omitted.
k8s is for docker containers, this thing is like k8s but for wasm (and even uses similar apis).
Ok, so wasmCloud is like Kubernetes, but then I don't understand their tagline: "Build, manage, and scale Wasm apps across any cloud, K8s, or edge" or the "Run wasmCloud standalone or on Kubernetes" part. 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?
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
#8Too much marketing fluff on the website. How about showing simple example as how is it easier or useful to deploy some service to fly.io , AWS or GCP or maybe a Postgres deployment to Digital Ocean, Render or whatever. I want to use it but before I want to know how can I move my dependency from managed XYZ and easily run/manage my own deployment of databas, services.
Re: WASM-Native Orchestration
#9What are some real life use cases for this, instead of let's say edge functions or durable objects etc?
This is an abstraction on top of edge functions. So you do not have to tie into a provider like Cloudflare. At least that is suggested.
An orchestration engine like this will replace k8s one day. Kubernetes is great for enterprise development, but just too knowledge intense to get most out of it.
Re: WASM-Native Orchestration
#10What are some real life use cases for this, instead of let's say edge functions or durable objects etc?
I think it starts to be interesting because wasm modules are so lightweight it opens interesting ways of orchestration.
Each node can easily have copy of every deployed module.
Having modules locally means you can skip network and just call functions in memory directly.
Startup time is also tiny.
Scaling by replication is so efficient that it becomes a whole new thing (on demand, extremely high upper limits, write easy serial code everywhere and scale it for concurrency).
etc.
The whole thing is lightweight and performant enough that it could as well be part of OS.
Looks like early days of the future and like people say has potential of dethroning docker.
K8s will probably eventually have first class support for wasm but it may not dovetail so much with their current setup.
If they don't keep up somebody else is going create wasm orchestration that takes advantage of that and this wasm-native orchestration seems to be doing just that.
Ie. this "link" type looks like wasm linking, it's a bit like dynamic linking of libraries for native apps.