3 ms·
Running these api gateways on your own is very complex, especially when they need to be open publicly. Typically you’d want to layer a WAF and a CDN on top of t
by sheeshkebab 8y ago
Running these api gateways on your own is very complex, especially when they need to be open publicly. Typically you’d want to layer a WAF and a CDN on top of them, which already come with their own api gateway like features (eg AWS cloudfront).
My question - what do people use these for?
- fosk 8y agoAPI 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
- Bombthecat 8y agoYeah, my current project is using an internal / external api gateway style. You run into so many issues... You kinda want to run away (beside performance) it is super hard to actually manage / govern etc..