Orchestrating Wasm: Reconciliation Loops Aren't Owned by Kubernetes
summary
Cosmonic builds the wasmCloud Application Deployment Manager (Wadm) as a custom orchestrator instead of extending Kubernetes or Nomad, because it needs native component semantics and global multi‑region scheduling. Wadm consumes Open Application Model manifests (OAM), runs a scaler per component, uses NATS JetStream as a durable event store, and reconciles state from multiple independent Wadm instances. Demos show deployments across DigitalOcean, Azure, GKE and an ARM host, a Redis KV example, and a production backend with ~23 actors and 10 providers successfully running.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:48What is Wasm Cloud
- 4:16Custom orchestrator vs Kubernetes
- 7:05Orchestrator design
- 10:36WADM reconciliation loop
- 13:22NATS JetStream resilience
- 14:27Live demo: WADM
- 18:16Distributing components
- 19:21Adding a data store
- 20:44Kubernetes clusters
- 22:09WADM at Cosonic
- 23:12WADM future plans
- 23:52Call to action
- 24:14Q&A
related talks
28mWasm + Kubernetes: Beyond Containers
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
08mKWasm Operator - The Easy Way for Running WebAssembly on Kubernetes
36mWho Knew Dogfood Could Taste This Good? A WebAssembly In Production Story
39mMind the Gap Between the Future and the Present
26mHelping One of Europe's Banks Re-platform with Declarative, Self-healing, Multi-cloud WasmCloud Clusters on Kubernetes
18mCloud Native & WebAssembly: Better Together
31mHow We Can Create a Thriving Wasm Ecosystem