My company uses Kong Enterprise for ISC, so if we need data in one place or one application, we use the solution to retrieve the data with the help of REST API.
External reviews
External reviews are not included in the AWS star rating for the product.
kong avec terraform
Support client
Très agréable d'engager les clients en déplacement
API Kong
Renforcement de la gestion des API avec Kong
Efficacité dans la gestion : Kong a simplifié nos processus de gestion des API, offrant une interface unifiée et conviviale. Cela a rationalisé nos tâches, économisant du temps et des ressources.
Mesures de sécurité renforcées : Les fonctionnalités de sécurité robustes fournies par Kong ont considérablement renforcé la sécurité de nos API, assurant l'intégrité des données et protégeant contre les menaces potentielles.
Scalabilité et performance : Les capacités de la passerelle en matière de contrôle du trafic et d'équilibrage de charge ont considérablement amélioré la performance de nos API, assurant la scalabilité pendant les périodes de forte demande.
Surveillance perspicace : Les outils de surveillance de Kong offrent des informations précieuses sur l'utilisation des API, nous aidant à prendre des décisions éclairées pour l'optimisation et les améliorations.
En résumé, la solution de Kong API Gateway a notablement optimisé notre gestion des API, assurant une infrastructure plus sécurisée, efficace et évolutive, bénéficiant en fin de compte à notre efficacité opérationnelle et à la sécurité des données.
The tool offers its users with great integration capabilities and a good overall stability
What is our primary use case?
What is most valuable?
The most valuable feature of the solution stems from the fact that it seamlessly supports a vast number of tools. The integration capabilities the tool offers are smooth, and I don't see any hiccups there.
What needs improvement?
There is a tool called Apigee. Apigee has a portal where you can inspect the APIs and do a live tracing of the API, features that are missing in Kong Enterprise and Azure API Management. I am unsure if something else needs to be considered for improvement. Kong Enterprise fails to provide live tracing of the APIs, which is possible nowadays. With live tracing of the APIs, you can see how the request is going and where it gets stuck, what the actual input was, what the response is, and all that information we can see with the help of live requests, which is impossible in Kong Enterprise. The aforementioned area can be considered for improvement in the solution. With Kong Enterprise, you can examine after the fact, but why it happens can't be examined.
For how long have I used the solution?
I have experience with Kong Enterprise. My company is a customer of the solution.
What do I think about the stability of the solution?
The solution has been stable so far in my company.
What do I think about the scalability of the solution?
I can't comment on the solution's stability since my company is still in its development phase.
How are customer service and support?
For support, a group was created with the help of Microsoft Teams. My company hasn't contacted the actual support team of Kong Enterprise.
Which solution did I use previously and why did I switch?
I have used Apigee in the past. You can do the live tracing of APIs in Apigee, but it is not possible in Kong Enterprise.
How was the initial setup?
The solution's deployment was done in a couple of weeks.
Our company has not gone live with the product since we are still in the solution's development phase.
The solution's deployment model has changed from an on-premises to a cloud one.
Which other solutions did I evaluate?
It was not my company but our company's service provider who gave us Kong Enterprise.
What other advice do I have?
Kong Enterprise is a good solution with a few missing features, especially the one provided by Apigee, which is the live tracing of APIs.
I rate the overall solution an eight out of ten.
The solution provides protocol transformation and allows each client to have a specific UI experience
What is our primary use case?
We had worked for a client from the travel industry who wanted to propose an API manager. They had built microservices on Java and another integration tool. They wanted to apply policies, register their APIs in the API manager, and enforce policies and plugins, like client ID, client secret, throttling, rate limiting, and protocol transformation. The client wanted to apply these things to their APIs.
What is most valuable?
Protocol transformation is the most valuable feature of Kong Enterprise.
Kong Enterprise allows a lot of customizations that provide a specific UI experience for each client.
What needs improvement?
The solution should include policy features that are available in other solutions like MuleSoft API manager but missing in Kong Enterprise.
For how long have I used the solution?
I have been using Kong Enterprise for the past six to eight months.
What do I think about the stability of the solution?
We have not seen any stability issues so far with Kong Enterprise. None of our customers have reported any issues with the solution.
What do I think about the scalability of the solution?
Kong Enterprise is a scalable solution.
How was the initial setup?
No setup is required for Kong Enterprise because it has a complete cloud setup. You pay for a license, get credentials, and start registering your API and applying policies. It's completely cloud-based. We also have some open-source options where you set up the API manager on your Kubernetes clusters or dockers and register your API in the on-prem Kong API manager.
What other advice do I have?
The solution requires maintenance, but I haven’t heard of any maintenance challenges so far.
A user's decision to choose Kong Enterprise or MuleSoft varies from use case to use case. Users should do a detailed technical assessment before choosing Kong Enterprise, MuleSoft API manager, or any other API manager tools available in the market.
Overall, I rate Kong Enterprise an eight out of ten.
Kong Passerelle API
Meilleur outil de passerelle API - L'équilibrage de charge et le proxy inverse fonctionnent assez bien et sont configurés.
Nous l'utilisons pour la passerelle API pour l'application de microservices.