Cons
It can cause performance degrade due to lots of happenings on the API Gateway.
With this, discovery service should be implemented.
Sometimes, it becomes the single point of failure.
Managing routing is an overhead of the pattern.
Adding additional network hope in the call.
If not scaled out properly, the API Gateway can become a bottleneck.
An API Gateway requires additional development cost and future maintenance if it
includes custom logic and data aggregation.
If the API Gateway is developed by a single team, there can be a development bottleneck. This aspect is another reason why a better approach is to have several fined-grained API Gateways that respond to different client needs.