there are couple of things also
ie. wasm modules can be published and consumed to/from oci registries, which is nice
this linking is interesting also - ie. in docker you don't dynamically load other container to import functionality, but with wasm you can and because they're small you can architect your system around independent modules that use each other directly
they use nats for comms
and you can probably run your orchestrated system in browser - may sound silly but it's interesting capability as well
"More than 20 programming tools vendors offer some 26 programming languages — including C++, Perl, Python, Java, COBOL, RPG and Haskell — on .NET. "
-- https://news.microsoft.com/2001/10/22/massive-industry-and-d...
Same old, sold with a rebranded package.
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.