Oracle Service Bus Reviews

Organizations have found Oracle Service Bus to enhance scalability and application orchestration without directly impacting ROI due to its technical nature. It delivers approximately 20% cost savings, boosts observability, and promotes standardization, facilitating faster recovery times and proactive interventions. Its plug-and-play architecture adapts efficiently to business and operational needs.

Oracle Service Bus pricing varies widely, with some users noting it is included with Oracle SOA Suite 11g, potentially eliminating extra licensing costs. For others, it is deemed highly expensive, with perpetual licensing and a price influenced by processor count and user numbers. Users often find the cost high compared to alternatives like Mule ESB. Licensing complexity and the need for support can impact the perceived value, with prices reaching $300,000 or utilizing enterprise agreements for more favorable terms.

• "Oracle Service Bus is a bit expensive"
• "The pricing is on the higher side."
• "I'm not aware of how much Oracle Service Bus costs."

Oracle Service Bus is primarily used for integration and connecting various applications, including API management and microservices. It facilitates transformations, message processing, and aggregation. Used by IT solution providers, developers, integration architects, telecom sectors, core banking, and global projects, it connects systems like Salesforce and ServiceNow. It supports business processes, bridging modern and legacy technologies, hosting on AWS cloud and on-premises, and managing real-time web services and managed file transfers.

Technical support for Oracle Service Bus is varied. Some find support satisfactory, rating it eight or nine out of ten, praising the speed and professionalism. Others mention delays, especially with escalations, describing it as time-consuming. Users encounter mixed outcomes; resolutions sometimes require self-troubleshooting. Many note improvement over time, though issues persist. Availability of support materials, especially for OSB 11g, is limited. Developers report insufficient support without a professional account.

Initial setup experiences with Oracle Service Bus vary. Some find it straightforward, quick, and simple, taking minutes to a few hours, especially with experience. Others find it complex due to multiple features, requiring knowledge of servers, databases, and project-specific needs. Deployment times range significantly depending on environment and team expertise. On-premises and cloud implementations differ, often requiring additional applications. Installation generally requires documentation for best practices and understanding of architecture and security considerations.

Oracle Service Bus is recognized for its scalability, accommodating high-load transactions and expanding efficiently. While it handles scaling well, complexities and occasional bottlenecks are noted, particularly in memory management and hierarchical definitions. Users have successfully scaled it with various numbers of developers and users, though challenges may arise in testing scenarios. Although non-cloud environments exhibit scalability, modern cloud-based solutions like Kubernetes present more flexible options. Despite these points, many rate its scalability favorably compared to other technologies.

Oracle Service Bus is consistently stable, praised for handling vast transactions without issues. Users highlight its reliability, even during high-demand situations. Occasional minor anomalies may occur in the development phase, needing resets, yet it remains dependable. Proper configuration is crucial for optimum performance, avoiding latency or disruptions. Companies rarely encounter significant stability issues, appreciating its performance. Most rate its stability highly, some giving it eight or nine out of ten. It proves reliable for enterprise applications.