Signature tests

Imagine a scenario where we have several development teams working on different microservices of the same application. These microservices have some communication between them; there is a kind of contract between them that is the payload of the microservice, also known as the Service Signature. One of the development teams modifies the signature of the microservice causing errors in other parts of the application.

As previously stated, modifying microservices is common, especially if they are part of the internal layer. When a microservice has the signature changed, a task must be generated for the other development teams responsible for microservices that integrate with this signature.

The problem is not the change, but the ...

Get Microservice Patterns and Best Practices now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.