Standards are essential for implementing a Microservice Architecture. In this article, I will focus on the types of requests and responses involved in this architecture. Typically, a request enters the system through an API gateway. Then the request goes thru an application orchestration layer which is responsible to apply rules/validations and forward that request to a specific microservice. This microservice processes the request and forwards to a second microservice. Subsequently, another request is created by a second microservice, and a third, fourth ... microservice joins the pipeline. Until a final response is created and follows the reverse path back to the orchestration layer and API gateway. This process can continue across several, sometimes hundreds, of microservices until a final response exits the system. To accurately correlate the various requests and responses, it is crucial that all requests and responses share a unique transaction ID. Additionally, identifying the originating client that made the initial request is important. Therefore, having a standard base request and response type across all microservices will help ensure consistent processing of these requests and responses throughout the system.
Rubens Gomes
No comments:
Post a Comment