Consumer driven contracts in a polyglot world
summary
A concrete recipe for preventing consumer breakage using Spring Cloud Contract and a homegrown Contract Checker that registers artifacts in Nexus during CI, records which contract versions a service produces and consumes, and runs compatibility checks by launching a Docker stub runner to execute consumer contracts against producer stubs. Example: a date formatting change that broke frontends becomes caught by contract tests. Approach scales to 50+ microservices across 5 teams, supports non‑JVM frontends, and gates deployments when contract versions mismatch.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:20Story time
- 2:10History
- 2:46Software
- 3:43Monolith
- 5:53Microservices
- 7:07Contracts
- 9:33Test pyramid
- 11:25Contract testing
- 13:07Example contract
- 14:14Spring Cloud Contract
- 17:52Spring Stop Runner
- 20:55Consumer driven contracts
- 26:00Contract checker
- 27:15Predeployment check
- 29:47Demonstration
- 36:47Recap
related talks
01h 04mConsumer Driven Contracts and Your Microservice Architecture
47mCollaborative Contract Driven Development
49mCollaborative Contract Driven Development
30mManaging APIs and Contracts in a Microservices World Using Spring Cloud Contract
17mConsumer driven development with Spring cloud contract
01h 00mTesting Microservices and Evolving APIs with Consumer Driven Contracts
43mEnhancing Backend Microservices Ecosystem with Contract Testing
39mWhy you should contract test your Microservices 🧭