Migrating AsyncAPI 2.6 to 3.0 Safely with Backward Compatibility Checks
summary
Live demo migrates an AsyncAPI 2.6 spec to 3.0 using a converter, Kafka in Docker, a Spring Boot order service, and Specmatic to generate contract tests from examples; initial mock-server tests fail because the converter cannot infer a request-reply pattern encoded as examples so two reply mappings are manually added; rerunning the 3.0 mock with the original 2.6 tests passes, proving the spec-vs-spec backward compatibility checks catch behavioral mismatches early (default timeout ~5s).
AI-written summary · about
chapters (11)
- 0:00AsyncAPI migration intro
- 1:07System architecture context
- 2:30AsyncAPI 2.6 contract testing
- 6:02Motivation for AsyncAPI 3.0
- 7:50Safe conversion to 3.0
- 10:20Mock servers for issues
- 13:33Backward compatibility checks
- 14:35Validating AsyncAPI 3.0
- 16:03Generating contract tests
- 17:46AsyncAPI tools for testing
- 18:30Q&A on migration
related talks
31mUnifying OpenAPI & AsyncAPI : Designing JSON Schemas+Examples.
39mIntroduction to AsyncAPI for Apache Kafka
08h 51mAsyncAPI Conference 2021 - Day 3
51mMajor Migrations Made Easy
19mGenerating & Using AsyncAPI Specs from Real-World API Data
19mAutomate your API to perfection
35mAPI-First! Contract-First! Make API development great again!
08mMy Journey from Contributor to a TSC Member at AsyncAPI