We performed a comparison between Kong Gateway Enterprise and OpenLegacy based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Google, Amazon Web Services (AWS) and others in API Management."Kong Enterprise has excellent plugin support."
"It boasts remarkable speed and stability, and these qualities, particularly the gateway's resilience, are standout features for me."
"We use the solution for load-balancing, caching, and rate-limiting APIs."
"The solution provides good performance."
"This is a solid intrusion prevention system that combines a firewall and antivirus in a single solution."
"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."
"The tool's feature that I find most beneficial is rate limiting. In our usage, especially in the financial sector, we prioritize limiting API usage. This is crucial because we provide APIs to other companies and must ensure they adhere to their allocated usage limits. Without rate limiting, there's a risk of excessive usage, which could result in significant costs."
"Kong enterprise has significantly enhanced our ability to manage and secure our Microservices. Its most valuable feature is monitoring."
"Opens the door to connect modern web products to an old legacy system."
"The biggest advantage of OpenLegacy was how simple the technology was. We were able to build out the OpenLegacy parts very quickly. We put together a couple hundred APIs in six months."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"The technical support team's response time needs to be improved."
"The ease of billing is lost when Kong is not available directly on the Azure marketplace. This is one area where they can improve."
"The solution should include policy features that are available in other solutions like MuleSoft API manager but missing in Kong Enterprise."
"From an improvement perspective, the product should offer more readily available connectors and also allow for more seamless AI integrations."
"Kong is meant for north-south communications, so it will be interesting to see what solutions they can come up with in the realms of east-west communications, service-to-service communications, and Zero Trust architecture. I believe that if they can provide for these areas, then they will be able to solve the overall integration and security concerns for microservices architecture in general."
"Kong Enterprise fails to provide live tracing of the APIs, which is possible nowadays."
"We would like to see an automatic data API when we have a table in the database."
"Kong Enterprise needs to improve its pricing, which starts at hundreds of thousands of dollars. Pricing should be based on API usage rather than monthly. It should improve its documentation as well."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"Debugging and logging for programmers could be better."
Earn 20 points
Kong Gateway Enterprise is ranked 6th in API Management with 20 reviews while OpenLegacy is ranked 37th in API Management. Kong Gateway Enterprise is rated 7.8, while OpenLegacy is rated 7.6. The top reviewer of Kong Gateway Enterprise writes "Provides role-based access control and can be easily customized with Lua script". On the other hand, the top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". Kong Gateway Enterprise is most compared with Microsoft Azure API Management, WSO2 API Manager, Apache APISIX, Apigee and Layer7 API Management, whereas OpenLegacy is most compared with IBM API Connect and MuleSoft Anypoint API Manager.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.