OCI API Management vs. Workato

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

Well Suited

• Business Process Work Flows, File Management, Small/Medium # of Records Queried (<~1000)
• Closing a sales deal in system one kicks off work flows in system two for implementation
• Notification of key events in system one via text, outlook event, etc
• While I note management of two-way integrations needs improvement, it is a strength of Workato and easier to set up here than in any other tool.
• Support for connectors business processes require (Docusign, Dropbox, Outlook, Quick Base, Salesforce, etc)

Needs Improvement -

• Management of two-way integrations. It's often a bit of a struggle to create the appropriate fields in both systems to ensure redundant jobs are not run nor infinite loops created. That said, Workato does provide some documentation to counter this.
• Working with Large Data Sets (1000+)

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.

• Workato is very easy to pick up and use. You'll be creating complex recipes within days. The UI, workflow, formulas, and other features are very intuitive.
• Workato is very powerful. The native connectors it has to hundreds of software already, allows users to make substantial automation and integrations, but the HTTP connector makes it seem like it has no boundaries. If you are using software that isn't a native Workato connector but it has an API, you can use their HTTP connector to make calls to and from.
• Workato is always making improvements to its platform. This includes adding more connectors, more features, updating current connectors to be more powerful, or expanding on other tools it offers.

• 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

• Customization has a bit of a learning curve associated with it. Be prepared to expand your programming knowledge for any deep customization, however having the option to customize is critical
• Online training material is out there, but can be a bit cumbersome to read through and retain. More straight-forward online training material would help 10 fold

We need to develop Enterprise Application Integrations and Workato was not designed for this

Due to prebuilt recipes, Workato is easy to learn and use for non-technical users if their use case fits the existing recipes. It is not easy for non-technical users to create, modify, debug or maintain complex integrations that are outside the prebuilt recipes.

They employ an extremely knowledgeable team of problem solvers. I've never had a disappointing interaction or one that has left me still searching for answers. I know that when I ask for help, they'll partner with me until we find a solution together

Incentivized

We discovered that we could not use Workato for our more complex, large enterprise integrations. It was useful for simple workflows that matched the prebuilt recipes.

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 found Workato to be easier to use, more powerful and more robust than other solutions we tested at the time. It simply does the trick and allowed us to implement all that we needed in all the precise details we needed. It gave us all the power, flexibility and autonomy we needed without bogging us down with unjustified complexity. Workato came through for us and that's why we keep using it after three intense years.

• 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

• Workato is an unusual type of software in that it’s very much middle-wear, which means it’s extra important for stake holders in your company (especially those who won’t be interacting with Workato on a daily basis) to see the ROI that Workato can provide. Typically ROI is in developer time, as well as replacements for other SaaS tools. For our team, we move 2X as fast and need 1/2 the developers, so the ROI is just incredible.