Revolutionizing Cloud Native: WebAssembly's Role in Serverless...
summary
WebAssembly replaces cold-start containers by running components that boot in <1 millisecond versus ~200–500 ms for VMs, packaged as OCI artifacts and deployed with Spin and Spin Cube. The stack uses containerd shims plus runtime class manager (kwam) and a Spin operator to run wasm modules on AKS, supports runtime-configured Redis and remote GPU inference (Fermyon Cloud) for a demo sentiment app, and reports 60% cost savings in one case study.
AI-written summary · about
chapters (24)
- 0:00Speakers and talk overview
- 1:44Defining serverless
- 2:27Problems with first-wave serverless
- 6:18WebAssembly for serverless challenges
- 6:38What is WebAssembly
- 8:25Spin and developer experience
- 10:35Spin CLI demo
- 12:21Spin apps to external resources
- 14:05SpinKube for Kubernetes
- 15:28SpinKube and Kubernetes
- 17:14Zeiss Group case study
- 18:40Separation of concerns
- 21:03SpinKube custom resource
- 23:50SpinKube runtime config
- 24:13Sentiment analysis demo
- 29:37Local sentiment testing
- 30:40Spin apps on AKS
- 34:18Final demo and Q&A intro
- 35:22Get involved with Spin
- 36:25Q&A: Browser requirements
- 37:49Q&A: Debugging components
- 38:30Q&A: Supported languages
- 39:15Q&A: SpinKube cluster integration
- 40:19Q&A: OCI compliance
related talks
24mA Greener, Cost Effective Cloud with Serverless WebAssembly
44mA Greener, Cost-Effective Cloud with Serverless WebAssembly
30mA Greener, Cost-Effective Cloud with Serverless WebAssembly
36mA Greener, Cost-Effective Cloud with Serverless WebAssembly
26mWebAssembly as a cloud-native runtime for serverless functions
30mThe Future of the Cloud is WebAssembly
08mKeynote: How WebAssembly can Power the New Wave of Serverless AI
25mBuilding Serverless AI Apps with Spin and WebAssembly