Nonviolent communication in the world of distributed systems
summary
Explains how Pact consumer-driven contract testing ensures API compatibility by generating a shared JSON contract from consumer tests, publishing it to a Pact Broker, and having providers run automated verification. Demonstrates a workflow where a consumer test creates the contract, the broker stores it, the provider pulls and runs the generated tests, and CI enforces a deploy safety check that blocks versions breaking any consumer contracts.
AI-written summary · about
chapters (8)
- 0:00Nonviolent communication intro
- 3:16Microservice communication
- 6:33Integration testing problems
- 17:22Contract tests solution
- 27:34Contract tests in large projects
- 30:55Live Pact demo
- 40:38Contract testing benefits
- 42:04Q&A
related talks
42mNonviolent Communication in the world of distributed systems
19mBridging the Verifiability Gap: Why We Need More From Our Specs and How We Get It
38mThe Verification of a Distributed System
37mRethinking How We Test Our Async Architecture
30mThe Architecture of Microservice Transaction Based on Distributed Consensus with Kubernetes
41mSurviving Continuous Deployment in Distributed Systems
22mGovernance of event-driven distributed systems
01h 02mCommunication Patterns for Distributed Architectures