Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
Oracle Integration (OIC)
Score 5.1 out of 10
N/A
The Oracle Integration Cloud Service is an iPaaS providing prebuilt integration flows between applications, including other Oracle products. The Integration Cloud Service is scaled for enterprises, with prebuilt codeless adapters for on-premises and SaaS systems and low-code automation capabilities.
N/A
Pricing
Azure API Management
Oracle Integration (OIC)
Editions & Modules
Consumption
0.042 per 10,000 calls
Lightweight and serverless version of API Management service, billed per execution
Developer
$48.04
per month Non-production use cases and evaluations
Basic
$147.17
per month Entry-level production use cases
Standard
$686.72
per month Medium-volume production use cases
Premium
$2,795.17
per month High-volume or enterprise production use cases
Isolated
TBA
per month Enterprise production use cases requiring high degree of isolation
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.
For all type of integration except those with a huge volume. It can deal with 20MB of transactions and processing of 1GB file when a file is being read using file or FTP adapters. It cannot be used for EDI as this support is not there. OICS is a perfect fit for other integration and is best when a customer has Oracle applications in the landscape. It is even greater if you have a requirement to create a custom form and make use of Process Cloud. All of these work very well together seamlessly. API needs can be handled by APIary.
Auto-association of Oracle applications prepopulates the application connector select box and preconfigures Oracle Integration (OIC) using secure credential access for faster integration.
Various other system connectors are available to use readily.
User-intuitive experience--Connectors, integrators, and dashboard can be seen on one page.
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.
Currently, it is not retaining the logs for more than 3 days, which it needs to address.
We also need some functionality inside the interface to re-push the same transaction again so that it will be helpful while testing and fixing the issue.
Also, some log errors are not giving the correct details. Oracle needs to rectify those.
The nearest thing I have used to OIC is UiPath, as it is often used as a tool to integrate software together. However, it is much more suited to legacy software which have little to no API endpoints. If the infrastructure already exists I understand why people use RPA for integration, however for when API's are easily accessible and you're using Oracle tools, OIC is better.
Created a solution for unique business integration with minimal processing times
Saves my team about 7 hours per week because of how it communicates with all the information. Because it communicates faster, and because there's a lot of information to communicate with, another solution might not work.
