This document discusses consumer driven contracts (CDC), which define the interactions between a consumer (e.g. frontend) and provider (e.g. backend service). A contract specifies a set of interactions that the provider must support. The consumer tests its interactions with the provider to create a contract, which is stored in a pact broker. The provider then tests that its implementation matches the contract to ensure any changes do not break the consumer. Using CDC allows both consumer and provider teams to develop with confidence that APIs will not break unintentionally.

1. Consumer Driven Contracts
Jasiek Matusz

2. what the hell is cdc
● what endpoints can I use?
● what input do the endpoints take?
● what does the output look like?

3. important terms
➔Provider
➔Consumer
➔Interaction
➔Contract

4. Consumer, provider… what do you mean, dude?
Consumer is a CLIENT (example: frontend)
Provider is a SERVICE (example: web app backend)

5. So what are interactions?

6. What are contracts?
Contract is a set of interactions between a Consumer and a Provider.

7. So what are interactions?

8. Consumer test contains interactions, which define contract

9. Contract file

10. Pact broker

11. Pact broker

12. Provider testing and CI pipelines

13. Provider testing and CI pipelines

14. Development process

15. ● Helps Providers make changes without being
scared of accidentally breaking their Consumers;
● Lets Consumers know that the APIs they consume
won’t suddenly break
● allows Consumers to develop against API
definitions before the Provider API has actually
been developed;
● Makes integrating and testing a service in a
microservice landscape easier; and
● Serves as an efficient communication tool between
Provider and Consumer teams

16. Contract testing lets everyone
relax and be assured that the
APIs won’t break up and die.
medium.com/@alex.pruss

17. Thank you!