Micro-Service Delivery Without the Pitfalls
summary
Argues that consumer-driven contract testing prevents last-minute integration failures by generating machine-readable contracts from unit tests and verifying them against real services using Pact and a centralized Pact Broker. Developer tests spin up a mock HTTP server, produce JSON pact files, provider CI replays requests and records pass/fail in a matrix so the pipeline can answer Can I deploy quickly. Notes caveats: provider states, test data setup, and weaker guarantees for static Pactflow checks.
AI-written summary · about
chapters (11)
- 0:00Microservice delivery challenges
- 8:28Distributed monoliths pitfalls
- 16:14Software contracts importance
- 22:16Test doubles risks
- 26:33Explicit vs implicit contracts
- 31:52Contract testing fundamentals
- 41:16Consumer-driven contracts
- 47:37Microservices deployment pipelines
- 54:18Introducing Pact
- 1:03:50Pact Broker confidence
- 1:11:11Contract testing benefits
related talks
59mUsing Pact to Deploy Microservice with Confidence
24mHow to test microservices and stay sane
39mPacts to the Rescue! Making your microservices play nicely together
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
47mContract-Based Testing for Microservices and UI
39mWhy you should contract test your Microservices 🧭
22mMicro Testing Pains
01h 02mAvoiding Common Pitfalls With Modern Microservices Testing