We changed our name from IT Central Station: Here's why
Get our free report covering Google, MuleSoft, Microsoft, and other competitors of TIBCO Mashery API Management. Updated: January 2022.
563,148 professionals have used our research since 2012.

Read reviews of TIBCO Mashery API Management alternatives and competitors

SVP - API integration, Fintech, Solution Architect, Delivery and Digital Lending at a financial services firm with 10,001+ employees
Real User
Top 20
Good runtime fabric and API management, but doesn't scale well
Pros and Cons
  • "The stability overall has been pretty great."
  • "We find that the enterprise level is lacking scalability."

What is our primary use case?

We primarily use the solution for API management.

What is most valuable?

Their gateway is great. They have a pay manager gateway which I find very interesting. 

We like their API manager.

Their RTF, runtime fabric, is very useful.

The stability overall has been pretty great.

We didn't have any issues with the initial setup.

Technical support has been very helpful.

Their ability to observe is good.

What needs improvement?

Some items are not ideal. For example, they should for sales management, they need better performance in the core processing.

The IO blocking isn't ideal.

We find that the enterprise level is lacking scalability.

We have some hundred Linux boxes and 400 or so APIs and for scaling, we are facing challenges. However, we haven't yet compared it to other ESBs, and therefore it's possible that all ESBs are limited in the same way.

They're in the process of evolving right now. There are many changes on the horizon that may prove to be interesting. For example, we've implemented CI/CD and now it's my understanding that the graph scale's also coming. 

For how long have I used the solution?

I've been using the solution for four years.

What do I think about the stability of the solution?

The stability of the solution is pretty good. There are no bugs or glitches and it doesn't crash or freeze. It's reliable. 

What do I think about the scalability of the solution?

The scalability is lacking. We're not sure if it's just this solution or ESBs in general, however, we've had trouble scaling as we need to.

We have about 100 users on the solution currently. They are mostly tech leads, senior developers, and architects.

How are customer service and support?

Technical support has been great. If you raise a ticket, then they respond on the basis of the severity of the issue, the criticality of the issue. They attend to the call really quickly. We've been happy with the level of support on offer.

How was the initial setup?

The initial setup is very straightforward. We didn't have any issues at all. It's simple and easy to implement and not overly complex.

We have 30 to 50 people that comprise a support team that can help handle any maintenance issues. 

What about the implementation team?

We did have assistance from MuleSoft support.

What's my experience with pricing, setup cost, and licensing?

I don't have any visibility on the licensing and therefore cannot speak to the exact cost of the product.

We are working with a platinum tier and have an unlimited core. It's my understanding is that there are no additional costs beyond the licensing fee itself. 

Which other solutions did I evaluate?

We've gone live with MuleSoft and I have been comparing it with TIBCO or Dell and IBM products. If it's threat management that can be done concurrently across platforms, maybe it can be performed better. However, I've heard TIBCO is not evolving at this time.

I was exploring other options for my own knowledge and understanding as I am looking for a job change. People not only use Mulesoft, and companies want to have knowledge in two to three platforms. I'm just comparing Mulesoft with IBM ESB, Oracle, and a few other products. 

What other advice do I have?

We're just a customer and an end-user.

Previously, a Mulesoft community edition was available. We started using Mulesoft's community version. We were exploring some ESB in our organization four years back. We started using MuleSoft as we've got Salesforce. At that time, Mulesoft was not yet acquired by Salesforce and that's why we went with the community edition. It was good. It was free. Then, slowly, we purchased some courses and Mulesoft was more connected to Salesforce. Now also Salesforce is there and AWS is there and it's more well-known and integrated. We thought it would help us due to its growth.

I'd rate the solution at a seven out of ten. It's a product that's still evolving. 

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Systems Architect at a consultancy with 5,001-10,000 employees
Real User
Great solution for exposing legacy applications.
Pros and Cons
  • "It is scalable."
  • "It would be good if the Apigee management allowed us to be able to consolidate many operations into single one for the gateway functionality."

What is our primary use case?

One of our use cases for Apigee was when we were exposing a legacy application that we were using in the past.

What needs improvement?

As of now, we have not found anything major that needs improvement. It is not something that we are heavily using, it's something that is still in the process of being adopted company wide.

Maybe securing the APIs could be a little bit more straightforward. There might be some room for improvement in the process of securing the applications that we're exposing through the API. We would like additional documentation on this or some examples of how to do it. Overall, we have had to invest more time than expected to do that setup.

It would be good if the Apigee management allowed us to be able to consolidate many operations into a single one for the gateway functionality.

For how long have I used the solution?

It has been two years that I am using Apigee.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

It is scalable.

We have around four users.

There is a team of less than five people for deployment and maintenance.

As of now, we are going through a consolidation process within the company. Oliver Weyman is part of a larger group of companies. We are among the first ones to use it, but the plans for it are still not outlined for the next year, at least. This is something that we will finish figuring out within the next few quarters.

How are customer service and support?

Support is good.

How was the initial setup?

At the beginning the initial setup was very straightforward, but the fine tuning during the setup is something that needs some improvement. The initial setup was pretty straightforward because we were trying not to do very complicated things. The initial setup was easy. But then as we started to grow, we realized that there was some room for improvement, but overall the initial setup was easy and we liked that.

Since it initially started as a POC and then we started moving forward from there, it was not complicated. But had we started with a real life application or with more complex applications or requirements, it probably would have been more difficult for us. But the way that we decided to start and also because of the complexity level, it allowed us to go very smoothly with the first setup and deployment.

What about the implementation team?

The implementation was all internal.

What's my experience with pricing, setup cost, and licensing?

Normally the company tends to do agreements with the vendors, where we are trying to get everything in one single license so as not to add complexity to the licensing. That's what I recommend.

Which other solutions did I evaluate?

The company started evaluating solutions and we found that we have three other options. One of them was Mashery, the other one I don't remember the name, and the last one was SAP. The company decided to go for Apigee and now there are no plans to go to something else because the process that we take to evaluate and assess the solution is a very thorough process. We try to spend as much time as possible evaluating the pros and cons of the solutions and what issues might come up.

What other advice do I have?

My advice to anyone considering Apigee is to start small and then grow from there. Try not to start migrating big, meaning to consolidate many applications into one single one. I would say to start small and try to run some POCs to make sure that they understand the fine tuning. Because the initial setup was easy but the one thing that needs time is the fine tuning of the setup. That, as I said before, is something that is really important for security. The security is something that I would recommend people look at.

On a scale of one to ten, I would give Apigee a nine out of 10.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
John Liu
Integration Architect at a wellness & fitness company with 5,001-10,000 employees
Real User
Top 10
Easy to use compared to other products and enables us to manage the API
Pros and Cons
  • "It's easy to use compared to other products. It's easy to set up."
  • "Other products have more customization options."

What is our primary use case?

We use it to manage the API. We have a backend API with service in the backend. We use API Management in the front to manage the vendors. They can do their own testing. It's quicker for us to put in the specifications so we can knock off the responses. We build the specs and then get an external developer to start the development without the web service being ready. 

We also use it for the security and for the clock in features.

What is most valuable?

It's easy to use compared to other products. It's easy to set up.

What needs improvement?

Other products offer more customization options. 

For how long have I used the solution?

I have been using this solution for six months. 

What do I think about the stability of the solution?

We haven't had any issues with it since we set it up. It's quite stable. 

What do I think about the scalability of the solution?

We don't need to worry about scalability. We just use it. It works on demand because it's on the cloud. 

How are customer service and technical support?

We are not a Microsoft shop, we just started using it. We haven't contacted technical support yet. 

Which solution did I use previously and why did I switch?

I also used Tibco Mashery. There aren't so many differences. The biggest difference is that you can run it on-prem while you can't do that with Microsoft Azure API Management. 

How was the initial setup?

The initial setup was pretty straightforward. It took less than one day, around a couple of hours total. It's pretty quick. I deployed it myself with some product documentation. 

What other advice do I have?

You can't use this on-premise. If you want to run on-premise you would have to get a different product. Other than that, it's easy to use and start up. There is a lot of support available from the community online. You can do a domain name yourself with Microsoft, as opposed to other products where you need to contact support in order to set up a domain. 

I would rate it an eight out of ten.  

I can't give a ten out of ten because I'm not experienced enough with it. So far so good, though. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Get our free report covering Google, MuleSoft, Microsoft, and other competitors of TIBCO Mashery API Management. Updated: January 2022.
563,148 professionals have used our research since 2012.