API Gateways back in the days were primarily being adopted at the edge for external traffic, but they are increasingly being used internally to connect teams/pr

API Gateways back in the days were primarily being adopted at the edge for external traffic, but they are increasingly being used internally to connect teams/products together, or in a Service Mesh deployment pattern for microservices. Solutions provided by cloud vendors are generally not well suited for all the N-S and E-W use-cases that typically an organization requires, they are usually slow (which in turn prevents more decoupled and traffic intensive architectures from working well), provide little extensibility options and while are every cheap to get up and running with, they also get expensive very quickly as traffic increases exponentially. Disclaimer: I am CTO of Kong [1]. [1] https://konghq.com https://konghq.com