Managing APIs and Contracts in a Microservices World Using Spring Cloud Contract
summary
Shows how Spring Cloud Contract uses Groovy DSL contracts stored in source control to produce generated stubs (WireMock) and on‑the‑fly generated tests for producers, exchanged via a Maven stub repository and a stub runner. Demo builds a login service: consumer tests run green with stubs, a password rule change updates the contract, server unit tests fail then pass after a small code fix, and integration failures drop dramatically when contracts drive both sides.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:55Day 2 Development
- 4:41Ideal
- 6:39Spring Framework
- 7:51Bugs and Errors
- 8:22What went wrong
- 8:54Why did it happen
- 10:57What is supposed to do
- 14:19Spring Cloud Contract
- 15:25Spring Cloud Contracts
- 16:10What is a contract
- 17:09Demo
- 18:01Contracts
- 22:42Running Unit Tests
- 23:02Building a New Contract
- 24:32Unit Testing
- 27:12Summary
related talks
01h 04mConsumer Driven Contracts and Your Microservice Architecture
47mCollaborative Contract Driven Development
49mCollaborative Contract Driven Development
45mREST and Messaging contracts with Spring Cloud Contract
33mPractical Contract Testing with Spring Cloud Contract
17mConsumer driven development with Spring cloud contract
50mFrom Contracts to Confidence: Spring Cloud Contract 5 in the Age of AI
44mBuild Resilient Systems with Spring Cloud Contract and Testcontainers
