Hierarchical Integration of WebAssembly in Serverless for Efficiency and Interoperability
summary
A hierarchy places many WebAssembly modules inside larger container sandboxes to preserve container semantics while packing tenants for density; implementation called Wasabi integrates with Knative and WasmEdge with under <2k LOC change, runs on a 9-node test cluster (~100 cores, 200 GB RAM), and combines resource-aware scaling, queuing, overbooking, memory preallocation and thread cgrouping. Results show roughly 10x resource reduction (16 containers versus ~1,000 starts) while matching or improving service-time percentiles.
AI-written summary · about
chapters (9)
- 0:00Serverless computing challenges
- 2:23Why serverless is expensive
- 5:54WebAssembly basics
- 8:24Balancing Wasabi integration
- 11:51Wasabi optimizations
- 13:35Implementation and setup
- 14:19Resource allocation with Wasabi
- 15:21Performance and scaling
- 16:22Conclusion and future
related talks
41mRevolutionizing Cloud Native: WebAssembly's Role in Serverless...
28mWasm + Kubernetes: Beyond Containers
38mCloud-Native WebAssembly: Containerization On the Edge
41mOptimizing Microservices with WebAssembly and Linux Containers: Exploring Hybrid Contain...
22mCreate an Extensible Cloud Native Application with WebAssembly
19mWebAssembly's Journey Beyond the Browser
24mA Greener, Cost Effective Cloud with Serverless WebAssembly
08mKeynote: WebAssembly in a Containerized World
