Azure API Management vs. OCI API Management

The range of policies that enable the APIs to loosely couple it with security, rate limit, retry, etc. are good. We can easily tie authentication mechanisms to external and other internal services without having to modify the backend.

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

• Management of APIs
• Security of the API through Azure AD, AD B2C etc.
• Providing an outer layer through APIs

• 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.

• Cost - the upfront cost is a bit restrictive. I've been told it is because there are a few underlying VMs that are running this service. So if you're just starting out with API management, it can be an expensive proposition. Value increases as you add additional APIs. If you're using Azure B2C for the developer portal, you'll require Standard or Premium since they support AAD integration.
• Security granularity - at time of writing, APIM doesn't support breaking out operations to products. For example, if you have an API that has a GET and a POST operation, and you want the POST operation to require a different subscription. There is a work around, but it makes management a bit messy.
• Developer and Publisher portal - it's a little weird. Microsoft hasn't migrated all the publisher portal functionality into the "native" Azure portal. So some of it feels a little weird - especially when working with the content management side of things for the developer portal.
• Scaling - while it's easy to scale up, the cost of APIM ramps up very quickly. Standard -> Premium is a 4x jump.

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

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

• It’s really pay as you go, so it's not that costly to get in and try it out. There’s no expensive client to buy and manage, but you do need to stay on top of the rapidly changing Azure environment to be sure you upgrade or adjust when needed.
• It’s not great having more than one API tool, but it’s ok to spread out your work, as you always want the right tool for the right job. For example, if you are a Salesforce-heavy organization, I’d go with Mule over Azure.
• It was easy getting an external consultant access to the tool to build their own API for a project they were working on for us.

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