266 Kong Gateway Reviews
We use Kong Gateway for its flexibility and ease of integration. One of the best features of Kong Gateway is that it is a powerful plugin architecture that allows us to easily add different features like security, logging, etc. Also, the ease of scaling is another feature I like. It can be installed across multiple nodes and clusters. Its performance under heavy traffic is authentic. Review collected by and hosted on G2.com.
Not many points to dislike, but one of the challenges we face is that the new users sometimes may feel overwhelmed by the complex configurations and wide range of plugins that are provided. Review collected by and hosted on G2.com.
It has its roots in open source software
Its built on top of nginX - a world-renown reverse proxy
Its lightweight and expandable architecture - use only the modules (plugins) that you require
Its modular design is easy to understand and intuitive - learning curve is small. Review collected by and hosted on G2.com.
Out-of-the-box monitoring and observability support for which you need to buy their additional products. Review collected by and hosted on G2.com.
Kong API Gateway makes life easier will all the existing capabilities that it provides through its user interface for Configuring Services, routes along with handling SSH requirements through Kong itself. It also helps in having a constant access to client servers that are on SSH but needs to be accessed while developing solutions to integrate with the apis where the ips are not static. This is one case that we use kong regularly for. I like the Request Transformation and Response Transformation feature of Kong the most. Its real pain doing that with other API Gateway solutions. If we go with native way of handling Request or Response transformations with Spring Cloud API Gateway etc.. we end with many issues that takes hell a lot of time to fix but with Kong it doesn't need to be deployed every time and with a save everything gets updated and fixing it is also gets easier and requires less effort. Also the logs of kong are also pretty much descriptive about the errors that we face in the Request routing failures, request tracking, identify the reason for failures etc.. Review collected by and hosted on G2.com.
Currently I dont have any dislikes regarding Kong API Gateway and I have worked with Community and Enterprise versions and never found any issues using it. It makes our life simple. I have recommended it at many places wherever there was a need to introduce API Gateway solution. Review collected by and hosted on G2.com.
Kong is a one-stop solution for managing your microservice in the container world. Right from kong mesh to seamless experience with API management reduces the API development burden to market the product quickly as never before. It saves my organization from paying bills of many IPs addresses and make it easy implement for inbound traffic. Review collected by and hosted on G2.com.
Multi-tenancy of the kong control plane (IngressClass) needs to be documented. Kong API integration with ISTIO is a bit harder Review collected by and hosted on G2.com.
What I like most about Kong Gateway is its ability to scale and manage APIs efficiently. Its plugin-based architecture allows for great flexibility and customization. Additionally, it offers easy integrations with existing systems and has an active community that facilitates the resolution of questions. Review collected by and hosted on G2.com.
The least useful aspect is that the learning curve can be somewhat steep for new users. The documentation, although extensive, could be clearer in some technical sections. Review collected by and hosted on G2.com.
Coming from a security engineer we can add custom logic in the form of kong gateway plugin. it's extensible to a decent scale Review collected by and hosted on G2.com.
i found it difficult to implement on a personal research level. Review collected by and hosted on G2.com.
All most everything. Like plugins and all Review collected by and hosted on G2.com.
here comes the main thing come on to that what i dont like is that -
1. Lack of Client credential storage operation which we get in apigee and IBM connect.
2. Way worse developer portal in comparison of the other developer portals.
3. Frequent issues in syncing of Dataplane is a big concern.
4. the document should be more detailed and on point. Review collected by and hosted on G2.com.
obviously there are things that are likeable like -
1.the automation process of the deployment of entities and developer portal is great in kong konnect due to the Admin/Management API.
2.Its way easier to use in comparison of IBM connect , akana and Apigee.
3. It justifies its cost to the consumers as it is not the expensive to subscribe for.
4. The plugin stack of kong is great and still in progress of adding more plugins like with the implementation of AI.
5. The low latency for the API request is a great plus too. Review collected by and hosted on G2.com.
here comes the thing which are not talk about much about kong-
1. kong is yet to understand the requirements of the clients let alone the thought of implementing it, because it takes too much time (months)to solve a simple bug .
2. Delay in deliviring products like kong mesh and Api hub is a big negative for me.
3. they should tie with more CRM's to provide a better experience. Review collected by and hosted on G2.com.
Upsides:
Simplified API management (different country clusters)
Robust security features (Introspection Plugin)
Scalability and performance of DB-less mode Review collected by and hosted on G2.com.
Downsides:
Steep learning curve for decalrative configuration as well as plugin usages
Limited documentation in some areas especially releated to plugins
Occasional stability issues with updates (version upgrade) Review collected by and hosted on G2.com.
