Microsoft offers Azure Service Bus as a reliable cloud messaging as a service (MaaS) and simple hybrid integration solution.
N/A
Oracle Integration (OIC)
Score 7.8 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 Service Bus
Oracle Integration (OIC)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Azure Service Bus
Oracle Integration (OIC)
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
Optional
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Azure Service Bus
Oracle Integration (OIC)
Features
Azure Service Bus
Oracle Integration (OIC)
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
If you need a cloud-based service bus or a simple to use queue/topic/routing/pub-sub service, then Azure Service Bus is a very good choice at a reasonable price and performance. Typically on-premise we'd use RabbitMQ because it "just works", but if you're building a "cloud-first" application, then this is the one to go with. It's especially easy to integrate with if you're already embedded in the Microsoft ecosystem.
Oracle Process Cloud is suited for medium-sized companies and up who want to create applications that can automate tasks without the need of recruiting more software developers. With a couple hours of training, any member of the organization's business team will be well-equipped with all of the knowledge that is needed to use Oracle Process Cloud effectively. If your IT team is large and able to take upon the task of making the given application, then something like Oracle BPM is a better solution.
Acting as a basic queuing service it works very well.
One of the best parts is that Azure Service Bus can work over HTTPS which helps in strict firewall situations. There is a performance hit if you choose to use HTTPS.
The routing capabilities are quite good when using topics and subscriptions. You can apply filters using a pseudo-SQL-like language though the correlation filters are quick and easy options.
Costs are very reasonable at low-ish volumes. If you're processing 10's of millions of messages a month... it may be a different story.
New enhanced activities that are targeted to reduce the integration pain. For example, file stage activity reduces the pain of chunking the input file while sending and mapping the data to the target application. Stage activity takes care of it automatically for the customer. Similarly, recommendation on the mapper is a huge plus for people looking for common integration.
There are around 50 adapters available including dedicated out of the box application adapters and generic technologies adapters on OICS. The best part of these application adapters is that they are designed considering LOB users. Most of the time integration implementor does not require, application knowledge to perform the integration. OICS has some of Oracle Cloud applications adapters which make integration much easier may not be available in other integration platforms.
Inbuilt diagnostic dashboard and error hospital makes this product lucrative. OICS also comes with integrated Process Cloud and Visual Builder at the same cost. the customer can have seamless integration with Apiary and SSI on demand.
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.
RabbitMQ is simple and awesome... but so is Azure Service Bus. Both accomplish the same thing but in different environments. If you're building a cloud-native application - especially one that is serverless by design - Azure Service Bus is the only real choice in Azure. It works well, it's performance, and it's reasonably priced in the Standard tier. From our testing, RMQ is more performant, but it's hard to compare service-based implementations vs RMQ installed on VMs.
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.
The modern and advanced analytical abilities in Oracle Process Cloud are also a missing element that should be catered to.
This tool is used greatly for IT departments at a lower level with some very basic and limited access for general employees only.
Oracle Process Cloud has many advantages like it offers some very great and scalable solutions.
I find Oracle Process Cloud pretty straightforward and easy as compared to the different options available. Lastly, I think that as it is just one platform, managing the Oracle Process Cloud is pretty easy too.
