Nonviolent Communication in the world of distributed systems
summary
Claim: contract testing gives fast, cheap assurance of microservice communication correctness and backward compatibility by sharing a single, versioned contract instead of relying on brittle integration or slow end-to-end suites. Demo uses the Pact/pack framework to generate a JSON contract and client stub, publish it to a Pact broker, run provider verification (initial build fails with 404, then API added and build passes), and run a can I deploy check in CI. Tests run locally, require contract discipline, and remove network flakiness.
AI-written summary · about
chapters (13)
- 0:00Introduction to talk
- 1:16Monoliths vs microservices
- 5:27Communication challenges in microservices
- 6:28Testing pyramid limitations
- 17:24What is contract testing
- 20:55Producers and consumers explained
- 23:43How contract testing ensures correctness
- 27:15Drawbacks of contract testing
- 28:59Consumer vs producer driven contracts
- 30:49Demo setup and expectations
- 33:58Generating and verifying contracts
- 35:24Testing the producer side
- 39:46Key takeaways and conclusion
related talks
45mNonviolent communication in the world of distributed systems
59mUsing Pact to Deploy Microservice with Confidence
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
09m"Contract Testing 101"
24mHow to test microservices and stay sane
23mContract Testing for Mobile Application Development
22mContract Testing – An efficient way for integration testing
42mInvestigating Contract Testing