Stick to the rules! Consumer Driven Contracts as a TDD on architectural level TDD introduced many improvements into development process, but in our opinion the biggest impact relates to code design. Looking at the code from the usage perspective (by first writing an acceptance test) allows us to focus on usability rather than concrete implementation. Unfortunately usually we rest on laurels not trying to uplift this practice into architecture level.
Consumer driven contracts are like TDD applied to API. It’s especially important in the world of RESTful endpoints and microservices. Since it’s driven by consumers it’s much more user friendly. Of course microservices are really cool, but most people do not take into consideration plenty of potential obstacles that should be tackled. Then instead of frequent, fully automated deploys via delivery pipeline, you might end up in an asylum due to frequent mental breakdowns caused by production disasters. In this talk we will try to show you how to write tests of your microservice's contracts so that your chances to go down on production due to sending improper requests get lowered substantially. We’ll present how to move TDD to the architecture level and design the API from the consumer’s point of view.