Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
API Gateway for Lua Developers
What do you like best about the product?
Kong is wonderful if you enjoy Lua with Openresty and look to have an sll-in-one solution for API implementation and management. Lua is not as popular as it should be, but Openresty has proven performance and a strong community. For developers using either (likely both) technology, Kong is exciting and fun to implement.
Documentation is also spectacular. Many of the tools within their ecosystem is open source, and usage is free for smaller use cases. They are one of the biggest sponsors of Openresty, so the developer community is pretty active as well.
Documentation is also spectacular. Many of the tools within their ecosystem is open source, and usage is free for smaller use cases. They are one of the biggest sponsors of Openresty, so the developer community is pretty active as well.
What do you dislike about the product?
While Kong is great for implementation of API's, a more manual implementation using serverless is usually the path most devs go for. Kong's use case is a bit too specific to bring over most modern microservice devs to the table. This really limits Kong to just large enterprise contracts which likely do not have as large of a consumer base due to the usage of Lua.
What problems is the product solving and how is that benefiting you?
I found Kong looking for active products implementing Openresty. I assume 90% of kong's customers also do the same.
Recommendations to others considering the product:
serverless will be easier to hire developers for if you are looking for long-term implementations.
- Leave a Comment |
- Mark review as helpful
A tool for the future
What do you like best about the product?
It’s very easily and readily accessible and can access it
What do you dislike about the product?
The interface still can be quite daunting for a novice user
What problems is the product solving and how is that benefiting you?
I’m solving data visualization tools
Best API Management Solution
What do you like best about the product?
API management, with REST interface. Plugin oriented architecture means it is easily extensible. Huge support from open source community.
What do you dislike about the product?
Have not encountered any problems yet with offering. If anything Kong is updated at very fast pace and that requires constantly trying to keep up with new release, If Kong Nodes are properly setup on docker containers behind Load Balancer like F5 then it becomes easy task.
What problems is the product solving and how is that benefiting you?
API Management. Logging, Analytics, Monitoring and Alerts. Supports several Authentication protocols. Plugin architecture means easily extensible and several options for any tasks for example for logging, you can use loggly/Galileo/Httpd(Elastic search)/Statsd(Graphite-Grafana)/Syslog etc. Huge support from open source community.
Recommendations to others considering the product:
Absolutely the best solution out there. Tried several other offerings like Tyk, WSO, IBM, SAP API Management, API umbrella, AWS, Fusio, Apigee, ApiAxle etc before picking Kong
Kong - API Gateway
What do you like best about the product?
1. Plugin based Architecture help to extend faster
2. Build on top of Nginx prove it to be satble in production
3. Lua Scripting Language make it easy to understand write code for Kong
4. Quick support community on Slack
2. Build on top of Nginx prove it to be satble in production
3. Lua Scripting Language make it easy to understand write code for Kong
4. Quick support community on Slack
What do you dislike about the product?
1. Lack of a Official UI or Administration Panel
2. Lack of built-in analytics at small scale
3. Lack of policies structure to be applied to multiple consumers
4. Non Cassandra DB support
2. Lack of built-in analytics at small scale
3. Lack of policies structure to be applied to multiple consumers
4. Non Cassandra DB support
What problems is the product solving and how is that benefiting you?
We needed to publish our REST APIs to our partners and later utilize same APIs to be consumed for our mobile products. So we need to implant an API gateway which helps us to stream line our APIs development to deployment process.
With kong we can avoid writing lot of similar code on each API, like rate limiting and logging.
With kong we can avoid writing lot of similar code on each API, like rate limiting and logging.
Recommendations to others considering the product:
Must consider evaluating its available UIs or admin interfaces before going live. Since in live environment, you can't actually go to your notes and look for curl commands.
It looks like it can be useful, but not necessarily for my use case.
What do you like best about the product?
The documentation is well-organized. Getting things running in Docker as a test was very easy. It has many potentially useful features.
What do you dislike about the product?
I understand Mashape had Cassandra running already, but it's a ridiculous requirement for a configuration store.
What problems is the product solving and how is that benefiting you?
We switched to Nginx.
Simple and Powerful
What do you like best about the product?
First of all it is easy to setup and start playing with. It is super important for microservices to have full control and it is easily deployable.
What do you dislike about the product?
actually there is nothing that i can not already implement with kong, i just wish it was easier to implement plugins based on more popular languages like python, ruby or even javascript.
What problems is the product solving and how is that benefiting you?
i can easily add an extra layer of permissions and even more on top of my API
Excellent OpenSource API Gateway
What do you like best about the product?
The project is very well documented. I like the fact that Mashape released the API as an Open Source product some other could benefit from it. It's also a very valuable addition to the API ecosystem.
What do you dislike about the product?
Kong lacks a User Interface which I think might speed up the process of getting familiar with Kong. It will makes sense far more intuitive.
What problems is the product solving and how is that benefiting you?
We were looking for an API Gateway solution which provided:
- Flexibility (we have more than two sources of users)
- Performance
- Flexibility (we have more than two sources of users)
- Performance
Recommendations to others considering the product:
You should consider evaluating other API Gateway solutions (like Tyk) before moving ahead with Kong. Also keep in mind that should you ever need to develop a plugin of your own, it needs to be implemented in LUA.
Api Abstraction to the best
What do you like best about the product?
No worries about implementation, Takes very little time to setup and get things running. I was using way2sms api to send sms for my project work. I used their python library which was great
What do you dislike about the product?
I was a bit doubtful about the auth system. which involved sending the sms text, and login credentials as url parameter in the GET request.
What problems is the product solving and how is that benefiting you?
I was trying to implement phone verification using sms
Recommendations to others considering the product:
I used a very small portion of serrvice that kong provides and i was pretty happy :)
Evaluated Kong for API management for microservices
What do you like best about the product?
Open source nature.
Plugin approach and available built in plugins that cover the most of the basic necessities.
Great community support. Questng are being answered.
Easily extensible using more plugins.
Plugin approach and available built in plugins that cover the most of the basic necessities.
Great community support. Questng are being answered.
Easily extensible using more plugins.
What do you dislike about the product?
Need Better built-in metrics plugin.
Can use only Cassandra as backend.
No built-in UI for non-programmers to access admin UI - For onboarding clients, APIs etc.
Can use only Cassandra as backend.
No built-in UI for non-programmers to access admin UI - For onboarding clients, APIs etc.
What problems is the product solving and how is that benefiting you?
Implement security, throttling etc for our Microservices suite.
Realized benefits in terms of onboarding initial set of clients with MVP feature set.
Realized benefits in terms of onboarding initial set of clients with MVP feature set.
Recommendations to others considering the product:
Design your micoroservices framework with Kong in mind right from the beginning.
showing 171 - 179