I dont agree on "Nr. 3 Less Network calls" .
I don't see an api-gateway as equal as a "backend-for-frontend". I would route each request to the designated service behind the gateway. The reason is that I would not implement the complexity of the aggregation logic for all my microservice calls inside the gateway.
What he says it's that if the workflow is held by the client, it has to make multiple network calls. However, if it is held by a server component, the client needs to ask what it wants and nothing else (one network call).
I dont agree on "Nr. 3 Less Network calls" .
I don't see an api-gateway as equal as a "backend-for-frontend". I would route each request to the designated service behind the gateway. The reason is that I would not implement the complexity of the aggregation logic for all my microservice calls inside the gateway.
What he says it's that if the workflow is held by the client, it has to make multiple network calls. However, if it is held by a server component, the client needs to ask what it wants and nothing else (one network call).
Hi
I think that api composition pattern can be used at this case.
Thanks