Amazon API Gateway vs. Apigee Edge

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

Apigee has been great when managing the quota based access to the APIs. It is really good and suitable when considering proxying the in-house server endpoints access with the way it provides security with API Key validation and OAuth.

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

• Manage user access, we can allow specific access to users based on their need and even customize requests of services based on user requirements.
• Allow branding, so that SFO can maintain its look and feel but still get the support and functionalities we need from Apigee.
• Integrates well with other platforms we use.

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

• Might need to bring in more features that a gateway performs, such a orchestration to some extent.
• May seem to be costly at start for small scale enterprises.

Incentivized

I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.

Incentivized

Support has helped us to resolved all the queries and community support was also good.

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

Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.

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

Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSON

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

• Unruly, difficult to maintain, unable to test, difficult to troubleshoot and debug. Every ticket that requires Apigee work increases stress and anxiety.

Incentivized