Deploy microservices confidently using Consumer Driven Contracts
summary
Shows exactly how Consumer Driven Contracts catch real breaks using the Pact framework: consumer test generates a JSON pact for a POST /v1/person create that gets published to the Pact broker, provider runs a verification job against a live app and fails on missing state or renamed field. Demo fixes include adding a provider state, mapping SSN to SocialSecurityNumber during serialization, adding GET /v1/person/{id}, and safely migrating to v2 while keeping consumers green. No integration environment or deployment required.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:50The problem
- 3:28How to avoid dependencies
- 15:17Demo
- 15:49Endpoint
- 17:59Create headers
- 19:00Create body
- 19:57Create pact
- 21:04Pact Broker
- 21:43Dependency graphs
- 22:23Pact verification test
- 23:30Adding another pact
- 24:54Status of the pact
- 25:44Why does it fail
- 27:24Consumer Driven Development
- 32:42Address
- 34:28Create API Version 2
- 41:19Summary
related talks
10mDeploy microservices confidently using Consumer Driven Contracts
01h 00mTesting Microservices and Evolving APIs with Consumer Driven Contracts
59mUsing Pact to Deploy Microservice with Confidence
42mDeploy microservices with Certainty
32mConsumer-Driven Contract: A better approach for API Testing
22mCollaborating with Contracts
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
39mPacts to the Rescue! Making your microservices play nicely together