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
eQube®-AG
Score 0.0 out of 10
N/A
eQube®-AG, API Gateway, manages APIs through creation, publication, monitoring, maintenance, and security. Its interface offers a governance framework for API lifecycle management, allowing flexibility in defining security policies at the organizational level and applying rules to each API. API consumption monitoring is made easy with built-in BI dashboards, facilitating rapid issue identification and resolution. The API definition capability (REST, OData, Web services) is integrated with eQube®…
N/A
Pricing
Amazon API Gateway
eQube®-AG
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
eQube®-AG
Free Trial
No
Yes
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
eQube®-AG
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 …
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.
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.
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
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.