CNCF CloudEvents Project: A Step Towards Serverless Interop
summary
CloudEvents defines four required metadata fields (id, source, specversion, type) and transport bindings for HTTP JSON, AMQP and protobuf so events move between systems without touching business payloads. Project releases CloudEvents 0.3 with a new subject field, renamed data_content_type and a data_ref extension for external payloads; SDKs and Knative integration are available and a live airport demo sends heterogeneous events through middleware to trigger supplier and carrier actions.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:22History
- 2:29What are Events
- 3:59Goals
- 5:01Metadata
- 6:58Example
- 7:12CloudEvents Spec
- 9:00Structure Format
- 9:59Project Updates
- 11:25Project Littles
- 12:50Status
- 15:33Demo
- 15:45Demo History
- 16:17Mad Libs
- 16:56Airport Ecosystem
- 17:43Airport Demo
- 18:57IBM Coffee Demo
- 21:55CloudEvents Demo
- 22:14Useful Links
- 23:07Questions
related talks
30mCNCF CloudEvents Project: A Step Towards Serverless Interop
35mIntro: CNCF Serverless WG/CloudEvents
28mCloudEvents - A First Step Towards Serverless Interop
31mIntro: CNCF Serverless WG / CloudEvents
01h 19mCloudEvents - Intro, Deep-Dive and More!
26mCNCF Serverless WG: CloudEvents and Serverless Workflow
34mDeep Dive: CNCF Serverless WG / CloudEventsClemens Vasters, Microsoft & Cathy Zhang
37mThe Serverless and Event-Driven Future
