Amazon API Gateway vs. OCI API Management

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

Oracle API Manager is well suited in a business or company that make use of Apis to facilitate access of backend services and data sources by the staff or customers or both. It is also imported in situations where all actions in a system need to be attributed to specific users.

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

• Mature and Reliable. Last year, Oracle API Manager was quite buggy, and couldn't be used at production-level. Fortunately, almost all of the problems that it had previously are now patched.
• Offloads Most of the Workload of Developing APIs. While defining APIs, Oracle API Manager does a great job in providing suggestions and error checks in our logic.
• Supports SOAP and REST. Not only can you create APIs that can query for data, but you can also create API endpoints that can manipulate the data in your back-end databases.

• 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

• I would say it would be nice if it could handle non-Oracle type API's...such as in-house developed interfaces, etc.
• It would be nice if it at least could list non-Oracle type APIs so that this system became a repository for ALL of the application interfaces
• Maybe it has this and I missed it, the monitoring appears to be one API at a time, would be nice to see a page that has all of the monitored APIs with some basic monitored info perhaps. It does have alerts, audit trails, and integrates with Enterprise Manager (I did not see this integration though)

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

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

Oracle API Manager is much easier to learn and understand then IBM Data Power Gateway and IBM API Connect. We selected Oracle API Manager in our company because to have a good intuitive interface with drag and drop features and because beginners and easily get up to speed to use this tool.

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

• Overall, the client is pleased with the API Manager. They are rather new to it so the ROI has not really been realized yet
• They like the ability to monitor the API's utilization (this monitoring could maybe be used for the prior question on usage billing...they do not currently do this for their supported applications)
• They like the ability that the APIs can be secured. Just because it exists, doesn't mean it can be used just anywhere...

Incentivized