spring-microservice-sample | Spring Boot based Mircoservice sample | Continuous Deployment library

The above MockRestServiceServer or WireMock is widely used when the existing external service is out of control, eg. it is from the 3rd party company or organization. In our application, the auth service and user service are developed by ourselves, but may be produced by two different teams. Assume when the auth service requires to embed the result of a /users endpoints that should be provided by user service, but at that moment such an AP does not exist in the user service at all. To resolve the problem, the best way is the developers from two sides sit down at a table and sign a contract about the communication details between these two services. Firstly the auth service developer lists all required HTTP endpoints that should be provided by the user service. For example. The user service developer reviews the requirements, and confirm the items one by one, and make sure they are on the same page. Then they are back to work and focus on their own development. When the development(both side) is done, they can use a real world environment to verify if they have complied with the rules defined in the contracts they have signed. In the software development world, this kind of scene is called Consumer Driven Contracts. In the CDC world, the auth service is called the API consumer, and the user service is the API producer/provider. In these years, CDC/Contracts testing becomes more and more popular. Obviously, an advantage of applying this pattern is the consumer side can start work immediately when the contract is signed and do not need to wait for the complete work from the producer side. There are a few projects available to improve the CDC development process. Spring Cloud Contracts Workshop provides the best practice when introducing Spring Cloud Contracts into your Microservices project.