Cross-cloud App Splitting With WebAssembly Components
summary
Claim: one codebase compiles to WebAssembly and is split at deploy time so pieces run in different Kubernetes clusters, clouds, or edge locations. Uses Rust and TypeScript, the CNCF tool Spin, Helm and SpinKube to turn ~a dozen independently compiled Wasm components into a CMS demo (QR generator, front end, repo, admin). Demo runs locally end to end and deploys split across clusters; component sandboxes reduce boilerplate and surface-area for ops, though the component model is still maturing.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:47Monoliths vs microservices
- 10:32Monolith and microservice problems
- 19:38Cloud platforms evolution
- 27:28WebAssembly runtime
- 35:50WebAssembly Components
- 41:11Demo: component CMS
- 46:05Q&A
related talks
32mCloud Native Apps with Server-Side WebAssembly
01h 01mAn introduction to WebAssembly components
28mWasm + Kubernetes: Beyond Containers
50mWebAssembly: A Recovering Kubernetes Engineer's View of the Future
01h 03mTruly Portable Code: Serverless WebAssembly in a Distributed World
30mThe Future of the Cloud is WebAssembly
39mRunning WebAssembly on Kubernetes
30mShrinking Software Attack Surface with WebAssembly & CNCF Wasmcloud
