If you were talking to someone whose organization is considering TIBCO Mashery API Management, what would you say?
How would you rate it and why? Any other tips or advice?
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.
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.