We performed a comparison between OpenLegacy and TIBCO Cloud API Management 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."It is possible to solve larger legacy API issues on an enterprise level with this product."
"Opens the door to connect modern web products to an old legacy system."
"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 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."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"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 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."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"The reason why we selected the solution originally was because of its ability to have a gateway both on-premise and in the cloud. This is the most valuable aspect of the solution for us."
"Conversion to RESTful and SOAP protocols and management console (can manage individually throttled settings to manage our service levels for customers)."
"The control that we have and the security features are very valuable. With regard to API implementation or API orchestration, it works very well in the cloud because as soon as you create an API with one click, you can actually expose your APIs."
"We can completely manage the APIs at the org level and BU (business unit) level."
"Very few outages or SLA issues."
"The most valuable feature is the ability to have different packages based on the API keys. The same core system can have different packages based on different environments."
"The solution is a good general API manager. They have a few propriety features but are offering items that are standard in the industry as well."
"The most valuable aspect of Mashery is its stability."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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."
"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."
"Debugging and logging for programmers could be better."
"We observed delays under heavy load conditions, and without proper tuning, changes could take an extended period to filter and become effective."
"The security needs improvement, specifically, propagation of security to an API. Calling other APIs is something that is missing in the product and that makes us think about going to a competitor."
"Monetization is not that great in API management. You need customization. Improvements are needed with sandbox local as well as with monetization. Those features are missing."
"The way agile life cycle is working needs improvement. I also want to see more support for open API standards. I want to see some improvement on the protocol transformation. That is quite missing now. These are the three main issues."
"Policy management has been a bit of a concern."
"I'd like to see TIBCO integrate authentication and security features into Mashery."
"They can fix some stability issues and probably make it more user-friendly so that not only an IT savvy person but an end-user can also easily navigate through this solution."
"The management console of API and customers' applications are not the most intuitive."
Earn 20 points
OpenLegacy is ranked 37th in API Management while TIBCO Cloud API Management is ranked 26th in API Management with 10 reviews. OpenLegacy is rated 7.6, while TIBCO Cloud API Management is rated 7.2. The top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". On the other hand, the top reviewer of TIBCO Cloud API Management writes "Is highly scalable, but monetization and analytics need improvement". OpenLegacy is most compared with Kong Gateway Enterprise, IBM API Connect and MuleSoft Anypoint API Manager, whereas TIBCO Cloud API Management is most compared with Apigee, Amazon API Gateway, Layer7 API Management, MuleSoft Anypoint API Manager and IBM API Connect.
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.