API gateway locate between the client apps and the

internal microservices.

▪ Working as a reverse proxy and routing requests from

clients to backend services and provide cross-cutting

concerns like authentication, SSL termination, and cache.

▪ Several client applications connect to single API Gateway

possible to single-point-of-failure risk.

▪ If these client applications increase, or adding more logic to

business complexity in API Gateway, it would be antipattern.

▪ Best practices is splitting the API Gateway in multiple

services or multiple smaller API Gateways: BFF-Backendfor-Frontend Pattern.

▪ Should segregated based on business boundaries of the

client applications.

https://medium.com/design-microservices-architecture-with-patterns/api-gateway-pattern-8ed0ddfce9df