Kong is an open source API management software that will help you create new business scopes, new revenue streams and generate traffic by expanding partner network. If you run an enormous number of APIs and need dedicated 24/7 support, then this software is apt for you.The software is embedded in Nginx and it provides a powerful proxying performance.The tool has boosted the API gateway with necessary functionalities for multiple uses.The software plugin system is open and it is possible to write your own custom plugins.Its high customization feature will give you complete control over the architecture.It is easy to scale and offers high integration.
|Support||Business Hours Online||Customer Type||Large Enterprises Medium Business Small Business|
|API||Contact||San Francisco, CA - 94108|
|Deployment||SaaS/Web/Cloud Installed - Mac||Category||API Management Software|
The blazingly fast open source microservice API gateway
The microservice API platform for large organizations.
Contact the vendor to get the latest pricing detail.
Disclaimer: The pricing details were last updated on 04/06/2018 from the vendor website and may be different from actual. Please confirm with the vendor website before purchasing.
Pros: Kong is a scalable and open source API Layer. It runs in front of any Restful Web services. Kong is designed to make secure, reliable and modular communicate between client and micro-services. Kong works as reverse proxy of micro-services that provides Authentication, Security, traffic control, Analytics & Monitoring and Transformations of request and responses. Kong has a great technical support team that replies very quickly.
Cons: There is nothing i dislike about Kong but I think user interface to define API gateway should be there.
I love the versatility of Kong. It pretty much will run on any platform and the price point from my understanding isn't that much as well. Great for all types of businesses.
It is good for small APIs but the moment I tried to connect to a big one, it immediately started blocking.
It manages multiple APIs at a very efficient way. I like the userface.
Easy to use interface with tools to help manage all inventory.
Some errors and kinks need to be worked out.
Tracking is easy but can be tricky
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.
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.
serverless will be easier to hire developers for if you are looking for long-term implementations.
I found Kong looking for active products implementing Openresty. I assume 90% of kong's customers also do the same.
It’s very easily and readily accessible and can access it
The interface still can be quite daunting for a novice user
I’m solving data visualization tools
API management, with REST interface. Plugin oriented architecture means it is easily extensible. Huge support from open source community.
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.
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
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.
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
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
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.
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.
The documentation is well-organized. Getting things running in Docker as a test was very easy. It has many potentially useful features.
I understand Mashape had Cassandra running already, but it's a ridiculous requirement for a configuration store.
We switched to Nginx.
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.
i can easily add an extra layer of permissions and even more on top of my API
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.
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.
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.
We were looking for an API Gateway solution which provided:
- Flexibility (we have more than two sources of users)