AWS offers the Amazon API Gateway supports the creation and publication of an API for web applications, as well as its monitoring and maintenance. The Amazon API Gateway is able to support thousands of API calls concurrently and provides traffic management, as well as monitoring and access control.
$0.90
Per Million
Mashery (now part of Boomi)
Score 10.0 out of 10
N/A
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.
N/A
Pricing
Amazon API Gateway
Mashery (now part of Boomi)
Editions & Modules
Past 300 Million
$0.90
Per Million
First 300 Million
$1.00
Per Million
No answers on this topic
Offerings
Pricing Offerings
Amazon API Gateway
Mashery (now part of Boomi)
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon API Gateway
Mashery (now part of Boomi)
Considered Both Products
Amazon API Gateway
Verified User
Anonymous
Chose Amazon API Gateway
Amazon API Gateway really provides Product functionality and performance. So this is the main reason of choosing it over the competition. Also, cost effectiveness is also second reason to choose it for our project. This product Create both internal and operational efficiencies …
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 …
Our organization uses AWS infrastructure for many projects across different business units so we choose Amazon API Gateway for initial web services development. After exploring all features especially integration with other Amazon services like Lamda and Cloud watch we chose to …
I have reviewed NGINX, Kong, and Azure API Management. While very capable, NGINX and Kong are server-based implementations; my team would prefer not to have another cluster of servers to manage. Having a managed service in API GW is preferable.
When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up …
Our primary architecture is AWS, so we selected [Amazon] API Gateway as our gateway solution. While ApiGee and SwaggerHub provide great solutions for service orchestration, [Amazon] API Gateway provided the best integrations with our web services which were mostly running …
Compared to other solutions, Azure is much easier to use and setup, but probably for hybrid solution Talend API in the cloud is the best solution and Talend API can take advantage of Amazon API Gateway, thus all this hard work is done by other software solution. Additionally, …
As AWS API comes with more security and API key authentication functions, it's easy for the organization to handle the various customers based with different level of permission. And also very easy comparable to others for tracking the API calls. Also, scalability and …
Since we have been using AWS products since the beginning, we did not think about using any competitors of API Gateway. It has great and strong integration with other AWS products.
Nginx is a powerful tool but configuring, running and maintaining but Nginx will never be a competitive advantage for our business. API Gateway is powerful because it is managed and does what we need out-of-the-box. Nginx is used more widely in the community; it may be easier …
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 …
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.
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.
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.
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
It is a great product very reliable and stable for connecting various aws services like we connected with lambda function and it is working very well, never faced any issue after the setup. It also saves out lots of money as well as time after we implemented the automatic ec2 server recovery system
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
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.
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.
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.