Testing Microservices and Evolving APIs with Consumer Driven Contracts
summary
Describes using consumer driven contracts to catch breakages at build time by recording outgoing calls as pacts, publishing them to a Pact Broker, and having providers pull and verify those pacts in CI so consumer and provider compatibility is proven before deploy. Shows a live Pact JVM demo that generates a pact, publishes it, and verifies failures caused by missing routes or state callbacks. Notes limits: not a replacement for end‑to‑end tests and adds CI and state management complexity.
AI-written summary · about
chapters (5)
- 0:00Introduction and challenges
- 8:23Consumer-driven contracts explained
- 13:14Pact framework overview
- 37:53Live coding demo attempt
- 57:08Implementation tips and resources
related talks
45mDeploy microservices confidently using Consumer Driven Contracts
32mConsumer-Driven Contract: A better approach for API Testing
10mDeploy microservices confidently using Consumer Driven Contracts
39mWhy you should contract test your Microservices 🧭
09m"Contract Testing 101"
42mDeploy microservices with Certainty
59mUsing Pact to Deploy Microservice with Confidence
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#