Try our new research platform with insights from 80,000+ expert users

Amazon API Gateway vs OpenLegacy comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon API Gateway
Ranking in API Management
3rd
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
42
Ranking in other categories
No ranking in other categories
OpenLegacy
Ranking in API Management
34th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2025, in the API Management category, the mindshare of Amazon API Gateway is 13.8%, down from 14.5% compared to the previous year. The mindshare of OpenLegacy is 0.3%, down from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Dinesh Agrawalla - PeerSpot reviewer
Requires minimal configuration and easy-to-launch
I would like to improve the restrictions and security elements of the solution, as there are certain configurations that are not currently supported. There are certain restrictions that cannot be implemented without web access. In the next release, I would like a feature that can validate requests and filter out any jQuery injections. Additionally, I would like to prioritize these requests. I've noticed that such features are usually not available in web applications.
reviewer1042905 - PeerSpot reviewer
The biggest advantage is how simple the technology was.
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. OpenLegacy handles the bread-and-butter TP monitoring stuff, but I am working for one of the six banks in the United States still using the Hogan mainframe, which has a slightly proprietary mechanism. But OpenLegacy currently doesn't have a connector for Hogan. So it would help if they could build one. That would appeal to financial institutions that still use Hogan, like US Bank, Wells Fargo, KeyBank, and Vanguard.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature is it has lots of integration."
"It is a stable solution."
"In terms of scalability, I haven't encountered any issues with API Gateway. We've significantly increased our traffic from hitting it once or twice a minute to now hitting it ten to fifteen times within a minute. In an hour, we're receiving hundreds of hits. So, it's performing excellently."
"It's flexible. It was valuable."
"It allows us to expose our APIs and provides tools for managing them."
"The most valuable feature in Amazon API Gateway is the itinerary release."
"In terms of most valuable features, it would say that it is really easy to start working with it."
"Amazon API Gateway facilitates our serverless architecture, particularly with Lambda, by allowing us to perform various tasks. For instance, Lambda functions authorize API calls, execute multiple workloads, and integrate with other services like Azure and Kubernetes. Additionally, we leverage Lambda functions behind the Amazon API Gateway to query databases, process data, and interact with different systems."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"Opens the door to connect modern web products to an old legacy system."
"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."
"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."
"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."
 

Cons

"I believe that there could be more features associated with analytics since it is an area where the product lacks."
"The user interface, in general, can be better. The user interface for the entire Amazon cloud can be more friendly. There are some scenarios that are not really easy to manage and configure through the user interface."
"Currently, I'm not facing any issues with Amazon API Gateway, which satisfies my requirements. I'm pretty happy with what Amazon API Gateway offers, but as its pricing is on the higher side, that's one area for improvement in the solution. What I'd like to see in the next release of Amazon API Gateway is an improvement in the status checks you get from the monitoring feature of the solution. Currently, you get the number of requests received, the number of reports, etc., but if there are more details than what's given by Amazon API Gateway, that will improve the solution."
"Like most Amazon services, and this one's the same, you're expected to effectively do your own support, and any other support is by emails, so it's quite limited."
"The solution should include change data capture (CDC) features that will help reduce workload"
"From a use cases perspective, you need to have an internal and external gateway. AWS can only handle external traffic so has to be used together with another solution."
"Their support services come at a considerable cost, leaving room for improvement."
"The API Gateway lacks the capability to directly facilitate API strategy development or user onboarding workflows."
"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 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."
"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."
"Debugging and logging for programmers could be better."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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."
 

Pricing and Cost Advice

"We use all open-source technology."
"It is somewhat costly, particularly when it introduces server-related features, which are often scheduled on our end."
"It's cost-effective, even as our workload and the number of APIs we manage have increased."
"AWS charges for data ingress and egress, which could be further reduced. This would be helpful for customers dealing with large amounts of data coming in or going out from their systems."
"Fees are volume-based."
"Since it's a serverless solution, Amazon API Gateway is not so expensive."
"The product is a little expensive."
"There are no licensing fees."
"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."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
838,713 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
14%
Manufacturing Company
9%
Government
6%
Financial Services Firm
37%
Insurance Company
12%
Manufacturing Company
10%
Computer Software Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Which is better - Apigee or Amazon API Gateway?
Amazon API Gateway is a platform that supports the creation and publication of API for web applications. The platform can support thousands of simultaneous API calls, and it provides monitoring, ma...
How does Mulesoft Anypoint API Manager compare with Amazon API Gateway?
I have found that Mulesoft Anypoint API Manager is the best integration tool out there for API management. It is easy to implement and learn; it provides several options for deployment, (including ...
Which is better - Azure API Management or Amazon API Gateway?
If you use Azure products, API Management is a great solution. It solves many of the problems of externalizing web services. For example, when you need versioning, establish a developer portal and ...
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

Autodesk, Fox Digital Consumer Group, iFlix, UK Driver and Vehicle Licensing Agency (DVLA), Miovision, Olympusat, PhotoVogue, Royale International Group, Veracode
Many of openLegacy's global customers are among the Global 100 companies. Review case studies in these industries: Agriculture, Airport Authority, Automotive, Auto, Finance, Insurance, Government, Healthcare, Manufacturing, and Retailwww.openlegacy.com/case-studie...
Find out what your peers are saying about Amazon API Gateway vs. OpenLegacy and other solutions. Updated: January 2025.
838,713 professionals have used our research since 2012.