Contract-Driven Development-Escape Microservices Integration & Deployment Hell

on YouTube ↗51m

" summary

Argues that keeping API specs in a central git repo and generating executable stubs and tests from an OpenAPI spec lets teams shift left and avoid integration freezes; demo shows Specmatic pulling a contract and producing 44 generated tests that run locally and in CI. Claims this lets a service be validated in isolation (HTTP, Kafka, JDBC plugs), enables independent deploys across thousands of developers, and catches compatibility breaks before integration environments.

AI-written summary · about

" chapters (9)

1. 0:00Architecture challenges
2. 2:31Integration hurdles
3. 6:43Shift-left strategy
4. 12:37The test pyramid
5. 16:53Independent deployment
6. 21:03Contract-driven development
7. 27:56Defining the contract
8. 34:09Tooling and implementation
9. 44:23Conclusion and Q&A

" related talks

• 01h 21mContract Driven Development-Deploy MicroServices Independently W/out Integration TestingHari Krishnan, Joel Rosario · Agile India 2022
• 01h 20mContract Driven Development-Deploying MicroServices Without Integration TestingJoel Rosario, Hari · Selenium Conf 2022
• 50mContract-Driven DevelopmentNaresh Jain · YOW! Perth 2023
• 48mContract Driven Development: The Death of Integration HellNaresh Jain · Agile India 2020
• 49mCollaborative Contract Driven DevelopmentBilly Korando · Devnexus 2020
• 37mStop Doing E2E Tests! Write Better Tests with ContractMarkus Oberlehner · Frontend Nation 2025
• 45mContract Driven Development in AsyncApiJosé E. García Maciñeiras, Pablo J.López Rivadulla · AsyncAPI Conf 2022
• 01h 04mConsumer Driven Contracts and Your Microservice ArchitectureAdib Saikali, Marcin Grzejszczak · SpringOne Platform 2017