Getting Started with AsyncAPI
summary
AsyncAPI v2 specifies a single file per application (YAML used here) with four sections: info, servers, channels, components; bindings hold protocol details. The demo uses AsyncAPI v2 YAML, runs a local Mosquitto MQTT broker, and generates a Node client with the Node.js code generator from the asyncapi cli, then npm installs and connects: the generated app subscribes to claim status and claims processed topics and successfully publishes and receives JSON messages.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:55Structure
- 4:33Server Object
- 8:01Channel Objects
- 8:53Claim Status
- 9:41Publish Operation
- 13:23Demo
- 15:04Node Js Template
- 15:51Npn Install
- 17:04Publish a Message to the Broker
- 20:45Open Api Code Generators
- 21:49Bake Breaks
related talks
39mHow to document a Socket.IO API?
22mAsync API Specification 2.0
43mDesigning Event-driven architectures with AsyncAPI
31mAsyncAPI is here to stay
57mManaging Asynchronous APIs
42mAsyncAPI Recipes for EDA Gourmet
13mEverything You Wish To Know About The AsyncAPI Community
01h 03mOpenAPI and AsyncAPI, when to use which and why