Collaborative Contract Driven Development
summary
Claim: programmatic API contracts let clients and services develop in parallel and stop flaky integration tests. Uses Spring Cloud Contract with Groovy/HAML contracts, a Maven plugin that runs 4 passing contract tests against a sample produce service, generates WireMock/JSON stubs and Docker stub server images, and produces Asciidoctor documentation and stub artifacts for CI/CD. Demo shows a Docker-backed mock the Angular UI talks to reliably, tests succeed, and removing an endpoint breaks the contract tests as expected.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker info
- 2:32What is contract driven development
- 5:02Pain points without contracts
- 12:47Why Spring Cloud Contracts
- 18:05Producer vs consumer driven contracts
- 20:51Polyglot support with Docker
- 22:59Live demo of contracts
- 37:26Solving initial problems with contracts
- 42:00Final points and Q&A
related talks
47mCollaborative Contract Driven Development
30mManaging APIs and Contracts in a Microservices World Using Spring Cloud Contract
01h 04mConsumer Driven Contracts and Your Microservice Architecture
01h 21mContract Driven Development-Deploy MicroServices Independently W/out Integration Testing
45mContract Driven Development in AsyncApi
17mConsumer driven development with Spring cloud contract
51mContract-Driven Development-Escape Microservices Integration & Deployment Hell
38mConsumer driven contracts in a polyglot world
