Elevating Serverless Platforms with Wasm Components
summary
American Express converts its FaaS into a polyglot, high‑density runtime by compiling functions to Wasm components and running them on wasmCloud capability providers, enabling native binaries for heavy IO (DB pools) while keeping business logic as tiny Wasm components. Platform automation generates Go modules, WID interfaces and OCI component artifacts; 1,500 active developers use the platform today. Dynamic linking, secret/config reuse, and a component Explorer for OCI‑deployed components reduce cold starts and shrink function packages; runtime is working in staging, production rollout is imminent.
AI-written summary · about
chapters (12)
- 0:00Serverless and Wasm components
- 3:34Our FaaS platform
- 11:49Multi-language support challenges
- 13:14Why Wasm components
- 15:04Why Wasm Cloud runtime
- 18:35Compiling and deploying Wasm
- 21:07Reusing platform capabilities
- 22:54Developer reuse with Explorer
- 24:19Wasm Cloud contributions
- 25:27Function dev workflow demo
- 29:47Status and future plans
- 35:39Q&A on security
related talks
22mPlatform Engineers assemble! Create your FaaS Platform using WASM
32mCloud Native Apps with Server-Side WebAssembly
41mRevolutionizing Cloud Native: WebAssembly's Role in Serverless...
28mI Wasm’t Expecting This Many Apps: Scaling Without Losing Your Bytes
19mWebAssembly's Journey Beyond the Browser
18mCloud Native & WebAssembly: Better Together
56mEdge-native applications - what happened to cloud-native?
25mFrom Cloud to Edge computing - Unleashing the power of WebAssembly at the edge