java – Spring Cloud Contract – is it Consumer Driven?

java – Spring Cloud Contract – is it Consumer Driven?

Thanks for this question. Yes, Spring Cloud Contract can be consumer-driven or producer driven.

The contract definitions can lay either with the producer or in an external repository. The concept of consumer-driven is not related to the fact where the contract are stored. Its related to the fact who creates them or actually who drives the change of those contracts. Another thing is whether each consumer can define a set of their own requirements. That means that one consumer can have different requirements than another one.

So in Spring Cloud Contract for the producer-driven approach, the producer just creates the contracts and it doesnt really care if different consumers use their API in a different way. The producer of the API creates e.g. 1 contract definition for all the consumers and its the consumers problem to align to that contract.

With consumer-driven contracts with Spring Cloud Contract, its the consumer that suggests the changes and creates the contract definitions. The consumer sends a PR either to the producer teams repo or to a separate repo where all the contract definitions are stored. Its not the producer, but the consumer who does it. The consumer can, in the meantime, create the stubs locally without asking the producer for the permission, and prototype the API. Once the consumer has finished its work and of course talked with the producer team about the changes before, then a pull request can be sent with the suggested changes. Important thing to remember is that each consumer has their own folder with their requirements. E.g. if there are consumers example1 and example2 and theres a producer producer1 then under producer1s contract folder there will be 2 folders, one example1 and the second example2. Both will contain expectations for the particular consumer.

Then the producer takes the PR over and the verification happens on the producer side. The tests are generated. Once the implementation is written and tests are passing the stubs can be uploaded.

Finally, on the consumer side, the consumers can switch to start fetching the uploaded stubs to always get the fresh version of the stubs.

All the workflows related to doing contract tests with Spring Cloud Contract can be found here –

java – Spring Cloud Contract – is it Consumer Driven?

Leave a Reply

Your email address will not be published. Required fields are marked *