CNCF Serverless WG: Where Do We Go From Here?
summary
CNCF Serverless WG produces a white paper and a landscape spreadsheet, and ships CloudEvents to solve event routing by adding four minimal fields so middleware can route without parsing payloads: CloudEvents: id type source specversion. The spec is at 0.3 with JSON HTTP protobuf formats and SDKs now and aiming 1.0 in weeks. A workflow draft defines v0.1 state‑machine primitives: states steps triggers actions (it omits function signatures). Over 70 companies contribute, yet only a few report serverless in production.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:55Service Working Group
- 5:33Cloud Event Attributes
- 7:47Data Content Type
- 9:03Deliverables
- 10:32Workflow
- 11:24Basic Primitives
- 13:52Current State
- 15:24Questions for You
- 16:25Container Usage
- 17:29Use Cases
- 21:16Last Time
- 21:58Microservices vs Functions
- 23:58Scale to Zero
- 25:55Pain Points
- 29:42Current Workloads
- 31:50Summary
related talks
37mCNCF Serverless WG: Where Do We Go From Here?
31mIntro: CNCF Serverless WG / CloudEvents
01h 32mCNCF's Serverless WG - Tell Me Where it Hurts
26mCNCF Serverless WG: CloudEvents and Serverless Workflow
01h 27mIntro + Deep Dive: Serverless WG
34mDeep Dive: CNCF Serverless WG / CloudEventsClemens Vasters, Microsoft & Cathy Zhang
35mIntro: CNCF Serverless WG/CloudEvents
30mCNCF Serverless WG - Serverless Workflow Project Deep Dive