I have also used TIBCO. It's difficult to manage, but it's a very robust product. You will not see any issues, but management of TIBCO is a challenge. You need expertise. In Oracle, you don't need a huge skillset, but if you talk about the robustness of the product, TIBCO is better. The performance of TIBCO is better compared to Oracle.

I am familiar with a few similar products such as TIBCO, webMethods, and OpenESB.

OpenESB is a similar product that is based on different technology. To scale OpenESB, you need to have a very large machine.

Deploying Oracle Service Bus is a bit rigid if you compare it with similar tools, like OpenESB. For example, when you deploy an application on Oracle, you can deploy a set of services. The important part is that the service is defined when you deploy it. This can be a problem because in some cases, you just want to expose the interface of the service so that it can be used by other services.

Assume that you have services A and B; with some products, you can develop service A without having service B on your system. You simply define a dummy B on your system and after that, you can deploy. This capability means that you have can many teams working concurrently and you can manage many different types of routines because you don't have to access the service itself. You only have to access the interface. However, Oracle Service Bus does not have this capability.

My company chose Oracle Service Bus over other products because of its stability.

I've only ever really worked with Oracle products. I did not previously use a different solution.

I've been involved in numerous projects spanning over twenty-five years. My experience ranges from implementing SAP solutions to integrating various data sources and operating systems. I've managed nationwide deployments using remote desktop solutions and utilized SQL Server extensively. Throughout my career, I've worked with diverse technology brands, databases, and operating systems, including hardware components from Cisco, and storage solutions from NetApp, EMC, and HP. While I haven't directly compared Oracle with other ESP products, one noticeable difference is pricing. Oracle products tend to be higher-priced options, which may impact budget considerations. Additionally, while Oracle offers robust features, it often requires a larger team of skilled professionals to manage effectively, which can further affect costs.

I replaced this solution with a Red Hat product.

It's more mature than Red Hat. They have a whole process that you go through. If the bug is their fault, you'll get a fixed board within one to two days, which is great if it's a major issue. I'd say support is a little better than the Red Hat solution.

Even though we had been using Oracle BPEL, we had to go with Oracle Service Bus because it is able to handle JSON inputs. We tried to implement one scenario using Oracle BPEL but couldn’t achieve it in BPEL, so we had to go for OSB and were amazed by its flexibility in accepting incoming messages.

I am a solution architect and while my background is mostly in Microsoft solutions, I am familiar with the Oracle products as well. Our company has dedicated teams that are specialized in many different solutions. The choice is driven by the client. For example, if a customer mostly has Oracle products then that is the solution that we implement.

This client for Oracle Service Bus was having trouble with point-to-point integrations, so everything was being done at the back end and it affected the ability to do jobs. This is the reason that they adopted this solution.

Prior to this solution, we used Java and Java Brains suite. Using Java is more complicated, and these things are taken care of by Oracle Service Bus.

Prior to using Oracle Service Bus, I was using webMethods Integration Server, by AG.

It was not my decision to switch and I am comfortable working with either of these solutions.

webMethods is very easy to use but it does not offer the same level of capability for personalizing your development. With respect to ease of use, for data transformation in OSB, we had to write a function but with webMethods it was just a drag and drop.

For a microservices solution, we preferred to use rest APIs and a lightweight message Bus such as Kafka or RabbitMQ for integration.