We performed a comparison between IBM API Connect, Microsoft Azure API Management, 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.
"The most valuable features are stability and security."
"The solution is very stable."
"The services that I consume through IBM API Connect are beneficial. It can handle multiple API management."
"This solution is ready to scale and already supports our agile CICD."
"Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and potentially billing rules."
"WSRR is a powerful component for getting the endpoints."
"The most valuable feature for me is the ability to distribute work among our API developers, so we don't have to do all the work as IBM API Connect administrators and IBM DataPower administrators."
"This is a very easy to use solution."
"The most valuable features are the API and integrations."
"The API management is very good."
"The most valuable features are the ease of use and it is a platform that has self-enablement for the customers to be able to register themselves."
"The Application Gateway we have found to be the most useful in Microsoft Azure API Management. We have integrated the Microsoft Azure API Management with Application Gateway. Application Gateway is a type of load balancer that we are using for the high availability of our API calls."
"I like API Management's sandbox feature. It's an environment where you can test out the API before putting it into production and connecting it to a live environment."
"Azure API is scalable."
"The ease of setting up a new solution is the most valuable feature. It's very easy to set up a new solution and to deploy it to production."
"The tool's most valuable feature is the integration of CI/CD with the API gateway."
"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 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)."
"When we did the product evaluation, we saw that TIBCO Mashery offers end-to-end API life cycle management. It provides all API features that are required for managing the complete life cycle. It includes the developer portal and tools for API monitorization. The out-of-box security features that TIBCO Mashery provides are enterprise-grade, which gives it an edge over other API products."
"We can completely manage the APIs at the org level and BU (business unit) level."
"The most valuable aspect of Mashery is its stability."
"The platform's most valuable features are its capabilities to support security measures such as tokenization, token refresh, throttling, and enforcement of payloads."
"It is easy to work with ."
"In terms of what needs improvement, some of the product documentation could be better."
"We have asked IBM for scalability and for some other features that we wanted. We had a dialogue with them and in the end, they have agreed to provide us with features related to API setup and security."
"I would like to see automation of the installation. If there could be a single-click function where you could automate everything, that would be helpful."
"The initial setup and installation could be easier."
"The solution would be better if it had cloud functionalities."
"It would be nice to have a SaaS solution that can be deployed into the cloud."
"Extracting the data could be improved."
"Our main pain points are in these two areas: creating a better developer portal and improving stability in terms of synchronization and monetization."
"The implementation has room for improvement and can be more user-friendly."
"Other products have more customization options."
"The developer console for external users could be improved, especially in the testing site."
"The cloud deployment performance could be better."
"If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be."
"The portal where we publish the APIs could be improved. Maybe this is because we didn't configure it. It is quite easy to bypass API management because we have a lot of information shared on the portal, where we publish our APIs. I worry there is potential for a security breach in the API publishing. There needs to be more security available on terms of the way we publish them."
"In the next release, Azure APIM should include deployment in various environments and CI/CD for deployment."
"The API gateway can be very complex."
"Policy management has been a bit of a concern."
"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."
"TIBCO Cloud API Management should improve its installation and make it easy."
"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."
"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."
"It lacks many features at the API gateway compared to other solutions."
"I'd like to see TIBCO integrate authentication and security features into Mashery."
More Microsoft Azure API Management Pricing and Cost Advice →
