Seamless Upgrades: Mastering API Compatibility

on YouTube ↗44m

" summary

Claims that updating the API spec first uncovers breaking changes immediately and lets teams develop in parallel with consumer stubs. Uses Specmatic to spin up a mock from an OpenAPI change, runs old-spec contract tests against the new mock, and finds a missing mandatory field; tests expand from 3 to 7 as optional combinations are added. Shows in-memory Kafka/AsyncAPI stubs, CI gating of contract checks, and a workflow that defaults missing cancelable to false so the change remains backward compatible—i.e., it works.

AI-written summary · about

" chapters (10)

1. 0:00Seamless API upgrades
2. 1:10Testing approaches for upgrades
3. 4:28Why version skew matters
4. 6:00API compatibility challenges
5. 8:57Speaker background
6. 10:02API evolution example
7. 14:04Contract-driven development demo
8. 23:20Contract changes in CI/CD
9. 29:35Contract-driven workflow summary
10. 36:44Specmatic and alternatives Q&A

" related talks

• 51mContract-Driven Development-Escape Microservices Integration & Deployment HellNaresh · Agile India 2023
• 24mUsing API spec as an Executable Contract To Mock and Test MicroservicesHari Krishnan · AsyncAPI Online Conference 2024
• 37mStop Doing E2E Tests! Write Better Tests with ContractMarkus Oberlehner · Frontend Nation 2025
• 30mBreak the API Test Data Bottleneck: Real Scenarios on Real SystemsAnand Bagmar · apidays India 2026
• 20mOpenAPIspecTaylorBarnett · API the Docs Paris 2018
• 24mBreaking the Interface - API Versioning with REST, JSON and SwaggerThomas Bayer · apidays Helsinki 2019
• 33mKafka and JMS Mocking with AsyncAPI using SpecmaticHari Krishnan · AACoT 2023 Bangalore
• 50mRun Specs & Avoid Wrecks — A "Speed With Seatbelts" LabJoel Rosario · Apidays India 2025