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.
We do use Amazon's API Gateway service for some …
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 …