Verifying Microservices in Chains without Chain Testing?
summary
A bank with 100+ teams maps a messy API landscape, adopts consumer-driven contracts stored in producer repositories, and replaces brittle end-to-end acceptance environments by running contract tests in CI with reusable stubs. Concrete results: earlier integration failures shrink from weeks of late feedback to immediate CI breaks, discovery of ambiguous fields (nil vs empty) and clearer consumer lists. They also ban multiple long‑lived branches and keep versions strict to avoid divergent contracts.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:40Question
- 1:20Agenda
- 1:45What is Chain Testing
- 4:21Chain Testing
- 5:21Contract Testing
- 7:05Agreement
- 7:17Problem
- 7:46Testing Perspective
- 9:32Tracking
- 11:14Testing
- 18:37Discussion
- 26:33Test
- 34:44Consumer Driven Contracts
related talks
39mWhy you should contract test your Microservices 🧭
24mHow to test microservices and stay sane
01h 21mContract Driven Development-Deploy MicroServices Independently W/out Integration Testing
43mEnhancing Backend Microservices Ecosystem with Contract Testing
22mMicro Testing Pains
47mContract-Based Testing for Microservices and UI
37mTesting in a Microservices Architecture
01h 04mConsumer Driven Contracts and Your Microservice Architecture