Validating Event Driven Architecture (EDA) with AsyncAPI
summary
Relayr adopts AsyncAPI to validate Kafka and MQTT messages across 30–40 microservices with over 50 message types. A small open-source library, asyncapi-validator (npm), uses AJV-based JSON Schema validation to check payloads: runtime logging for device messages and test-time checks for internal Kafka. Schemas become the authoritative source, reducing README drift, speeding code reviews with a schema-first workflow, and allowing the team to flip from passive logging to rejecting invalid messages when desired.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 1:31Our use case and EDA challenges
- 2:58What is AsyncAPI and why it matters
- 4:22AsyncAPI playground and schema example
- 7:13Problems with undocumented EDA
- 9:05Documentation with AsyncAPI
- 10:30AsyncAPI validator demo
- 13:18Production validation workflow
- 15:44Use cases and team adoption
- 17:35AsyncAPI community and future
related talks
42mAsyncAPI Recipes for EDA Gourmet
03mWhy AsyncAPI Is Essential for Modern Event-Driven Architectures
22mAsync API Specification 2.0
20mAPI Management for Event-Driven Microservices
31mAsyncAPI is here to stay
27mAsyncAPI & The future of API specs
57mManaging Asynchronous APIs
26mAsync API for Event Driven Architecture