Kong Gateway Enterprise

What do you like best about the product?

Its performance. It's a super lightweight gateway built on top of nginx that's optimized for low latency and high throughput use cases. It can handle hundreds or even thousands of concurrent requests, depending on your infra.

What do you dislike about the product?

Not much, but I would say that for many plugins it lacks more documentation with samples.

What problems is the product solving and how is that benefiting you?

Exposing Open Banking and Banking as a Services APIs. The time to market is not dependent on Kong, since it's quite simple to define and deploy new APIs on Kong.

What do you like best about the product?

Kong is full featured and really easy to setup API Gateway, featured as a leader in the Gartner magic quadrant.
Out of the box it has a lot of plugins centred in security, rate limiting, validations, and much more. It also supports custom plugins.
Kong is also a cloud native product, that works really well in containerized environments such as Kubernetes, and runs really well under load on low resources, such as low CPU and RAM.
Kong also offers an amazing and customizable API Gateway.

What do you dislike about the product?

I don't have anything that I dislike about the product, as Kong always listens to customers complaints and tries to fix the issues that are raised.

What problems is the product solving and how is that benefiting you?

We are providing Kong Gateway to our own customers, and customers are always happy about the product.
We have several customers using OSS, Enterprise and Konnect versions.

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

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

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Thanks to Kong, we can now centralize traffic management, apply authentication, and rate limiting easily.

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.

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.