These are the advantages of using an API Gateway proxy in your distributed application:

• API Gateway provides an easier way for clients to call API services
• You can apply client-specific policies, such as authentication and rate-limiting, at a single place rather than across multiple services
• You can also expose selected APIs to the clients with exposing internal microservices endpoints
• Microservices endpoints can be changed without forcing the clients to refactor consuming logic
• You can implement any routing rules or any filter implementation
• API Gateway is like an Edge microservice and is independently scalable

You have seen some pros of using the API Gateway proxy service in your microservices architecture, and now let's look at some cons of using this API Gateway pattern.