We performed a comparison between 3scale 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."3scale API Management's best feature is API management."
"The standard deployment is very simple."
"To me, the most valuable feature of 3scale API Management is that it lets you add a backend to the product. I also like that you can integrate it well with OpenShift clusters, making 3scale API Management a useful solution."
"The solution is quite lightweight, and the installation is very easy. It's like a two-click installation."
"The most valuable features are the gateway and security features."
"The product is stable."
"I like the API automation."
"The gateway is the most valuable feature because it makes it possible for us to gather all traffic into one proxy, which is a good thing."
"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 platform's most valuable features are its capabilities to support security measures such as tokenization, token refresh, throttling, and enforcement of payloads."
"Very few outages or SLA issues."
"It is easy to work with ."
"The most valuable aspect of Mashery is its stability."
"Conversion to RESTful and SOAP protocols and management console (can manage individually throttled settings to manage our service levels for customers)."
"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."
"We can completely manage the APIs at the org level and BU (business unit) level."
"The product is not that flexible for developers. It's less flexible and rigid. It's not easy to make changes or customize it."
"We tried to use the portal, but we decided that it wasn't enough. The content management system (CMS) is not easy to use if you want to customize things, and it's hard to get someone who has the knowledge to work with the CMS."
"What was suggested by Red Hat was a crucial part of the configuration, but when we started to ask about the supportability of this configuration, Red Hat said only some parts of the configuration would be supported."
"I believe the CMS part of it has room for improvement though. That is where you write a couple of things if you want to publish your API. It's based on liquid scripting, which doesn't seem like the obvious ones to script with."
"It would be helpful to improve the customization features so that the customer can do it based on their own needs."
"The user experience could be better. The developer portal is too complex and hard to configure."
"What I'd like to improve in 3scale API Management is its route-limiting feature. Currently, I don't know how to do that effectively on the solution, but in Kong, I know how to do it, so I would love to see route-limiting being easily done on 3scale API Management. It would also be good if there was some authentication that you could do from 3scale API Management because Kong offers that functionality out of the box. What I'd love to see in the next release of 3scale API Management is the ability to integrate more plug-ins easily onto the platform, so you'll be able to extend it, and even do customs management. If Red Hat could offer that extension where it allows the internal organization where 3scale API Management is deployed on-premise to integrate its tools on top of 3scale API Management and provide an API for that, that will make the solution very powerful."
"3scale API Management only supports restful APIs and doesn't support SOAP."
"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."
"Policy management has been a bit of a concern."
"TIBCO Cloud API Management should improve its installation and make it easy."
"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."
"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."
3scale API Management is ranked 11th in API Management with 10 reviews while TIBCO Cloud API Management is ranked 26th in API Management with 10 reviews. 3scale API Management is rated 7.4, while TIBCO Cloud API Management is rated 7.2. The top reviewer of 3scale API Management writes "Useful as it lets you add a backend to the product, it integrates well with clusters, and it has exceptional technical support, but route-limiting isn't easy to do on it". On the other hand, the top reviewer of TIBCO Cloud API Management writes "Is highly scalable, but monetization and analytics need improvement". 3scale API Management is most compared with Amazon API Gateway, Kong Gateway Enterprise, Apigee, IBM API Connect and WSO2 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 3scale 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.