Oracle Service Bus (OSB) and IBM Integration Bus (IIB) compete in the enterprise integration category. OSB seems to have the upper hand in handling web services and integration simplicity, while IIB excels in orchestration capabilities supported by WebSphere MQ.
Features: OSB is notable for its simplicity in managing web services, integration of multiple protocols, and robust API management. Key features include security functions and system stability. IIB offers exceptional orchestration capabilities, seamless connectivity with WebSphere MQ, and extensive protocol support including HTTP and REST APIs. Additionally, IIB facilitates high availability and efficient data management.
Room for Improvement: OSB faces challenges with error handling, cloud service support, and licensing complexity. Users call for enhanced monitoring and better cloud compatibility. IIB requires improvements in CI/CD support, simpler documentation, and more straightforward orchestration features to enhance ease of use and deployment.
Ease of Deployment and Customer Service: Both OSB and IIB can be deployed on-premises, private cloud, and hybrid cloud environments. OSB is praised for its ease of use and rapid deployment, though technical support can be slow. IBM's customer service could benefit from more straightforward orchestration and automation features, while its support infrastructure is noted as strong despite some concerns about cost.
Pricing and ROI: OSB and IIB are considered expensive enterprise solutions. OSB's intricate licensing model is costly, yet users report operational efficiencies and cost savings. IBM's pricing is also on the higher side, especially for new cloud deployments, though it remains competitively priced. Despite their expenses, both solutions provide scalability and optimization benefits, with ROI not always immediately apparent.
I would rate the technical support of IBM Integration Bus as nine out of ten; it was the best.
I rate the technical support from Oracle a nine out of ten.
There are dependencies on the Java version and application being used.
In my experience, it is a scalable solution, and IBM Integration Bus is indeed a stable product.
I rate the stability of the product as eight out of ten.
They are improving one of the nodes such as the HTTP request node, implementing the indirect retry mechanism itself, and we are getting new features.
This can happen due to legacy systems that might not allow the use of microservices.
Regarding the pricing setup cost and licensing for IBM Integration Bus, I believe it is expensive.
I view both Oracle and IBM products as expensive.
The features I find most valuable in IBM Integration Bus are very useful for performing transformations from systems such as SAP to Salesforce, and from Salesforce to S/4 and 365.
The main advantage of Oracle Service Bus is the possibility to integrate different systems using workflows and different architectures in the same product.
| Product | Mindshare (%) |
|---|---|
| IBM Integration Bus | 15.5% |
| Oracle Service Bus | 6.8% |
| Other | 77.7% |
| Company Size | Count |
|---|---|
| Small Business | 15 |
| Midsize Enterprise | 17 |
| Large Enterprise | 47 |
| Company Size | Count |
|---|---|
| Small Business | 8 |
| Midsize Enterprise | 6 |
| Large Enterprise | 22 |
IBM Integration Bus provides robust integration with multiple protocol support, allowing for scalable and secure message transformation and routing between diverse systems. It enhances deployment efficiency and aligns with service-oriented and containerized environments.
IBM Integration Bus is known for its capable integration, flexibility, and comprehensive monitoring. It facilitates seamless communication, ensuring reliable data transition with high security between diverse applications. It acts as middleware, enriching messages and providing a security layer for API calls. Companies in sectors like finance and retail leverage it to enhance enterprise communication capabilities.
What are the key features of IBM Integration Bus?IBM Integration Bus is implemented in industries like banking, finance, and retail, facilitating integration of internal systems and external partners. It supports communication by receiving, transforming, and routing messages in formats like XML and JSON, ensuring seamless data transition across applications.
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.
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.
We monitor all Enterprise Service Bus (ESB) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
