What is Amazon API Gateway?
What is Apigility?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using Amazon API Gateway?
What are the cons of using Apigility?
I use Kong because it reliably proxies traffic quickly with an assortment of pluggable features. The engineers behind the product are of the highest quality. The Company has cultivated the largest active open source community of any API gateway. They generally squash bugs in hours or days not weeks/months. Company engineers help community members through social avenues as well as supporting large enterprise. They heavily value their product and individuals as opposed to just solely growing enterprise license fees.
We needed a lightweight and completely customizable #microservices #gateway to be able to generate #JWT and introspect #OAuth2 tokens as well. The #gateway was going to front all #APIs for our single page web app as well as externalized #APIs for our partners.Contenders
We looked at Tyk Cloud and Kong. Kong's plugins are all Lua based and its core is NGINX and OpenResty. Although it's open source, it's not the greatest platform to be able to customize. On top of that enterprise features are paid and expensive. Tyk is Go and the nomenclature used within Tyk like "sessions" was bizarre, and again enterprise features were paid.Decision
We ultimately decided to roll our own using ExpressJS into Express Gateway because the use case for using ExpressJS as an #API #gateway was tried and true, in fact - all the enterprise features that the other two charge for #OAuth2 introspection etc were freely available within ExpressJS middleware.Outcome
We opened source Express Gateway with a core set of plugins and the community started writing their own and could quickly do so by rolling lots of ExpressJS middleware into Express Gateway
Apigility is loyal to the standards; we do not need a framework to write custom REST APIs, anyone can do that; we need a framework that makes sticking with the standards easy.
Every PHP framework should be designed in such a way, that it forces you to think about what you are doing, the current PHP mind-set is too much crowded with lazy documentation of custom-solutions that do not work as expected (because the language gives you too much freedom).
With Apigility it is easy to build RESTful APIs in a declarative way, so that you do not need to write tests for every API Service you create, because the underlying code doesn't change or break, all functionality comes within the framework, that has already been tested.
You do not need to write any boiler plate code, which is huge plus compared to Symfony 2 and the likes.
Apigility has had some reliability problems with newest releases and as far as I know, they do not report which release is the latest stable. But of course, they reached the 1.0 in 2015.
We're a small startup in San Francisco (team of 18 people). After spending lots of time building our core technology, it was time to bring it to life and deploy with several very large customers (500+ API requests/customer/minute).
We looked for a solid API management solution that would allow for easy authentication, quick installation and great logging features (requests and responses). After looking at various (very) expensive solutions out there, we ran into Kong.
After testing it for a few days, we deployed quickly to production to serve the needs of our customers. 3 weeks in, our experience has been great. Highly recommended to anyone who's looking for API management solutions.
P.s. Scored "Reliability" as "OK" for now with lack of data. Will definitely update once we've had Kong in production for a longer period of time.
API Gateway in conjunction with Lambda has allowed us to become 'serverless'. We have a number of API endpoints that range from simple CRUD operations, through to triggering chains of complex background jobs. Like Lambda, this service has released us from getting bogged down in infrastructure management, freeing up huge amounts of time to focus on solving business problems.
It provides me with POST endpoints; I don't run servers and some third-party services need to POST data to my application.
And if developper can also code the load balancer ? Add plugin, dynamically change backend, Kong give this versatility
Triggers the Lambda function from a GitHub WebHook push into
Excellent API Gateway, some quirks but most are being addressed over time, easy integration with Lambda