You have to understand the role in your organization for API management so that you utilize the solution in the right way.

Mashery is a good product because it has a lot of functionalities and features, even though the local version does need more care.

Given that there are areas that require improvement, I would rate TIBCO Mashery API Management at seven on a scale from one to ten.

If you were to look at other products, Azure also doesn't have monetization capabilities. It's not that creative in API management because it's just a feature that Microsoft has provided to accommodate API management. It is not a great full fledged API management solution.

Google Apigee is a very heavy solution with more than 10 components. It's infrastructure is heavy, but it does have features and functionalities.

MuleSoft is light, but it can become very costly. The licensing model in MuleSoft is very tight, and the customer has to pay extra over a period of time.

Currently, TIBCO Cloud API Management primarily facilitates connections to service endpoints within its internal mesh in the cloud. It allows integration logic to be executed within this environment, providing connectivity between applications and data.

Regarding user interface and user experience, the platform could be more intuitive than other platforms like MuleSoft. This is because it was built before the API management trend took off, so it focuses more on services, endpoints, and other technical aspects. Additionally, there are severe limitations in terms of documentation exposed for the developer portal, which has had severe limitations in the past. The developer portal serves as the business card for the API services hosted on the platform, but its presentation options have been somewhat simplistic.

I would recommend TIBCO Cloud API Management despite the issues it may have. From what I've observed in the marketplace, it remains one of the top options available.

I rate it a seven out of ten.

You can use TIBCO Cloud API Management if you are using REST API, or else I won't recommend using it.

Overall, I rate TIBCO Cloud API Management a seven out of ten.

I rate this solution a six out of ten. If a user is going to use TIBCO Mashery API Management, they need to have experts for the containerized deployment, like Docker and OpenShift. If they have OpenShift, it will make it easier as they will have support from Red Hat.

TIBCO API gateway is one of the best products available around this space. Anyone who is currently looking at API gateway should definitely consider evaluating TIBCO Mashery.

I would rate TIBCO Mashery API Management an eight out of ten.

We've had TIBCO installed in the middleware all over the place including in our back and front-end systems. I would say about 20 to 25 systems altogether within our organization have TIBCO on them.

Whether a company should deploy the solution of not depends on the business itself and the need and the necessity. There are products that are cheaper than TIBCO. And, just by being cheap, they may not be as good as TIBCO. There are products that are more expensive than TIBCO as well. That doesn't mean that they're better.

It's been a while since I've worked with the system, but I would rate it seven out of ten overall.

We're partners with TIBCO and use other products of theirs as well.

I would rate the solution six out of ten.

The solution, in terms of the needs our company has, are not being met yet. In order to rate it higher, the solution needs to meet more of our needs, especially in terms of security propagation of the token.

I would advise others to start maybe with the SAAS version in the cloud, which is where we are moving. It's best not to go for a hybrid implementation at the core.

Other than that, it's pretty straightforward.

I rate TIBCO Mashery nine out of 10. 

My advice is to check all the features from a low-level perspective if they fit exactly the needs of the company at the moment that it is trying to using this solution. I have also checked other products and I'm working on other similar products. The thing that I experienced is that most of the high functionalities can be offered by everyone. Everything can be done by everyone, or at least the basic functions can be done by anyone. The main difference is at a low level. I experienced that sometimes only when you try the product can you really see the potential of it.

So the suggestion that I want to make is simply, before choosing it, try it. Whatever questions you can take to them, the answer will be every time, "Yes, we can do everything." But then when you try the product you see the real capabilities and the real pain points if there are any, not that there are pain points every time.

I would rate this as a seven out of ten. Besides the three main issues I mentioned, TIBCO is also missing some other features: ones that are quite standard for the market but not standard for this product, somehow. The ones I noted are the main reasons, but there are a lot of others.

I gave it a seven because it's mature as a product, but it's not mature enough regarding the differing needs around APIs these days. The solution is good, but it's not good enough.

TIBCO/Mashery do offer good support and training options, so make sure you take full advantage of those to get as much as you can from the system, etc.