We use this solution as a way to expose our internal APIs, both internally in Kubernetes and for private cloud of our own.
External reviews
278 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Kong API Gateway: Love it or leave it
What do you like best about the product?
Extendibility, deployment flexibility and scalability
What do you dislike about the product?
1. Plugin limitations
2. Observability challanges
2. Observability challanges
What problems is the product solving and how is that benefiting you?
It solving api gateway, traffic management, Cross cutting problem like authentication, rate limit etc. , monitoring and tracing
A lightweight, fast and scalable platform for APIs hosting
What do you like best about the product?
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.
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.
What do you dislike about the product?
Out-of-the-box monitoring and observability support for which you need to buy their additional products.
What problems is the product solving and how is that benefiting you?
We didn't have any API management platform and gateway. We started exploring options of which Kong community edition api gateway turned out to the most suitable candidate because it was light-weight, modular, fast and most importantly inherently scalable. We eventually ended up procuring the enterprise version of Kong. We primarily use Kong as a facade layer on top of our APIs that are consumed by multiple internal applications as well as by some third-party systems on a limited scale. it serves as a unified gateway for policing and monitoring all the API calls. It helps us authenticate and authorize API clients, enforce custom policies and functions via the modular plugins feature. One of the stand-out features is its intuitive interface that does not require steep learning-curve.
Seamless integration and efficient security boost API management capabilities
What is our primary use case?
What is most valuable?
The most valuable features of Kong Gateway Enterprise are its seamless integration with Kubernetes and cloud, many plugins that can be incorporated in a solution, and its incorporation with low-code function systems.Kong provides the ability to relatively fast change our development and DevOps scaling from on-premise API and managed APIs to a very good and scalable solution, which provides the ability to monitor and react to the API, making it more valuable and providing more benefits for customers.
What needs improvement?
More plugins for additional integrations would be helpful and openness for traditional development languages, such as .NET, because many enterprises are looking for .NET solutions or incorporating with .NET solutions. I mostly missed local resellers or partners that we could use within our enterprise, because it was difficult for some tech personnel to work with remote tech support.
For how long have I used the solution?
I am just a customer of Kong Gateway Enterprise from my former work.
What do I think about the stability of the solution?
The stability would be rated about eight, as it is mostly stable.
What do I think about the scalability of the solution?
The scalability of this solution would be rated about eight or nine, and it would benefit if there was a little less latency.
How are customer service and support?
The technical support from Kong Gateway Enterprise would be rated about eight, as we missed local technical support.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before using Kong Gateway Enterprise, I used Azure API management.We switched from Azure to Kong Gateway Enterprise because we needed a solution to make API management on-premise and on cloud, and we did not want to work with Azure Arc, so we tried to find a solution that is possible to work with on both platforms, such as hybrid platforms.
How was the initial setup?
The initial setup of this solution was pretty straightforward, as we started to work with Docker, Docker containers, and Kong Gateway Enterprise as a managed platform with Kong Connect; we quickly realized how to work with it and how to deploy it and work with GitOps.
What about the implementation team?
Our deployment was done in-house, as it is a private enterprise and closed.
What other advice do I have?
I did not work with the AI capabilities of this solution, so I cannot measure it.Based on my experience, I would definitely recommend Kong Gateway Enterprise to other people.I would rate the whole solution about nine.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Kong Gateway:fast and flexible
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Kong Gateway addresses many crucial problems in our API management. One of the major challenges that we face is efficiently routing and managing API traffic across multiple services. Kong gives us a centralized medium to manage, source, and monitor API calls with ease. Secondly, Kong also ensures consistent security by providing a built-in plugin. This safeguards us from unauthorized access and potential attacks.
Good gateway
What do you like best about the product?
Reliable, feature rich gateway that enable shared responsibility
What do you dislike about the product?
Nil, pretty much do all that we asked it to
What problems is the product solving and how is that benefiting you?
Solving shared responsibility between developer
I tried kong just for testing
What do you like best about the product?
I would say that is very easy to use with a good documentation
What do you dislike about the product?
UI is functional but can feel limited and unintuitive compared to competitors like Apigee or AWS API Gateway. Improving the UX for configuring routes, plugins, and analytics would enhance usability
What problems is the product solving and how is that benefiting you?
Some problem with the installation
It's a great API gateway management product
What do you like best about the product?
Easy to configure, manage, and use. It saved our development time.
What do you dislike about the product?
No so far. Sometimes it lacks flexibility to implement all the features we need.
What problems is the product solving and how is that benefiting you?
It speeds up the development and management time of API gateway
fine product
What do you like best about the product?
good security, scalability, performance, centralized management
What do you dislike about the product?
typical modern subscription-based licensing
What problems is the product solving and how is that benefiting you?
I'm only evaluating for customer infrastructure.
Easy to use and friendly interface
What do you like best about the product?
Most of API Gateway is kind of difficult to use, but this product is straight forward and easy to use.
What do you dislike about the product?
So far, I haven't found any dislike of this product
What problems is the product solving and how is that benefiting you?
Usual API interface issue but it solved all of issues
high performance and simple to use
What do you like best about the product?
Mostly configuring the Internal services and sometime exposing it to public
What do you dislike about the product?
Sometime upgrade , would cause issues with config
What problems is the product solving and how is that benefiting you?
Routing , Proxy and authentication & Authorization
showing 1 - 10