Oracle Service Bus Room for Improvement
Mainly our integrations are under JMS. We are looking at some products which have good features and performance related to the JMS. Even if tomorrow if you're planning to replace JMS with Kafka or some other product, then it will be feasible to do it very quickly. However, in Oracle, we have seen a lot of difficulties when we go to integrate Kafka with the replacement of JMS.
The personal settings are not up-to-date, in terms of orchestration. In Italy, we use SOA, however, we have faced a lot of difficulties when we have orchestration projects.
The interface console is very slow. Even in production, we need to increase the RAM or CPU. And even after that, the performance is still not good in production.
Sometimes, we have seen data loss from the EM. We can't even recover the data from the back end table. Even if we ask the Oracle support team to get a patch they're taking one or two months for the production issue to resolve. These issues are killing the business and productivity. For this reason, management decided to replace Oracle with some other products that are also based on the current application - such as SAP and TIBCO. We're updating our system anyway, so it is a good time to get rid of Oracle.
With Oracle right now, we have to hire more people in the support team to look into all the issues we're facing. That is killing our delivery times and everything.
If I want to do certain integrations or use certain plugins, it occasionally can be really difficult to do the configuration in Oracle Service Bus.View full review »
The main inconvenience is the composition between services. Using software initiation, occupation with BPM, or BPI is better. There are issues, especially if you want to create some compensation in your service bin. If you have six or seven services you call in the same process, it's very difficult and that's the main issue. I get compensation with the WBS tool.
Another point relates to monitoring. When you want to show what's happened in your system, you have to deploy a direct system on each service. It's simple to put the monitoring on your BPM and that's the main difference for me. Also, connectors can be on Apache Kafka, on Oracle, or OpenESB, or on Mule, it's the same thing. It's how you execute the process. For example, OpenESB support is the difference between the interface with the service and the implementation. Oracle is more intelligent. When you want to invoke a service B, for example, you don't directly invoke service B but ask the system for the best and most accurate implementation of B for your system and it provides that. You can't do that with a simple ESB.
For additional features, if I compare OpenESB, there is the possibility to define policy between services so that when you create a connection, you can't associate the connection with the policy. That could be included in the solution.
The connectivity with the solution is an area that needs to be improved. On occasion, requests are lost due to losing connectivity.
Also, there should be proper monitoring of what is coming into and going out of the Service bus and it should be logged.
Every request should be logged.
Technical support on the Oracle site needs improvement. When we have an issue, we create an SR for Oracle. The read the request, but they do not respond properly. When creating the SR, they ask for a lot of information from us. The requested information is provided to them but still, a solution is not provided.
It would be a benefit to have proper instruction on the different types of configuration or to have an example or suggestion for different types of Scenarios and how to configure them.
I would like the configuration information provided to us.View full review »
This solution would benefit from having more cloud-based adapters.View full review »
I can't recall coming across any missing features. There isn't anything glaring that is lacking in the product.
The initial setup is likely complex for many organizations.
In terms of the solution itself, they should be more open with the information that they provide about the licensing process. It's incredibly difficult to understand the licensing for Oracle Service Bus and it's a whole long process to get the information from Oracle itself.View full review »
Lead Tech of Oracle Service Bus with 51-200 employees
I had a problem with one of my projects because OSB cannot send cookies to the RESTful services.
This solution should work better with RESTful services.View full review »
Business&Integration Arch Manager at a tech services company with 201-500 employees
The support for GraphQL needs to be improved, and the response time for global support could be faster.View full review »