Coming October 25: PeerSpot Awards will be announced! Learn more
2019-08-11T06:26:00Z
Miriam Tover - PeerSpot reviewer
Service Delivery Manager at PeerSpot (formerly IT Central Station)
  • 0
  • 14

What is your primary use case for TIBCO Mashery API Management?

How do you or your organization use this solution?

Please share with us so that your peers can learn from your experiences.

Thank you!

4
PeerSpot user
4 Answers
GK
Data Architect at a computer software company with 1,001-5,000 employees
Real User
Top 10
2021-03-25T18:47:40Z
25 March 21

We implement a lot of TIBCO solutions for our clients. Most of the use cases for this solution are generally around API monitorization and API security. Some of our clients also use it for building an API mesh. We have deployed the latest version as well as the previous versions of this solution. We have on-premises deployments and public cloud deployments on AWS.

SS
Director at a tech services company with 1-10 employees
Real User
2020-03-16T06:56:17Z
16 March 20

We primarily use the solution for B2B integration.

NF
Chief Technology Officer at a transportation company with 10,001+ employees
Real User
2020-02-23T06:17:03Z
23 February 20

We're using the solution to expose our APIs so it can be used by a civil customer, where there are mainly internal touchpoints. We are also using it to expose our APIs internally.

PD
Integration Architect at a media company with 1,001-5,000 employees
Real User
2019-08-11T06:26:00Z
11 August 19

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

Find out what your peers are saying about TIBCO, Google, MuleSoft and others in API Management. Updated: September 2022.
633,952 professionals have used our research since 2012.
Related Questions
Julia Frohwein - PeerSpot reviewer
Senior Director of Delivery at PeerSpot (formerly IT Central Station)
Mar 25, 2021
Hi, We all know it's really hard to get good pricing and cost information. Please share what you can so you can help your peers.
2 out of 3 answers
NF
Chief Technology Officer at a transportation company with 10,001+ employees
23 February 20
The pricing is reasonable. It's not too high, so there's no reason to complain about the cost structure.
SS
Director at a tech services company with 1-10 employees
16 March 20
The pricing is a bit high, but it is by no means the most expensive option on the market.
Nurit Sherman - PeerSpot reviewer
Content Operations Manager at PeerSpot (formerly IT Central Station)
Mar 23, 2018
One of the most popular comparisons on IT Central Station is Apigee vs Mulesoft Anypoint API Manager Which of these two solutions would you recommend and why? Thanks! --Rhea
2 out of 7 answers
it_user521277 - PeerSpot reviewer
Technical Lead at hcl
22 March 18
I have worked on 5 API products each product has its own pros & cons. I would choose Apigee over all others because it provides pure API Management Tools & Services. Apigee also provides a lot of OOTB Policies which can be applied with little or no change. API Development & Exception handling is too easy in Apigee compared to Mulesoft. Go for Mulesoft if ESB capabilities are required and unlike APigee we can do a lot of customization & create custom policies in Mulesoft. Mule also provides a lot of third-party connectors OOTB which can be used to quickly integrate with other systems. We can also create custom connecters as per our requirement. Apigee supports Swagger & Mule supports RAML. So if your existing services/APIs produce/use Swagger go for Apigee. Anyway, we have many scripts which convert Swagger to RAML & vice-versa. A very good Developer/API Portal is required for exposing the APIs securely & well-documented. If this is an important requirement, I would recommend Apigee over Mulesoft. Apigee's Drupal-based Portal provides a lot of features which Mulesoft Portal lacks. Apigee also provides features/tools on Analytics & Bot-Detection for improving your APIs consumption.
it_user783168 - PeerSpot reviewer
Enterprise Architect & Principal Consultant at a tech services company with 10,001+ employees
22 March 18
It depends on your needs. I would recommend Apigee if you are don’t need an Integration Platform/ ESB for any heavy lifting. Mulesoft Cloudhub comes with one common engine “Mule Anypoint Runtime Engine” which is the core and offers ESB capabilities including a lot of OOTB connectors. Now if your southbound/ downstream has a lot of legacy applications requiring message/ file based integrations, then it makes sense to use Mulesoft, wrap these legacy-interfaces as HTTP/Web end-points and wire them using API Manager. On the other hand, if you downstream is already on HTTP endpoint/ microservices, then Apigee is far more robust than API Manager. You can simply scale it to 200tps without any hassle. The deployment model of Apigee is lot cleaner as you can scale the “Message Processor & Message Router” (part of Edge gateway) separately from Dev Portal & Management server. The analytics is far superior to Mule and you far more options when wiring API than Mule. For example, the concept of IP-whitelisting, data policies (as filters) is pretty cool in Apigee. Another key point is you can have a hybrid model in Apigee with on-prem Message Router(s) to deploy multiple clusters of microservices. I have not used BaaS but it gives you the ability to create “Application Network” very similar to Mule except it looks richer. Finally, with zookeeper, clustering of Apigee Edge server is more robust than Mulesoft, especially on higher loads. My verdict is Apigee if Integration is NOT a need. BTW, I felt API Manager’s Anypoint Exchange is a better collaboration platform for sharing API definition within enterprise and outside. It's actually nice ?. But with Salesforce acquisition of Mulesoft, please understand their long-term roadmap and support/upgrade (especially if you going with On-Premise and not on cloud). Best Regards, Arnab.
Download Free Report
Download our free API Management Report and find out what your peers are saying about TIBCO, Google, MuleSoft, and more! Updated: September 2022.
DOWNLOAD NOW
633,952 professionals have used our research since 2012.