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.
External reviews
External reviews are not included in the AWS star rating for the product.
Easy to use and robust
Integration of Kong API Gateway.
Powerful and Scalable API Gateway with Great Extensibility
We use kong as our api gateway
Like cors management ip filtering grpc gateway...
overall best Api management vendor and product and cicd solution with AI & ML.
Breadth of services
Product roadmap and future vision
Product functionality and performance
Strong customer focus
Strong services expertise etc. that way used Kong API Gateway product, also benefit organization.
Custom plugin capability with enhanced high traffic handling and lightweight performance
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using Kong for about five years.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
I am currently using a new gateway called Tyk. However, Kong is far better as an open-source tool.
What's my experience with pricing, setup cost, and licensing?
Kong's pricing is reasonable, as the open-source version provides sufficient functionality for a startup like ours without requiring a high initial investment.
Which other solutions did I evaluate?
We evaluated Tyke as a new gateway solution.
What other advice do I have?
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.
Which deployment model are you using for this solution?
The versatility of Kong Gateway
Amazing API Gateway
Provide amazing functionalities of plugin and we can also create custom plugin by building lua code.
Provide developer protal functionalities for the developer to onborad api to show them to the outer World.
Good customer support.
Comprehensive Review for Kong API Gateway
Extensive Plugin Architecture
Comprehensive API Management
Strong Security Features
Service Mesh Integration
Active Community and Support
Steep Learning Curve for Custom Plugins
Occasional Gaps in Documentation
High Cost of Enterprise Edition
Potential for Configuration Challenges
Problem: Complex and time-consuming management of multiple APIs.
Benefit: Streamlines and automates API management, reducing manual workload.
Security
Problem: Ensuring API security against unauthorized access and threats.
Benefit: Enhances security with features like OAuth2, JWT, IP whitelisting, and data encryption.
Scalability
Problem: Handling high volumes of API requests without performance issues.
Benefit: High-performance architecture ensures scalability and low latency.
Extensibility
Problem: Difficulty in customizing API functionality.
Benefit: Extensive plugin architecture allows for tailored solutions and enhanced functionality.
Service Mesh Integration
Problem: Complex integration of APIs within microservices environments.
Benefit: Seamless compatibility with service mesh architectures and container orchestration platforms.
API Legend
Additionally, I love the Kong's custom plugin feature, which allows me to enhance API capabilities according to my needs.
utilizing the portal for API sales. Additionally, I think there should be limits on the number of applications developers can create from the developer portal.
1. Enabling the addition of headers to my/client request payloads before forwarding them to the upstream, thanks to the request transformer plugin.
2. Safeguarding my service from DDOS attacks through rate-limiting plugins.
3. Facilitating response caching via the Response Cache plugin, thereby reducing response times.