Who Knew Dogfood Could Taste This Good? A WebAssembly In Production Story
summary
Cosmonic runs its entire backend as WebAssembly modules on the wasmCloud runtime, proving Wasm is production-ready by operating the platform in prod with services sized ~250 KB each (three replicas ≈750 KB per service). The system uses NATS message bus, Redis and Vault providers, OpenTelemetry tracing (which cuts mean time to resolution), Nomad for scheduling and Firecracker microVMs for untrusted binaries. Capabilities swap at runtime with no recompiles, event sourcing and reactive actors handle ingress and scaling.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:58Neither Web, nor Assembly
- 3:03But there are some gaps
- 4:03Modern Computing Env
- 6:32wasmCloud Application Runtime
- 7:06Capabilities
- 7:52Lattice Network
- 8:20What is Cosmonic?
- 10:58Dogfooding 101
- 11:59What tech do we use?
- 13:36Debugging and getting saved by Tracing
- 14:22An infrastructure provision trace
- 14:55Speed and Scale
- 15:49Event Sourcing and Reactive Programming
- 20:29Abstracting over Infrastructures
- 21:25Defense in Depth
- 23:40Welcome to the Bleeding Edge
- 25:02Wasm Pros vs Cons
- 28:09wasmCloud-Specific Lessons
- 30:12For Cosmonic
- 32:20References
related talks
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
18mCloud Native & WebAssembly: Better Together
28mWasm + Kubernetes: Beyond Containers
31mFrom Napkin to the Cloud: A WebAssembly Journey
19mWebAssembly's Journey Beyond the Browser
13mLightning Talk: Wildly Distributed Programming: Wasm and the Future of Distribute...
40mWebAssembly - The Future of Distributed Computing
22mCreate an Extensible Cloud Native Application with WebAssembly