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.

Kong's most valuable features are its lightweight performance when handling millions of requests and the ability to write custom plugins to enhance security, such as end-to-end encryption, even in the open-source version.

The open-source version of Kong does not support a dashboard, which would be very helpful. We use an open-source tool called Konga for basic dashboard needs, but it lacks support. It would be better if there was a comprehensive dashboard included in the open-source community version.

We have been using Kong for about five years.

Initially, we faced stability issues during an upgrade process due to migration problems with the schema. However, Kong has improved significantly, and maintaining stability is easier now when following their improved documentation and using Helm for deployment.

We've put in place SPA auto-scaling within our Kubernetes deployment, which efficiently handles increased traffic by automatically spinning up new pods, ensuring smooth scalability.

I am currently using a new gateway called Tyk. However, Kong is far better as an open-source tool.

Kong's pricing is reasonable, as the open-source version provides sufficient functionality for a startup like ours without requiring a high initial investment.

We evaluated Tyke as a new gateway solution.

If you are looking for a stable open-source gateway, Kong is a solid choice. It performs well under high traffic with low latency. For newcomers, it is advisable to explore its robust features and ability to manage high TPS effectively.

I'd rate the solution eight out of ten.

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.

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.

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.

It is a crucial part of my daily workflow.

I encounter no issues with deployments, and it reliably performs its duties on a daily basis. It proves to be both resilient and stable.

It's scalable to your needs, and if you have the financial resources, you can scale it as much as you want.

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.

The initial setup is relatively easy, but it requires a clear idea of your objectives.

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.

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.