Deploy microservices with Certainty
summary
A small demo service ecosystem runs on OpenShift (Kubernetes) with a Vert.x provider and a RestAssured-based consumer; a careless removal of the provider’s "wiki" field causes a 500 NullPointerException in production. Consumer-driven contract tests generated by Pact v3 use a local stub server to produce JSON contracts and a Pact Broker (or repo) to share them; provider-side verification replays interactions and fails the build when the response body no longer matches, preventing unsafe deployments.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:39Simple example
- 1:52example
- 3:38destroy production environment
- 7:53break production
- 8:23contract test
- 8:50who is responsible
- 9:48consumer test
- 14:04spring cloud
- 15:50Pact
- 17:42Consumer
- 21:24Web Client
- 24:02Nettie Server
- 25:05Source Code
- 28:10Conclusions
- 30:00Question
related talks
42mDeploy microservices with Certainty
59mUsing Pact to Deploy Microservice with Confidence
01h 02mAvoiding Common Pitfalls With Modern Microservices Testing
45mDeploy microservices confidently using Consumer Driven Contracts
24mHow to test microservices and stay sane
10mDeploy microservices confidently using Consumer Driven Contracts
39mPacts to the Rescue! Making your microservices play nicely together
01h 21mMicro-Service Delivery Without the Pitfalls
