Oracle Service Bus offers robust integration and API management, valued for its lightweight architecture, stability, and scalability. It is designed for efficient orchestration, routing, and data transformation, suitable for complex enterprise environments.
| Product | Mindshare (%) |
|---|---|
| Oracle Service Bus | 6.8% |
| Mule ESB | 17.2% |
| IBM Integration Bus | 15.5% |
| Other | 60.5% |
| Type | Title | Date | |
|---|---|---|---|
| Category | Enterprise Service Bus (ESB) | Jun 22, 2026 | Download |
| Product | Reviews, tips, and advice from real users | Jun 22, 2026 | Download |
| Comparison | Oracle Service Bus vs Mule ESB | Jun 22, 2026 | Download |
| Comparison | Oracle Service Bus vs IBM Integration Bus | Jun 22, 2026 | Download |
| Comparison | Oracle Service Bus vs IBM DataPower Gateway | Jun 22, 2026 | Download |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| webMethods.io | 4.0 | 7.7% | 94% | 95 interviewsAdd to research |
| IBM DataPower Gateway | 4.1 | 5.1% | 96% | 32 interviewsAdd to research |
| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 4 |
| Large Enterprise | 16 |
| Company Size | Count |
|---|---|
| Small Business | 78 |
| Midsize Enterprise | 46 |
| Large Enterprise | 111 |
Oracle Service Bus enables seamless integration with applications, databases, and web services, focusing on orchestration, routing, and data transformation. It supports SOAP and REST protocols through adapters, simplifying integration tasks with diverse systems. Known for its stability, scalability, and ease of deployment, it provides advanced monitoring features and a visual process view to enhance operations. Despite its strengths, there are areas for improvement, including error handling, logging, and better adapter support. Users report connectivity and integration challenges with modern systems like Salesforce, alongside a need for enhanced documentation and improved performance in cloud settings.
What are the key features of Oracle Service Bus?In the financial sector, Oracle Service Bus integrates core banking systems, connecting legacy infrastructure with modern solutions. It supports alerts and triggers in healthcare, ensures secure and efficient data exchanges, and facilitates API management for logistics companies linking diverse systems. Deployed both on-premises and in cloud environments, it adapts to industry-specific integration challenges, from managing real-time services to batch processes, making it versatile for multiple industries.
MakeMyTrip Ltd., Griffith University, Colab Consulting Pty. Ltd., Pacfico Seguros Generales, IGEPA IT-SERVICE GmbH, Guangzhou Municipal Human Resources and Social Security Bureau, Pacfico Seguros Generales, Bank Audi S.A.L., Rydges Sydney Airport, Intelligent Pathways, Nacional Monte de Piedad IAP
| Author info | Rating | Review Summary |
|---|---|---|
| IT Consultant at a tech vendor with 10,001+ employees | 4.0 | I primarily use Oracle Service Bus for integrating various systems through workflows, as it effectively enhances operations with its routing and enrichment capabilities. However, the system occasionally faces timeout issues due to constraints from legacy systems. |
| Solutions Architect at Metrobank | 3.0 | We use Oracle Service Bus to bridge modern and legacy systems. It's stable, scalable, and great for data, though its microservices need improvement compared to MuleSoft. Despite being expensive, we recommend it for a solid platform. |
| Digital System Architect at a financial services firm with 10,001+ employees | 4.0 | In my experience, Oracle Service Bus is widely used for integrating applications across networks, offering valuable connectors and flexibility. While it improves observability and standardization, resource efficiency and an API gateway need enhancement based on past usage. |
| Business Analyst at Kpmhealth.com | 3.5 | With over ten years of experience in Oracle EBS, I find its ability to integrate external systems and streamline processes invaluable, although its consolidation features need improvement. Compared to Microsoft Dynamics, Oracle handles complex structures better. |
| Party Enterprise Architecture Design Engineer at MTN | 4.0 | I utilize Oracle Service Bus for managing alerts and triggers through APIs. The review doesn't specify valuable features, improvement areas, or ROI, nor does it mention previous or alternate solutions. There's also no specified cloud provider for deployment. |
| Vice President Information Technology at Bharat Financial Inclusion Ltd | 3.5 | I found Oracle Service Bus excellent for real-time web services due to its quick time to market, stability, and scalability. However, I desire a clearer product roadmap for 12c and cloud hosting, rating it 7/10 overall. |
| Sales Manager at Mega tech S.A | 3.5 | I integrate Oracle Service Bus to resolve issues with local ISPs, focusing on infrastructure tasks. Its data transformation features are valuable, but monitoring needs improvement. Oracle's higher pricing and the need for skilled teams can affect costs. |
| Sr. IT Analyst at NCR Corporation | 4.0 | We use Oracle Service Bus to connect various applications like ServiceNow and Salesforce. It offers robust security, but connectivity with newer applications needs improvement. Previously, our company used Aurea Sonic, and we are now transitioning to Oracle Service Bus. |
| Sr. IT Analyst at NCR Corporation | 4.5 | I use Oracle Service Bus for Salesforce to ServiceNow integration, finding it stable, scalable, and easy to set up. Its versatile integration capabilities are valuable, but limited adapter connectivity and availability are areas for improvement. |
| Integration Architect at Pymma consulting | 4.0 | I find Oracle Service Bus a comprehensive, stable, and effective tool for defining services, despite its heavy resource demands, complex installation, high cost, and scalability issues, which are my main concerns. |
Positive
Positive
In previous organizations, Oracle Service Bus was predominantly used to build integration pipelines between many applications present in the network. In current organizations and projects, it remains in extensive use, providing various integrations needed for application landscapes and supporting different business operations.
The observability of the entire landscape has significantly improved, allowing proactive intervention in case of potential downtimes. Standardization and consolidation of the technology stack are essential benefits of Service Bus, as they create a consumable service and API architecture that is both scalable and adaptable. This plug-and-play approach allows businesses to scale operations according to their needs, which we have benefitted from in past projects.
Joining many services targeted at different endpoints is enabled through Oracle Service Bus. It provides a variety of connectors, allowing integration with numerous target systems.
The flexibility offered by Oracle Service Bus, especially in the latest versions, includes abstracting underlying processes and enabling drag-and-drop mappings from source to destination. This ability facilitates easy business logic implementation.
While I have not used the latest versions, resource efficiency could be optimized, considering past experiences. Another area for improvement is the potential inclusion of an API gateway, which is currently missing from Oracle's offerings.
I've been using Oracle Service Bus for seven to eight years.
I have not encountered major stability issues, although configuration needs to be thorough. Configuration errors might introduce latency or disruptions, hence careful configuration is required for optimal performance.
Scalability has not been a problem. Oracle Service Bus can be rated eight out of ten for scalability.
Oracle's customer support is excellent, rated nine out of ten. Their support is mature and provides peace of mind in terms of scalability, high availability, and security.
Positive
Before Oracle, organizations may go through benchmark evaluations comparing competitor tools and services to determine what best satisfies their needs.
The initial setup was not difficult and took approximately one hour to complete.
A separate infrastructure team was responsible for installations, which was comprised of 30 individuals, including engineers and administrators.
By improving observability and offering standardization, Oracle Service Bus has resulted in faster recovery times, proactive interventions, and a plug-and-play architecture adaptable to business or operational needs.
Oracle products are generally expensive. However, with an enterprise agreement, they offer a more affordable solutions package. It is essential to evaluate the coating offers and relationships between the organization and Oracle for cost-effectiveness.
Organizations perform competitor benchmarking or VM benchmarking for tools and services to assess potential solutions.
Oracle Service Bus offers great integration and observability benefits. It is recommended because of Oracle's comprehensive customer service and mature technology stack, ensuring scalability, security, and consolidation.
I'd rate the solution eight out of ten.
I have more than ten years of experience with Oracle EBS, particularly in the supply chain, financial, and limited experience in the manufacturing module. I have worked on financial conversions for multiple countries within a company structure, including manufacturing companies in China and sales offices or main offices in Hong Kong.
The solution helps consolidate all sales and purchase information and produce financial reports for listed companies. It allows month-end processing to be completed in a short period instead of waiting for extended periods, thus increasing operational efficiency and control.
The solution integrates external systems by providing a lot of APIs for external transactions, such as open purchase orders and sales orders. It streamlines processes end-to-end by integrating PO receipts in other systems into Oracle, enhancing the control over the entire process. It also allows the consolidation of financial data across multiple countries and companies.
The consolidation functionality is minimal, lacking advanced features for complex integrations. This includes eliminating internal company transactions for financial reporting, which currently takes a long time.
I have used the solution for more than ten years.
Oracle EBS can handle complex enterprise scenarios with a multi-company structure, however, Dynamics is not enough for such cases.
In recent years, support has improved since changing to Indian support staff. However, the timing can still take a while, and good experience is needed to work effectively with them.
Neutral
I have worked with Microsoft Dynamics for two periods yet have a strong background in Oracle. Microsoft Dynamics is suitable for smaller companies yet lacks the functionality of Oracle for more complex structures.
Integration was expensive around ten to fifteen years ago due to the need for highly specialized staff, not easily affordable for normal people.
For financial modules, I rate Oracle EBS between seven to eight out of ten for its ability to meet the needs of most companies.
We use the solution for alerts and triggers with the help of API.
It has improved the efficiency of development.
I have been using Oracle Service Bus since 2016.
Support is good.
Neutral
Pricing depends on the use case.
Overall, I rate the solution an eight out of ten.
I'm using Oracle Service Bus for all real-time web services.
What I found most valuable in Oracle Service Bus is its time to market. It's excellent.
An area for improvement in Oracle Service Bus is the roadmap for its product launch. Currently, it's unclear, so Oracle should develop a roadmap for version 12c, so people can see what's coming out of that version of Oracle Service Bus.
Cloud hosting is an additional feature I'd like to see in the next release of Oracle Service Bus.
I've been using Oracle Service Bus for the last ten years.
Oracle Service Bus is a stable product.
Oracle Service Bus is a scalable product.
I've often contacted the technical support for Oracle Service Bus, and on a scale of one to five, I'm rating support as four.
My company chose Oracle Service Bus over other products because of its stability.
The initial setup for Oracle Service Bus was easy.
I'm not aware of how much Oracle Service Bus costs.
I mostly use Oracle products such as Oracle Service Bus, Oracle SOA Suite, and Oracle FMW.
I started with Oracle Service Bus version 10g and 11g, and now I'm using version 12c.
About thirty people use Oracle Service Bus within the company.
I suggest that others look into using Oracle Service Bus because it's one of the most stable products for integration.
I'd rate Oracle Service Bus as seven out of ten because the time to launch is swift, and in terms of integration, it's a stable product.
My company is an Oracle Service Bus customer.
The use case involves tasks such as determining the appropriate licensing size, collaborating on firewall projects, and constructing the infrastructure to support the product. In most cases, I focused on integrating Oracle Service Bus to address issues, primarily with local ISPs and one ISP in Colombia. For larger projects covering all offices in Colombia, as well as two or three other projects, my involvement extended to local ISPs in Buenos Aires, specifically with Firecorp, a service provider catering to various companies within the country.
Enhanced error-handling capabilities significantly boosted the reliability of our application, preventing crashes and ensuring high availability. For context, when dealing with critical services requiring 24/7 availability, we would often implement geographic replication and active-active modes. This setup ensured continuous operation, with one system seamlessly taking over in case of downtime. While automated processes are feasible today, we relied on monitoring tools to confirm operational status. Upon detection of any issues, the system would automatically switch to an alternate data center. Our architectural approach varied based on project requirements, prioritizing resilience and continuity. The distinction between traffic replication and backup lies in the time needed for restoration. By adhering to proper processes, both methods yield similar outcomes, with the primary difference being the time required for recovery.
It aids in ensuring compliance with industry standards and protocols, although I'm uncertain whether the server comes with any preconfigured compliance settings. In my experience, I've been involved in PCI compliance and SOX compliance for large companies, and while considering the brand is essential, compliance configuration often extends beyond the software running on the network. Compliance efforts primarily focus on securing access and safeguarding information within servers or databases, rather than on individual software tools.
The most valuable feature for addressing data transformation requirements varies depending on the different layers involved in an IT project. My expertise primarily lies in infrastructure aspects. Therefore, it's important to consider various factors such as project size, focus, and the hardware being utilized, along with its configuration. For instance, when discussing infrastructure, noteworthy features would include ICI or NSX, STM, and essentially anything related to ensuring optimal performance and cost-effectiveness while considering the overall impact on the budget.
There is significant room for improvement in the monitoring capabilities. Enhancing this aspect of our monitoring process is essential for effectively pinpointing the root cause of issues accurately and resolving issues in our system.
I have been working with it for approximately eight years.
The stability is consistently high, with only one notable issue encountered. I would rate it nine out of ten.
While it offers high scalability, it also presents a challenge due to its complexity. Our user base ranges from five thousand to thirty thousand, with one particular department in Argentina boasting over fifty thousand users, since it's one of the government departments. I would rate it seven out of ten.
We've contacted tech support a few times, and the experience has generally been satisfactory. Regarding issue resolution and root cause analysis, I would rate it nine out of ten. However, when it comes to the time taken to escalate to the appropriate engineer with the necessary expertise, I would rate it five out of ten.
Neutral
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.
The initial setup is complex.
The number of people involved in deployment varies depending on the project's scale, ranging from one for smaller projects to four or five for larger ones. In my experience, significant deployments often entail multiple profiles. For instance, in the database aspect of a major project, installation, configuration, testing, and tuning phases are crucial. This process typically spans several stages, with additional tuning iterations even after transitioning to production.
The pricing is on the higher side. I would rate it ten out of ten.
My recommendation varies greatly depending on the specific context. Factors such as budget constraints, available personnel for system management, and geographical location play significant roles. It's crucial to consider the unique challenges and resources available in each country or region. For instance, hiring local talent in countries like Argentina, Brazil, or Colombia may present different challenges and salary considerations compared to the UK. Overall, I would rate it seven out of ten.
We are using Oracle Service Bus to connect multiple applications with multiple environments. So it's like we are connecting ServiceNow to Salesforce and ServiceNow to a legacy system.
With Oracle Service Bus, we can connect with different types of systems. Another feature I like the most is the security feature.
In my opinion, Oracle needs to improve its connectivity with the new applications, like, ServiceNow Salesforce, and it needs to be improved more adapters so that it can easily connect with others.
Moreover, there is room for improvement in customer service and support.
I have been using Oracle Service Bus for around ten years. I am currently using version 12.2.3.
Oracle Service Bus is very stable. I would rate the stability an eight out of ten.
Scalability is very robust. I would rate it a nine out of ten.
Occasionally, we haven't received good solutions from Oracle.
Neutral
We are using cloud and on-prem both. The deployment took around 15 minutes only. The deployment process involves submitting our code, and the admin team takes the latest version of the Endpoint. They then execute some scripts to deploy it.
I would rate the pricing model an eight out of ten, where one is the lowest and ten is the highest.
I have also worked with Aurea Sonic, or simply Sonic. initially, our company was using Aurea Sonic. However, they later upgraded to Oracle Service Bus, which is why I started using Oracle Service Bus as well. Currently, I am working with both.
I would suggest using this solution. Oracle Service Bus is very good. Any organization can use it. So it's very robust and scalable, and its security features are very good.
Overall, I would rate the solution an eight out of ten because there are some loopholes in service and support. Sometimes, when we have issues and go to Oracle support, they will not give us solutions. Instead, they will ask for so many log files and emails. The product is good, but the support is not.
We use Oracle Service Bus to send data to ServiceNow because we needed to connect Salesforce to ServiceNow, so that's our use case for the solution.
What I like most about Oracle Service Bus is that you can use it for many integrations. For example, you can use it for on-premises to on-premises integrations, on-premises to cloud integrations, and cloud to on-premises integrations.
What needs improvement in Oracle Service Bus is the connectivity between adapters such as the Salesforce adapter and database adapters. The limited number of adapters compatible with Oracle Service Bus makes you want to switch to a different solution.
I have ten years of experience with Oracle Service Bus.
Oracle Service Bus has good stability. My company rarely has an issue with it. It's mostly stable.
Oracle Service Bus is a scalable solution.
Sometimes, we contact the Oracle Service Bus technical support team and they immediately assisted us with our issues.
The initial setup for Oracle Service Bus wasn't complex. You can easily install it. There wasn't any challenge with installing the solution.
The implementation strategy my company used was to install Oracle Service Bus via scripts, similar to a DevOps deployment.
We implemented Oracle Service Bus through an in-house team.
A different team handles the licensing for Oracle Service Bus, so I don't know how much it costs.
My company has almost a hundred customers, so it has a lot of users of Oracle Service Bus.
Only four people handle the deployment and maintenance of Oracle Service Bus.
I would recommend Oracle Service Bus to people who want to start using it because it could be used for a lot of cases and for a lot of integrations.
My rating for Oracle Service Bus is nine out of ten.
We use Oracle Service Bus in the business sector (B2B and B2C). The developers use Windows machines for development and CentOS is the current OS for test, preprod and production environments.
Our primary use case was to implement business processes that can use legacy services (Java, .Net, Package Software). The other main objective was to monitor and analyse our business processes.
This tool allows us to define our services precisely. Although the XML language and the duo of XSD and WSDL may seem cluttered and inflexible at first glance, it provides us with rigour in our development processes and in defining our services. By using a strict service contract, we were able to reduce the misunderstandings between the development teams and the maintenance costs of our project.
Oracle Service Bus is a comprehensive product with many useful features for defining business processes, a powerful mapper, an implementation with many connectors that make life easier.
We were able to easily implement business processes related to sales scenarios.
As I explained earlier, Oracle Service Bus focuses on orchestrating services, but also allows us to compose services. This allows us to improve the granularity of the orchestration.
We have been able to take advantage of the monitoring
The documentation is well done.
The product is heavy and requires many resources (CPU, hard disc, memory). The installation is lengthy and complex and looks like an installation from the 90s. The installation of a database (Oracle if possible) and Weblogic is also required.
Today Oracle offers a Docker image that could reduce the installation effort.
In development, we often do not have the equivalent of the machine we can use in production. Because of the resource requirements, it was difficult to test clustering and high availability on development.
II have been using Oracle Service Bus for about three years as an integration platform for various integration projects. started using Oracle Service Bus for approximately three years for different projects.
With respect to stability, the product is good.
Scalability suffers because this is a very large product. Everything is recorded, and everything is very strict at the technical level. For example, it keeps track of what name is linked to each transaction.
If you have a lot of money, then this is a scalable product.
Being an Oracle product, everything is recorded in a database. That means that there is a bottleneck in terms of scalability.
We have between 10 and 20 developers working on this product. It is now in production but I can't easily estimate the total number of users.
We spent some time testing and found some problems with scalability. It can be difficult because when you test, you don't really simulate the behavior of the end-user. For example, people might generally use it in the morning but then one afternoon, everybody is using it and you don't know why. Ultimately, we had good test results but we were annoyed with the scalability.
We had some issues with support. It was a situation where we were under pressure and it took the technical support too long to reply and too long to solve our problem.
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.
With respect to implementation, this is a very heavy product. It isn't something that is implemented in isolation. Rather, you have to have applications such as a database and an application server, in addition to the Oracle Service Bus itself.
The basic installation will take a day to complete. After that, you need the resources to run that type of software.
The deployment itself is very easy because you just have to install a service on the application server.
Our in-house team was responsible for deployment but I was not there for all of it.
This is a very expensive product and the price varies depending on factors such as the number of processors and the number of users. Our licensing fees are approximately $300,000.
Depending on what other products you license from Oracle, you may have use of Oracle Service Bus. For example, if you use Oracle CRM then you have the right to use the Service Bus as well.
In a case like this, you have a good product, and you can save money on the license that can be put toward development, machines, and resources such as memory.
We target large companies that already have a regular license but if you have an SME or an average company with 100 people or less, then this product is not worth it because the cost is so high. Furthermore, you will be locked in with Oracle.
In summary, this is a very complete product and it works well for us.
I would rate this solution an eight out of ten.
