We performed a comparison between MuleSoft Anypoint API Manager 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."It is a good management tool for controlling purposes."
"The developer portal is easy to integrate. It is easy to use, easy to integrate, and I like the developer portal."
"MuleSoft Anypoint API Manager is a low-code product."
"Its best feature is that its plugins are somewhat unique in the market. We have budgets, Prime membership, and pre-plugins available in the marketplace that we can use immediately."
"It can create high-cost solutions, allowing for a great deal of customization to make it well-suited for specific needs."
"We use it heavily because Azure offers better pricing than its competitors."
"We can use both on-premises and cloud setups."
"I believe the API connectivity within the cloud marketplace is most valuable."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"Opens the door to connect modern web products to an old legacy system."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"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."
"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."
"The product's price should be available for public review since it is not currently available for others to see, making it one of the areas where the product has certain shortcomings."
"One improvement is maybe to add a plugin in the API manager. Let's say an organisation is using SOAP services or legacy APIs. Maybe I don't want to migrate it to rest API, but my plugin should be able to convert Jason to XML. Basically, protocol transformation features in API Manager."
"Since most components are situated in the cloud, there's one particular hosted in the cloud. This presents a considerable challenge. While all other components are implemented on-premises, this specific one isn't permitted to be hosted in the cloud as per customer requirements. Shifting this component to an on-premises environment requires a significant effort."
"The initial setup is very complex."
"They should develop on MuleSoft as it would be a good way of improving API monetization."
"Monetization and cataloging can be improved."
"We have issues with the tool's pricing. The product seemed to have most of the features required for the tasks I was working on. I didn't feel the need for additional features. However, one aspect that could be improved is making the platform more user-friendly for non-technical users. While it's not necessarily complex, it does require some familiarity. Unlike open-source tools available online, accessing and using this product may not be as straightforward. It needs to offer training to its users."
"The API gateway and API runtime are too heavy, which means that it is not suitable for microservices."
"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."
"Debugging and logging for programmers could be better."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
More MuleSoft Anypoint API Manager Pricing and Cost Advice →
Earn 20 points
MuleSoft Anypoint API Manager is ranked 4th in API Management with 49 reviews while OpenLegacy is ranked 37th in API Management. MuleSoft Anypoint API Manager is rated 8.2, while OpenLegacy is rated 7.6. The top reviewer of MuleSoft Anypoint API Manager writes "Responsive technical support, low tickets issued showing great stability, and limitless expansion". On the other hand, the top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". MuleSoft Anypoint API Manager is most compared with Microsoft Azure API Management, Amazon API Gateway, Apigee, IBM API Connect and Kong Gateway Enterprise, whereas OpenLegacy is most compared with Kong Gateway Enterprise 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.