0
Hello,
I’m developing a gateway API on a micro service architecture in a Kubernetes environment. The idea is to have not only a routing Gateway but also an aggregator that aggregates response from various micro services to return to the angular front-end.
I will have to develop the aggregator internally, I wonder if it is good practice to join the Gateway and the aggregator in the same solution? It saved network latency, minus one step for the response to reach the customer, but at the same time the level of scalability goes because I can’t scale just one component or another. And for the gateway there are already efficient proxies and being in a Kuberentes environment, I think I could even use the ticket for this work.
Thank you!
It’s an opinion-based response, but they’re different components, so I think of different applications. From another point of view still, putting everything together already leaves a bit of the concept of "microservice"
– Ricardo Pontual
@Ricardopunctual Thanks for the answer. Do you think it makes sense to develop a gateway api internally? Since it only does proxy Reverse, there are already very efficient solutions to the case. Recommend some ?
– alves
Out of curiosity, what is the need to join the answers in one?
– Woss
@Woss to reply to the frontend. For example, a shopping cart, need to analyze the stock, the catalog, the price, invoice, etc... Probably this transaction involves several micro services and so the frontend does not have to make several calls to the frontend wanted to return already a JSON with all the information q the frontend needs with a single call.
– alves