Mashery, for a time sold as TIBCO Cloud API Management, was an API management solution whose former capabilities have been added to Boomi's enterprise platform.
Other providers have been considered, such as Mulesoft and IBM. The choice for Tibco was primarily inspired because of the existing partnership, and the flexibility of their offering.
Mashery, in its deploy anywhere approach, protects web and non-web applications. It is flexible and holds its own against AWS's Web Application Firewall.
Amazon API Gateway mainly. We find AWS is innovating very fast in the space. For the user's already with workloads running in AWS, it's easier to integrate with many other value add services like security and monitoring.
TIBCO Cloud Mashery rates easier to use in API implementation and deployment. It also allows combining multiple APIs into packages which can be consumed by different applications.
Our selection process happened in 2016. TIBCO Mashery's easy hybrid deployment model was the reason why we decided on Mashery over Apigee. Akamai API Gateway is now a new tool on the market evolving really fast but was not available yet when we went through the selection …
When the evaluation of API Management was done, the market for a cloud, SaaS offering was limited. The short timeline for setting up TIBCO Cloud Mashery and the quick enablement of the developer portal have been major decision criteria.
I've really only looked at Mashery since it has been around a very long time and has a rich feature set. I do know our platform teams are looking into AWS gateway but not sure this product has everything we need.
When we were first trying to identify an API Gateway provider, we evaluated Mashery and Apigee and chose Mashery because they were more competitive on cost. Now that we are with Mashery, we have not considered other vendors.
I use Mashery because it is very easy to use and it can help some of the older people in my firm to understand how to use Mashery in the new programs in terms of back end and front end development. It also allows other competitors to not be needed and allows me to use other …
Mashery is great when it comes to deployment to your own datacenter and when it comes to managing third party API's like Salesforce using Mashery Cloud version. I would be a little bit more careful when deploying it on Kubernetes as it was not designed for it. New version 5 is re-architected to run more on natively on Kubernetes, but we have not tested it yet.
The "Control Center" admin dashboard is not performant. We have a lot of configuration data in Mashery (many endpoints, many plans, many users, many keys, etc.) and the website struggles with the volume of data it has to deal with.
Their systems have limitations that make it more difficult for us to operate the way we would like. For example, there is a limit to the number of API Definitions we can create, as well as a limit to the number of Endpoints we can define in a Plan.
Their support organization leaves a lot to be desired. Responses are slow, and when they do come they are often inadequate. We have to re-phrase the question to get them to answer it differently, or we have to repeatedly follow up to ask for additional clarifying information.
i find some of the package adding and key are complex . UI experience is bad . Every step need front and backward navigation too much. It would be better if endpoint itself contain package and key addiction option
I've really only looked at Mashery since it has been around a very long time and has a rich feature set. I do know our platform teams are looking into AWS gateway but not sure this product has everything we need.
As a API Mediation layer it has helped with the troublesome port setup with internal and external clients. Meaning it made that easy to the client that they know where to go for access to an API.
The interactive documentation is very well put together and has reduced the time that developers have to go back and forth with each other to figure how to call the API.