armonizing Asynchronous Systems: NATS, CloudEvents and AsyncAPI.
summary
A small observability platform is built with Java Spring Boot services: a demo app, a metrics agent, a data-collector and a reporter, all exchanging NATS JetStream messages carrying CloudEvents gem payloads; AsyncAPI files document channels and reference JSON Schemas used to generate classes. AsyncAPI 3.0 uses explicit action send/receive so publishers and consumers map clearly. The live demo shows memory varying 2–4 GB and CPU 20–80% on the HTML dashboard, proving the pipeline and codegen approach work end-to-end.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:28Async vs sync systems
- 2:52JIT delivery metaphor
- 3:55NATS transport layer
- 4:38NATS distributed systems
- 6:24CloudEvents packaging
- 7:49CloudEvents adoption
- 8:11GEM acronym
- 9:15AsyncAPI route planner
- 10:39AsyncAPI interactions
- 12:27Demo observability setup
- 14:14Running observability demo
- 17:35Code and AsyncAPI integration
- 21:27Summary
related talks
07h 08mAsyncAPI online conference | #asyncapiconf
57mManaging Asynchronous APIs
43mAsyncAPI or CloudEvents? Both My Captain!
01h 03mOpenAPI and AsyncAPI, when to use which and why
31mAsyncAPI is here to stay
32mFrom Design to Code using AsyncAPI
42mAsyncAPI Recipes for EDA Gourmet
26mAPI Management, meet Event Management
