Kong Gateway Enterprise Reviews

I use it as a gateway for our APIs. We have several hundred APIs here, so we use Kong Gateway Enterprise to manage and monitor them. In this application platform, we prefer to use the Kong Enterprise UI instead of the Kong Community Edition GUI.

We use both authorization and header-based methods. Additionally, we connect with our identity provider (IdP) using single sign-on (SSO) and OAuth 2.0. We also enable OpenID Connect.

The traffic control capabilities in Kong Gateway are effective. It helps me manage the usage of each API and monitor any anomalies. I can see any strange behavior or illegal usage from developers, which allows me to notify management about potential issues. Sometimes, it might just be a typo or a bug in the application, but other times, it could be something more serious. The Kong Gateway's traffic control helps detect these anomalies in usage.

We use this solution as a way to expose our internal APIs, both internally in Kubernetes and for private cloud of our own.

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.

I lead the integration practices in my organization and have been working in integration for the past 16 years, managing API integrations with various API manager tools such as Kong Enterprise.

We are primarily using Kong for the API gateway functionality. For example, we've had a couple of mobile applications with outbound traffic where we would use the Kong Enterprise gateway to expose the API by applying authorization, authentication, and other security policies.

We have also used Kong for role-based access control mechanism (RBAC) and integrated it with our enterprise directory in order provide it with this form of access control.

There was another particular use case in which we performed some customization, as well. In that scenario, we wrote a Lua script on top of Kong to add an AppDynamics plugin to our web server, for observability and monitoring purposes. 

Kong has been used over a large user base, not only because it's an enterprise application, but also because the mobile applications we worked with were B2C-based in the retail industry, so the number of users was quite high.

There are a few features that I like about Kong when it comes to authentication and authorization. Specifically, being able to use Kong for role-based access control (RBAC), and then further being able to integrate the RBAC mechanism with our enterprise directory, was very useful.

Another nice aspect of Kong Enterprise is the ability to customize it with Lua script, such as when we developed a way to provide observability for our web server with AppDynamics. 

Within Kong Gateway Enterprise, we utilize Kong Ingress and the Com API Gateway. It offers a wide range of plugins that we leverage, including OIDC, Rate Limiting, Lambda functions, and more. We also configure multiple deployments and utilize plugins like the OIDC Registration plugin for authentication and authorization. Additionally, we ensure schema validation for incoming requests and utilize security scanning. Kong Gateway provides a Request Transformer plugin that allows us to add or remove header values as needed.

The product seems to be good, especially in terms of API creation and management. The tool is seamlessly easy to use, and offers ease of configuration and management. The tool has some very good options for infusing some API security parts. The tool also offers some readily available connectors as well. From an overall perspective, I am handling both B2B integrations and cloud integrations. In our company, we had multiple products in place of Kong Gateway Enterprise.

Kong Gateway Enterprise enhances our company's API security in a strong way, and it is compliant with most of the security compliance issues, which is good from an assurance standpoint and acts as a strong point when it comes to the product. In terms of ease of configuration and maintenance of the APIs, the tool offers a very good dashboard, specifically API dashboards, which can provide you insights into how you can use the dashboard for monetizing your solution. For example, for some of the APIs that accompany the product and become a part of the ecosystem, be it for opening new services with different partners, the tool is able to provide good insights in terms of integration touchpoints, which not only caters to the internal ecosystem but also into a partner ecosystem, giving an agnostic view. Depending on the exact need of the hour and based on the requirements, Kong Gateway Enterprise is useful in terms of integration, ease of use, and dashboard.

Though I have not tested the tool, I can say that the product supports AI-driven applications. Nowadays, in most language models, especially when we talk about the edge deployment model, any of the platforms provide you with seamless integration, which is advantageous because most of the applications are consumed by end users. It also boils down to the fact associated with the latencies. For some of the services and requirements, it doesn't always have to be some public cloud infrastructure that one needs to experience. I believe that I will be better off with edge deployment, where things can be run on a nearby location where the customer proximity is there. A combination of AI and edge deployment will be an advantage.

We use Kong for our API gateway, handling all public traffic. It is an open-source tool, and even though we are a startup, it provides us with stability without incurring high costs initially.

Kong has helped us by performing smoothly even when we receive millions of requests, which prevents any latency issues impacting our applications. We have also been able to enhance security by writing our own plugins and easily integrating with various tools and platforms.

My company gave Kong Enterprise to only one company in the manufacturing sector, and now we are in talks with another manufacturing company.

Kong Enterprise is very useful, especially for IoT applications. Palo Alto Networks is also good for IoT applications. Kong Enterprise has a great licensing model. I am scanning capabilities, making it a good tool for infrastructures.

In comparison to Fortinet, Kong Enterprise fails to offer a huge number of ports in lower models of the solution. From an improvement perspective, the number of ports in lower models of the solution should be made available.

The GUI of the product is not very user-friendly, making it in areas where improvements are required. In Fortinet, the GUI allows users to deal directly with the configuration part.

The product's price is an area of concern where improvements are required.

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.

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.