TIBCO Cloud API Management Reviews

We mainly use it to expose APIs for internal and external usage.

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 way the Agile life cycle works needs improvement. I also want to see more support for open API standards. I want to see some improvement in the protocol transformation. That is missing now. These are the three main issues.

Based on my usage, it was quite stable.

We didn't reach the point where we tested the scalability of the system, because it was not productive. We only had three users.

Their customer support was pretty good. They resolved the problem every time, but sometimes there were technical limitations of the product itself. Every time we asked for their support they were very supportive.

There were some drawbacks on a low level, not from a high level perspective.

The initial setup was a little bit complex due to the fact that the first one was on premise, so we had some tech problems. We solved it, but it was a little bit complex in the beginning. The deployment took us two or three days, at least.

I used an external consultancy company for the implementation.

The main difference was that it was a little bit more mature in certain areas and the fact that we were, as a company, already experienced with TIBCO is why we took the direction of TIBCO itself.

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.

I use Mashery to integrate mobile applications with my services. 

The most valuable aspect of Mashery is its stability. 

I'd like to see TIBCO integrate authentication and security features into Mashery. 

I've been using Mashery for one year.

Mashery is scalable, but it depends on the environment. I am running it on-prem, so it's limited by my hosting ability. It's scalable, but I am finding some limitations with my environment. My environment is old. I am using the open-source version of Kubernetes on top of old hardware. It's an issue with my environment, not TIBCO. We're a relatively large enterprise with between 500 and 1,000 employees.

Before TIBCO, we had a custom API management solution that we created ourselves. We switched to TIBCO because it had a lot of features. 

Setting up Mashery is easy, but it takes time, especially the configuration. I need one or two only technicians to maintain it. 

TIBCO technical support assisted us. They were very helpful.  

I rate TIBCO Mashery nine out of 10. 

Conversion to RESTful and SOAP protocols and management console (can manage individually throttled settings to manage our service levels for customers).

We previously didn’t offer any API services to customers, so this has provided a new stream of traffic and exposure of our catalogue beyond the normal web store offering. We have also adopted the intercompany API Service as well.

The management console of API and customers' applications are not the most intuitive.

Over five years.

Very few outages or SLA issues.

None.

Sometimes, we have had issues pushed back to us as our “issue”, which was proven not to be the case. This can happen too quickly, seemingly without their investigating the root cause, but it hasn’t been a regular problem.

TIBCO/Mashery is our first provider in this area.

I can't comment as I wasn’t involved initially, but we are going through a migration to a new endpoint for the API service and Mashery are supporting us for this complex area.

We have secured terms on which we have been happy to renew for a number of years. However, this is an older Mashery-based contract which have been informed will change over to TIBCO and may not have as favourable terms. Not involved, so I can't comment.

Not involved, so I can't comment.

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.