TMForum's AsyncAPIs For a New Era of Event-Driven Architecture
summary
TM Forum announces adoption of AsyncAPI 3.0 across 100+ TMF APIs (more than 1 million downloads) and maps REST verbs to asynchronous command/request‑reply channels using Kafka brokers. A Dockerized CTK conformance toolkit and Specmatic virtual service generate async API specs, spin up Zookeeper/Kafka, run payload tests and produce pass/fail reports; demo shows automated generation of Docker images, some intentional failures for debugging, and end‑to‑end validation for certification.
AI-written summary · about
chapters (22)
- 0:00AsyncAPIs in telecom
- 1:29Time synchronization history
- 4:00TM Forum mission
- 6:08TM Forum Open APIs adoption
- 10:25Why AsyncAPI matters
- 13:17Event-driven telecom
- 15:49Autonomous networks
- 16:53Composable IT systems
- 20:08Legacy modernization APIs
- 21:30AI data stream needs
- 22:36REST vs event API
- 24:46Events vs commands
- 26:34REST verbs mapping
- 28:01AsyncAPI patterns
- 29:04OpenAPI vs AsyncAPI profiles
- 30:13AsyncAPI certification
- 31:39Conformance toolkit
- 37:17AsyncAPI tooling demo
- 47:30Conformance overlays
- 48:13Workflow validation
- 51:31Future developments
- 53:00Closing remarks
related talks
31mSpecify Your Asynchronous APIs with AsyncAPI
31mAsyncAPI is here to stay
27mAsyncAPI & The future of API specs
30mAsyncAPI v3: Streamlining Event-Driven API Design
03mWhy AsyncAPI Is Essential for Modern Event-Driven Architectures
44mAsyncAPI – Swagger for asynchronous APIs
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
39mIntroduction to AsyncAPI for Apache Kafka