The API of a microservice is the gateway to the business that the microservice must perform. If there is any kind of problem with the microservice API, business is compromised.
Usually, API problems are generated due to the necessary changes in the signature of a microservice not being properly informed. The first approach to avoid this kind of problem is to use a mechanism where there is a common file between the application that serves the data and the application that consumes the data. In our microservices, the gRPC fulfils this function.
Another way to achieve successful integrations of a microservice's APIs is by adopting API versioning. Let's revisit our nginx.conf file. Note that the location settings are inconsistent and have no version indication:
...
server {
listen 80;
location / {
...
}
location...
