My TIBCO Cloud Mashery Review
November 23, 2018
My TIBCO Cloud Mashery Review
Score 5 out of 10
Vetted Review
Verified User
Overall Satisfaction with TIBCO Cloud Mashery
We use Mashery in the Engineering department as an API Gateway for a client-facing RESTful API that has thousands of unique endpoints. We use it because we didn't want to have to reinvent the wheel on security, authentication, permissions, access rights, and things of that nature.
- The platform is solid. The product's uptime is excellent and Mashery has not struggled to handle the volume of requests our clients have thrown at it.
- Configuration is straightforward and intuitive. It's easy to create a new endpoint, a new package, a new API Key, etc.
- Mashery is good at communicating with us when new features, or enhancements to existing features, are rolled out.
- 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.
- Mashery enabled us to go to market quicker because we didn't have to write systems for authentication and security for ourselves.
- Mashery helps our MTTR when we have issues because we can use their transaction logs to identify and troubleshoot issues.
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 smaller internal APIs, but the use cases for those internal APIs are different from what we need for our customer-facing one.
We do use Amazon's API Gateway service for some smaller internal APIs, but the use cases for those internal APIs are different from what we need for our customer-facing one.