Amazon API Gateway vs. Mashery (now part of Boomi)

API GW is great for giving access to asynchronous operations that are fast and don't need to be online all the time. Lambda functions are the classic example. In the past, an operation that is called on via an HTTP endpoint would be implemented using a server-based solution. With high availability in place that would include a server or two and a load balancer. Over time this setup can be costly, especially if the service is not used at full capacity; cycles are wasted when the servers are sitting there waiting to respond. If the operation can be distilled down to a function, an API GW + Lambda solution could be put in place that performs the operation as needed only when requested. Comparing the low price point for API GW requests and Lambda CPU+Memory, the savings can be night and day over the server-based implementation.

Incentivized

TIBCO Cloud Mashery allows you to quickly enable API access control and management together with quick and easy setup of the developer portal. It focuses on core API management with limited integration features (filters, adapters, orchestration) - so TIBCO Cloud Mashery is mostly suited in a setup which already addresses integration features with other products.

Incentivized

• API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
• API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
• API Gateway's pricing can be very attractive for services that are accessed infrequently.

Incentivized

• Throttling of requests helps prevent DOS attacks. Attackers try to wreak havoc wherever they can. Mashery helps you control your environments to throttle every endpoint independently.
• The interface for setting endpoints is very intuitive and makes real-time adjustment easy to do.
• TIBCO Cloud Mashery support is superb. I do not have to go to their website to know of any issues. They are proactive in communicating with their customers

Incentivized

• I think there should be another way of enabling CORS. It basically creates OPTIONS for every endpoint, which makes your API Gateway look complicated.
• The integration timeout limit is 30 seconds, which limits you into that time.
• API Gateway UI should be improved and should work correctly when more than two people are adding/editing endpoints.

Incentivized

• Mashery should allow orchestration and transformation out of the box rather than it being a service or having to buy additional services.
• The dashboard is easy to use but I think it needs a face lift and it needs to start using TIBCO Spotfire to make it more of a analytical engine.

Incentivized

Ease of use.

Incentivized

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

Incentivized

We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.

Incentivized

Support has been good overall.

Incentivized

Initially it was difficult to understand . after few day , it was easy

Incentivized

Pricing is better at Amazon API gateway. Amazon API gateway is more user-friendly than SAP HANA Cloud. But SAP HANA Cloud supports more programming languages. The centralized management and monitoring system of Amazon API Gateway is more user-friendly. The User-Interface of Amazon API gateway is also better. Overall we can conclude that Amazon API Gateway provides a better work experience than SAP HANA.

Incentivized

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 process. Tyk is open source and evolving very fast, but 2 years back, it was not mature enough. That might have changed now.

Incentivized

• Positive, which accelerated business deliveries in months
• Negative, but in our positive case, if you are going to change the solution in the future, you need to adjust several things for the new solution.
• Positive, users celebrated with ease of use (lower learning curve, lower cost).
• Positive - Pay according to usage

Incentivized

• 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.

Incentivized