Collaborative Contract Driven Development
summary
Shows how Spring Cloud Contract turns API agreements into executable tests that validate a service and produce a stubs artifact for clients to run locally. Demonstrates Groovy and YAML contract formats, Docker images that run contract validation and a mock server (example stub run on port 9876), matcher rules to allow flexible headers and numeric IDs, and how mismatched contracts fail CI. Covers both consumer-driven contracts and producer-driven flows, plus messaging support beyond HTTP.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:05What is Contract Driven Development
- 2:33Why should you care
- 5:11Undocumented API
- 6:38Serial Path
- 7:42Parallel Development
- 9:36The Situation
- 11:50Why
- 16:01Collaborative Process
- 16:11ConsumerDriven Context
- 16:59Collaboration Importance
- 17:45Polyglot
- 18:01Language Independent Tools
- 19:44Docker Images
- 20:04Stalker Image
- 20:23Docker Image
- 24:43Validate Service
- 27:35Data Changes
- 29:03More Data
- 30:27Everly failures
- 31:23Consistent behavior
- 32:56Flexibility
- 34:34JSON
- 36:15Errors
- 38:29Mock Producer
- 40:04Contract Defined Services
- 41:51Final Points
- 43:29Other Questions
- 44:29Real World Example
related talks
49mCollaborative Contract Driven Development
30mManaging APIs and Contracts in a Microservices World Using Spring Cloud Contract
01h 04mConsumer Driven Contracts and Your Microservice Architecture
17mConsumer driven development with Spring cloud contract
45mREST and Messaging contracts with Spring Cloud Contract
45mContract Driven Development in AsyncApi
38mConsumer driven contracts in a polyglot world
42mInvestigating Contract Testing