Azure API Management vs. OCI API Management

APIM is useful for the standard scenarios:

1) Securing your back-end APIs - If you have a legacy back-end web service that has a basic authentication scheme, you can add some additional security by placing APIM in front, and requiring subscription keys. Leverage your existing firewall to ensure only your APIM instance can communicate with your back-end API, and you've basically added a layer of protection.

2) Lift and shift - there are always going to be clients that don't want to update their clients to use a newer API; in some cases you can make a newer API look like an older one by implementing some complex policies in APIM. You can also do the opposite, making older APIs look new, such as making an XML back-end accept both JSON and XML.

3) Centralizing your APIs - if you've acquired another company and want to make their API set look as if it's a part of the larger whole, APIM is an easy way to provide a consistent front-end interface for developers.

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

• Easy commissioning of APIs.
• Great policies to control access.
• Easy mock services for testing.

Incentivized

• API Manager allows for REST and SOAP API's to be easily created and tracked
• API Manager allows for only certain people/applications to use the API (does this thru a subscriber service it provides)
• It also publishes the API's it is tracking so developers can easily know what interfaces already exist.
• The monitoring ability is a nice feature. The admin person can easily see how and where the APIs are currently being used

Incentivized

• Lack of robustness is a bit of an issue. Several other providers offer more options and capabilities, but then, they are lacking in interface ease.
• As with anything Azure, pricing is really hard to stay on top of. I always find that you really don’t know what you’re paying for until you get the bill. Having an excellent Azure Administrator can help resolve that.
• Integrating with app services outside of Azure can be a challenge, or at least much more challenging than just using Azure App Services.

Incentivized

• Absence of Role-Based Access. A finer grain control on what type of users can call certain API Endpoints is needed.
• Performance with third-party databases isn't as fast as using Oracle Database.
• Long learning curve. Although Oracle API Manager provides performance and a vast deal of features, a certain level of expertise is required to effectively make use of them.

Azure APIM vs Amazon API Gateway:

1) Azure APIM was a complete package that included a developer portal.

2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.

3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.

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

• We can always think of positive ROI impact on business
• It helps to easily facilitate the design, deployment, and maintenance of our APIs

• Oracle API Manager supports both REST & SOAP API's.
• Secure and attributable connection to back-end services and data sources. In addition to creating API's for querying data, you can also create API endpoints that can manipulate the data in the back-end databases.
• Although Oracle API Manager provides performance and a vast deal of features, to start with it is really important you train your people working on development, deployment and administrators to effectively use Oracle API Manager.

Incentivized