Following are few use cases where this pattern will be a right fit:

• Multi datacenter deployment: When your Microservices are deployed across multiple datacenters, API gateway acts as a façade for managing, packaging and consuming Microservices without being aware of the actual deployment location.
• Developer focused: With capabilities around packaging, maintaining catalogues and documenting Microservices, API gateway becomes single source of truth for developers to build applications using Microservices.
• Analytics driven business: A centralized channel for consuming APIs helps build better analytics which then can be used to build insights to identify trends which may impact the business.
• Secure systems: API gateway acts like a gatekeeper preventing consumers from directly accessing the Microservices. Responsibilities like authentication, authorization and throttling are owned by the API gateway there by providing a centralized control over all the Microservices running within an enterprise.