Enhancing Backend Microservices Ecosystem with Contract Testing
summary
Argues that adding contract tests between unit and integration tests finds API breakages far earlier, reducing costly end-to-end failures; demonstrates a CI flow where consumer/provider contracts publish to a Pact Broker and providers validate on every change. Recommends concrete stack details: Pact (pact.io), JVM/Spring Boot with JDK 17, Maven/Gradle dependency 4.6, and JUnit 5. Covers versioning, JWT/OAuth auth, and logging/monitoring practices; claims this removed late-found regressions in a fintech microservice environment.
AI-written summary · about
chapters (11)
- 0:00Contract testing introduction
- 1:29Speaker and session overview
- 4:00Microservices and contracts
- 8:40Contract testing in pyramid
- 10:25Contract testing components
- 15:30Rules and expectations in contracts
- 23:07Pact broker setup
- 28:13Real-world contract testing
- 31:08Q&A part one
- 32:33Q&A part two
- 41:51Closing remarks
related talks
39mWhy you should contract test your Microservices 🧭
01h 00mTesting Microservices and Evolving APIs with Consumer Driven Contracts
01h 21mMicro-Service Delivery Without the Pitfalls
24mHow to test microservices and stay sane
47mContract-Based Testing for Microservices and UI
22mMicro Testing Pains
01h 02mAvoiding Common Pitfalls With Modern Microservices Testing
39mPacts to the Rescue! Making your microservices play nicely together