CloudEvents - Looking Beyond Event Delivery
summary
CloudEvents defines a required four-attribute context (id, source, specversion, type) plus optional data content type, data schema, subject and time, and maps those into HTTP structured or HTTP binary headers or transports like Kafka, MQTT, AMQP, NATS. SDKs exist for Go, Java, JS, Python, C#, Ruby, PHP and Rust. Interoperability work adds an OpenAPI discovery API, a subscription API and a schema registry; example: GitHub event type com.github.create.branch with id as a UUID and data content type application/json.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:52What Is Cloud Events
- 2:53Http Binaries Transport
- 5:51History
- 6:22Interoperability
- 7:53Discovery Api of Cloud Events
- 8:40Subscription Api
related talks
33mCloudEvents And Beyond!
28mCloudEvents - A First Step Towards Serverless Interop
41mOpen Standards for Building Event-Driven Applications in the Cloud
01h 04mCDEvents Project Summit
19mAdopting CDEvents and Embracing Interoperability
27mAsyncAPI and the World Wide Flow
52mNavigating complexity in event-driven architectures: A domain-driven approach
37mBuilding Event-driven Apps at Scale