An Auto-Documenting Event-Driven Architecture Using Async API and Inngest
summary
System captures JSON events with a v version field and publishes them to a per-workspace registry (separate prod and test). A worker parses each payload, generates a Q definition that becomes JSON Schema, versions and stores it, and a small npm package uses those schemas to emit an AsyncAPI YAML spec usable in AsyncAPI Studio. Typescript types and SDK code are generated, the parser is open source on GitHub, and the pipeline runs in production at Inngest today. captures JSON events with a v field parses to Q then JSON Schema then AsyncAPI
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:12Agenda
- 0:36Dan Farrelly
- 1:15Inngest
- 3:08Events
- 3:58Async API
- 5:29Json
- 6:54Q
- 8:12Architecture Diagram
- 9:56Event Schema Registry
- 11:16Async API Integration
- 13:35Generating the Spec
- 17:06Outro
related talks
22mUsing Async API schema to define event driven architecture with AWS SNS
22mAsync API Specification 2.0
39mEvent Design with AsyncAPI, DDD, and AI
27mAsyncAPI & The future of API specs
57mManaging Asynchronous APIs
22marmonizing Asynchronous Systems: NATS, CloudEvents and AsyncAPI.
31mAsyncAPI is here to stay
30mElevating Event-Driven Architecture: Boost your delivery with AsyncAPI and Microcks
