Open Standards for Building Event-Driven Applications in the Cloud
summary
Demonstrates that CloudEvents provides a concrete event envelope for routing (supports binary and structured modes, JSON/Protobuf, HTTP/Kafka bindings) and AsyncAPI documents servers, channels, publish/subscribe ops and message schemas, with AsyncAPI Studio, CLI and code generators producing working Node.js (MQTT demo that receives messages) and Spring templates; shows how CloudEvents can be modeled in AsyncAPI via payload references or CloudEvents headers as traits, notes SDK/protocol limitations and Google Cloud Pub/Sub bindings and links to GitHub demos.
AI-written summary · about
chapters (10)
- 0:00Introduction to event-driven apps
- 3:15Key concepts in event-driven architecture
- 7:33Why CloudEvents matter
- 10:24CloudEvents formats and modes
- 15:45CloudEvents SDKs and limitations
- 17:33Introducing AsyncAPI
- 22:32AsyncAPI vs OpenAPI differences
- 27:11Publish/subscribe semantics in AsyncAPI
- 34:17Combining CloudEvents and AsyncAPI
- 38:19Q&A and closing remarks
related talks
28mCloudEvents - A First Step Towards Serverless Interop
01h 19mCloudEvents - Intro, Deep-Dive and More!
33mCloudEvents And Beyond!
27mAsyncAPI and the World Wide Flow
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
46mManaging Event Driven Architectures
14mCloudEvents - Looking Beyond Event Delivery
21mCloudEvents - v1.0 and Beyond - Discovery/Subscriptions