- It’s a lightweight tool compared to Oracle BPEL
- The design of the product.
Because it can handle JSON inputs, we can now use JSON.
The logging and error-handling framework can be improved.
Usage of DVMs, MDS and other additional features that are possible in XSLT in BPEL are missing in this product.
I have used it for the past three years and I am satisfied with it.
There were no issues with deployment; it was very straightforward.
I have not encountered any stability issues. The product is highly stable.
I have not encountered any scalability issues. The product is highly scalable.
Technical support is 3 out of 5; availability of materials and support related to OSB 11g is less commonly available.
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.
Initial setup involves a learning curve; it’s not as straightforward as Oracle BPEL. For example, defining custom variables, assigning and replacing different activities is a bit intriguing compared to BPEL.
We implemented it through Zensar. Their level of expertise is 4 out of 5.
ROI is not tangible, but we have benefited highly from this product.
I heard it’s available free with Oracle SOA Suite 11g, so don’t worry about additional licensing costs for this product.
Before choosing this product, we did not evaluate other options. We only explored different Oracle alternatives.
It is a very lightweight product and has great processing speeds.