We performed a comparison between Microsoft Azure API Management and TIBCO Cloud API Management based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It’s easy to set up."
"The UI management is very easy to use."
"Azure API is scalable."
"Without a doubt, it has a very robust, strong marketplace where we can directly integrate with existing APIs and begin working on those."
"I have found this solution to be easy to configure, simple to use, and flexible."
"The product gives API gateway-related features, like throttling, which are easy to use and low-code/no-code."
"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 solution is quite stable. We have no issues with it. there have been no crashes and we haven't experienced bugs or glitches. It's been quite reliable."
"It is easy to work with ."
"The most valuable aspect of Mashery is its stability."
"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."
"The platform's most valuable features are its capabilities to support security measures such as tokenization, token refresh, throttling, and enforcement of payloads."
"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."
"We can completely manage the APIs at the org level and BU (business unit) level."
"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."
"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."
"Microsoft Azure API Management could improve by having better integration with third-party solutions."
"The documentation could be improved for the customer."
"An area for improvement in Microsoft Azure API Management is deployment, in particular, the deployment of versions in Oryx. The development to production instance isn't adequate for me and needs to be improved. Microsoft Azure API Management lacks automation, which is another area for improvement."
"Azure is our most expensive resource; it's costly."
"The user interface needs improvement."
"The solution’s security and performance could be improved."
"It would be better if it were easier to transition to Azure from JIRA. For example, different nomenclature must be performed when you shift to Azure from JIRA. JIRA's storage, tasks, and ethics are treated differently from Azure. Here they might become functions, which is not an option in JIRA because that nomenclature difference is there. If someone has to get into the nomenclature, then there can be different tasks from clients, and here, they may be treated as functions. JIRA has sub-tasks, but sub-tasks don't exist in Azure. The nomenclature and the linking between ethics and a function and a story are different, and people may have to learn to adapt to the new nomenclature."
"Sometimes when immediate support is required, it isn't available."
"Policy management has been a bit of a concern."
"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."
"I'd like to see TIBCO integrate authentication and security features into Mashery."
"It lacks many features at the API gateway compared to other solutions."
"The management console of API and customers' applications are not the most intuitive."
"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."
"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."
More Microsoft Azure API Management Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 67 reviews while TIBCO Cloud API Management is ranked 26th in API Management with 10 reviews. Microsoft Azure API Management is rated 7.8, while TIBCO Cloud API Management is rated 7.2. The top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". On the other hand, the top reviewer of TIBCO Cloud API Management writes "Is highly scalable, but monetization and analytics need improvement". Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and IBM API Connect, whereas TIBCO Cloud API Management is most compared with Apigee, Amazon API Gateway, Layer7 API Management, MuleSoft Anypoint API Manager and Kong Gateway Enterprise. See our Microsoft Azure API Management vs. TIBCO Cloud API Management report.
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.
