Kong enterprise has significantly enhanced our ability to manage and secure our Microservices. Its most valuable feature is monitoring.
External reviews
External reviews are not included in the AWS star rating for the product.
Kong API Gateway Enquête - Vivek Doddaguni
Expérience avec Kong API Gateway jusqu'à présent
L'API Kong et Ingress est quelque chose que j'utilise et en laquelle j'ai confiance chaque jour.
Rationalisation de la gestion des API avec Kong
2. Extensibilité avec des plugins
3. Facilité de déploiement et de gestion
4. Facilité de surveillance et d'analyse :
Passerelle API et maillage de services
service de passerelle API
Premium et fiable passerelle API open source
Has monitoring features but UX needs improvement
What is most valuable?
What needs improvement?
The tool needs improvement in UX.
For how long have I used the solution?
I have been using the product for six months.
What do I think about the stability of the solution?
I rate the solution's stability an eight out of ten.
What do I think about the scalability of the solution?
I rate the tool's scalability an eight out of ten. My company has five to seven users.
How are customer service and support?
I have encountered communication issues.
How would you rate customer service and support?
Neutral
How was the initial setup?
I rate the tool's deployment a ten out of ten, and it took a few hours to complete.
What's my experience with pricing, setup cost, and licensing?
Kong Enterprise's pricing is reasonable for our company size.
What other advice do I have?
I rate the overall solution an eight out of ten.
Which deployment model are you using for this solution?
Improves performance and comes with rate limiting features
What is our primary use case?
My company is a financial company involved in credit card processing. We use the solution for internal IT secure gateway.
What is most valuable?
The tool's feature that I find most beneficial is rate limiting. In our usage, especially in the financial sector, we prioritize limiting API usage. This is crucial because we provide APIs to other companies and must ensure they adhere to their allocated usage limits. Without rate limiting, there's a risk of excessive usage, which could result in significant costs.
The solution has improved our organization's performance.
What needs improvement?
Kong Enterprise needs to improve its pricing, which starts at hundreds of thousands of dollars. Pricing should be based on API usage rather than monthly. It should improve its documentation as well.
For how long have I used the solution?
I have been using the product for six months.
What do I think about the stability of the solution?
I rate the tool's stability a nine out of ten.
What do I think about the scalability of the solution?
The solution is horizontally scalable and very useful. My company has one customer for Kong Enterprise. I rate its scalability a ten out of ten.
How are customer service and support?
I haven't contacted technical support yet.
How was the initial setup?
The product is easy to deploy and gets completed in one hour.
What's my experience with pricing, setup cost, and licensing?
Kong Enterprise is cheaper than Apigee. I rate its pricing as four out of ten.
What other advice do I have?
Kong Enterprise can connect with other tools easily. It has features like APIs and logging that programmers can use to link it up with different systems. I haven't used its integration features much, but I know its possibilities. I rate the tool an eight out of ten.
Which deployment model are you using for this solution?
Robust API management solution offering scalability, resilience, cloud-agnostic deployment capabilities and powerful and adaptable gateway services
What is our primary use case?
It serves as an API gateway and microservices management platform, facilitating the creation, deployment, and oversight of APIs and microservices. It serves as a solution for measuring requests, managing upstreams, and handling internal APIs within the bank.
What is most valuable?
It is an excellent tool for managing data. It boasts remarkable speed and stability, and these qualities, particularly the gateway's resilience, are standout features for me. The shared features are also commendable. One of the aspects I appreciate is the effective rate limiting, achieved through the use of the throttling plugin for our APIs. Additionally, the straightforward automated deployment process for the gateway makes it exceptionally easy for everyone on the team to adapt without complications.
What needs improvement?
I find that expressing information can be a bit challenging, especially for those who are new to installing email configs or using it for the first time. Understanding the configurations and knowing what needs to be done can be a bit difficult initially.
For how long have I used the solution?
It is a crucial part of my daily workflow.
What do I think about the stability of the solution?
I encounter no issues with deployments, and it reliably performs its duties on a daily basis. It proves to be both resilient and stable.
What do I think about the scalability of the solution?
It's scalable to your needs, and if you have the financial resources, you can scale it as much as you want.
Which solution did I use previously and why did I switch?
Before adopting Kong, I utilized X-ray, which is another API gateway. I believe the strength of Kong lies in its agnostic nature. It allows deployment across various cloud environments, providing flexibility for implementation in any infrastructure. It is inherently cloud-native, enabling deployment and maintenance on platforms such as AWS, Azure, and Google Cloud. This sets it apart from other gateways that may not offer the same level of versatility.
How was the initial setup?
The initial setup is relatively easy, but it requires a clear idea of your objectives.
What about the implementation team?
When it comes to deployment, my team and I handle the entire process. We are responsible for managing all aspects of it. It is possible to deploy it within ten minutes in a cloud-native environment using our current CI process.
What other advice do I have?
My advice is to approach it with careful consideration. While it is a powerful tool, gaining expertise is crucial. It's essential to try it out firsthand, build confidence that Kong aligns with your requirements, and recognize its reliability as a gateway. In my experience, it has proven to be a top choice. If you encounter challenges, I recommend visiting the website and delving into the documentation, as it often holds solutions for various scenarios. Overall, I would rate it eight out of ten.
Passerelle API Cloud Native et DevOps
L'installation hybride via Kong Konnect est très rapide et puissante et vous permet d'externaliser toute la gestion sauf pour les plans de données qui sont installés sur site et gérés à distance. La version sur site est facile à installer. Elle peut être configurée à la fois via une interface web et par une configuration déclarative. En termes de support, la version Entreprise offre un support très rapide et efficace.
Elle prend en charge les outils CLI natifs pour lancer des tests et déployer des configurations dans vos pipelines CI/CD.
Pour la version Entreprise, le modèle de licence est un peu compliqué car il dépend du nombre d'invocations mais aussi du concept de service de passerelle, ce qui n'est pas toujours facile à maîtriser.