Phyllo vs. OCI API Management

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

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

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

• 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