Deploy microservices with Certainty
summary
Shows that consumer-driven contract tests stop accidental production breakage by example: a deployed change removes a JSON field and causes a runtime error and rollback. Uses pact to generate a contract from a consumer test, a stub HTTP server to exercise gateways, and a pact broker or artifact store to share pacts. Pipeline runs consumer contract publish then provider verification against staging and production contracts so deployments pass only when the real provider matches the recorded interactions.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:33Micro Services architecture
- 2:15Villains Database Application
- 8:39Unit Tests (and Mocks)
- 10:15Integration Tests
- 12:35Ownership
- 14:12Consumer Side
- 34:50Deploy with Certainty
- 35:05Deploying Consumer
- 37:43Deploying Provider
- 40:22Conclusions
related talks
32mDeploy microservices with Certainty
45mDeploy microservices confidently using Consumer Driven Contracts
59mUsing Pact to Deploy Microservice with Confidence
10mDeploy microservices confidently using Consumer Driven Contracts
01h 00mTesting Microservices and Evolving APIs with Consumer Driven Contracts
39mPacts to the Rescue! Making your microservices play nicely together
01h 21mMicro-Service Delivery Without the Pitfalls
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
