Amazon API Gateway vs. Oracle API Platform Cloud

Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.

Incentivized

There are countless solutions and needs in the marketplace. Some solutions are straight forward, other highly complicated and innovative. From my perspective, our platform and application is highly complex and innovative, with many "one-off" features.

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

• Oracles Cloud is endlessly variable, and endlessly expandable.
• These are qualities that we needed in our platform. Oracle's Name in business was also an important aspect of our decision.
• The most important "like" is the support. Oracle Backs up its cloud with a technical expertise that I believe is second to none.

Incentivized

• Client certificates are troublesome when trying to attach them to API GW stages.
• Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
• Creating internal/private APIs, particularly with custom domains, can be unintuitive.

Incentivized

• Planned maintenance. Oracle has certain days it schedules maintenance. We have been speaking with Oracle executives about the inability to schedule maintenance on days that are custom to the client.

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

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 choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.

Incentivized

Incentivized

• ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues.
• For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical.
• Service is easy to set up authorization and it is easy to manage.

Incentivized

• For ROI, my advice would be to stay the course. It will take longer than you think and cost more than you expect.

Incentivized