The following considerations should be taken into account while implementing this pattern:

• Another layer: While introducing an API gateway, it is important to account for the increase in latency which may be caused in consuming the APIs. In most of the cases this is negligible and can be optimized by caching the API responses.
• Centralizing diagnostics: API gateway will have its own diagnostics components which logs information to a store which may be different from the one use by the hosted Microservices. It may be useful to consolidate these logs to improve operational efficiency.
• Abstraction leads to information filtering: Abstracting responsibilities will filter out information which may be relevant for the operation of a Microservice. A good example is user (consumer) context which may be of relevance to the Microservice will be filtered out by the API gateway as it is responsible for authentication/authorization.
• Access control: It is important that the API gateway supports role based access control as it needs to cater to different teams with different responsibilities.