CNCF CloudEvents Project: A Step Towards Serverless Interop
summary
CloudEvents defines a tiny interoperable event header set — required fields: id, source, specversion, type — with HTTP binary and JSON structured encodings and protocol mappings (AMQP, MQTT, protobuf). Version 0.3 adds subject and data_ref, SDKs exist for multiple languages, and 1.0 aims to ship soon. Knative converts incoming events to CloudEvents, and an airport demo using a QR‑driven web client shows multi-vendor flows (demo suffers network glitches). SDKs and JSON/HTTP bindings
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:22History
- 2:29What are Events
- 3:59Goals
- 5:00Metadata
- 6:58Example
- 7:12CloudEvents Spec
- 9:00Structure Format
- 9:58Project Updates
- 11:24Project Littles
- 12:50Status
- 15:33Demo
- 15:45Demo History
- 16:16Mad Libs
- 16:54Airport Ecosystem
- 17:44Airport Demo
- 18:57IBM Coffee Demo
- 21:55CloudEvents Demo
- 22:09Useful Links
- 22:23Wrap Up
- 23:07Questions
related talks
30mCNCF CloudEvents Project: A Step Towards Serverless Interop
28mCloudEvents - A First Step Towards Serverless Interop
35mIntro: CNCF Serverless WG/CloudEvents
31mIntro: CNCF Serverless WG / CloudEvents
01h 19mCloudEvents - Intro, Deep-Dive and More!
26mCNCF Serverless WG: CloudEvents and Serverless Workflow
37mThe Serverless and Event-Driven Future
37mCNCF Serverless WG: Where Do We Go From Here?