Contract-Driven Development for Event-Driven Architecture.
summary
Shows migrating AsyncAPI 2.6 specs to 3.0 and proving zero behavior change by running the old spec as tests against a Specmatic mock server created from the 3.0 spec over Kafka, validating examples-as-test-data and catching mismatches like an enum/value or price type before deployment. Demonstrates AsyncAPI 3.0 request-reply support, local contract tests and mocks, schema validation that rejects invalid examples, and mutation-style resiliency checks that generate malformed inputs.
AI-written summary · about
chapters (11)
- 0:00Contract-driven development intro
- 2:08Sync API 2.6 with Kafka demo
- 7:15AsyncAPI 2.6 to 3.0 migration
- 17:36Contract test anatomy
- 21:14AsyncAPI 3.0 contract testing demo
- 27:13Mocking providers for testing
- 35:27Examples in API specs
- 38:17API governance design-first
- 41:47Backward compatibility in CI/CD
- 46:42Resiliency testing with AsyncAPI
- 50:40Parallel dev benefits
related talks
50mContract-Driven Development
06h 45mAsyncAPI Conf - Day 3 - 5th Nov 2022
24mUsing API spec as an Executable Contract To Mock and Test Microservices
27mAsyncAPI & The future of API specs
22mAsync API Specification 2.0
30mAsyncAPI v3: Streamlining Event-Driven API Design
51mContract-Driven Development-Escape Microservices Integration & Deployment Hell
46mManaging Event Driven Architectures