Beyond REST - Contract Testing in the Age of gRPC, Kafka & GraphQL
summary
Modern systems run many protocols (61% report multi‑protocol use) and a bank with 40 teams proves end‑to‑end tests break at scale, so consumer‑driven contract testing claims concrete wins: Pact records consumer unit tests into JSON contracts, a Pact Broker tracks version compatibility, and a Rust plugin framework now supports grpc plugin and ProtoBufs so provider verification can record-and-replay real interactions. Examples include a Global Payments bug caused by a ProtoBuf default and an implemented Pact integration that narrows types and reduces brittle E2E pipelines via Pact broker.
AI-written summary · about
chapters (12)
- 0:00Start
- 8:30Industry insights
- 10:43End-to-end tests
- 12:18Scaling Challenges
- 13:58What is Contract Testing?
- 25:23What about versioning?
- 26:07Protobufs (+ Avro and Thrift)
- 31:48GraphQL
- 33:57Your Provider Contract
- 36:40Pact
- 38:18Demo
- 40:40Summary
related talks
42mInvestigating Contract Testing
43mEnhancing Backend Microservices Ecosystem with Contract Testing
16mMicroservice Matchmaking: Pact Testing Between Spring Boot and gRPC
09m"Contract Testing 101"
39mPacts to the Rescue! Making your microservices play nicely together
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
59mUsing Pact to Deploy Microservice with Confidence
32mConsumer-Driven Contract: A better approach for API Testing