We performed a comparison between IBM Integration Bus, JBoss ESB, and Oracle Service Bus based on real PeerSpot user reviews.
Find out what your peers are saying about IBM, MuleSoft, Software AG and others in Enterprise Service Bus (ESB)."I am into microservices using Java Spring Boot, but if we are using legacy systems, IBM Integration Bus is very good for them. They have their own computational logic called EC12, their own proprietary language. You can do any kind of complex logic and can implement other ESVs that I have seen."
"The most valuable feature is the security."
"Promotes the reuse of developed resources to more efficiently consume resources."
"It makes the communication between multiple and heterogeneous applications so easy. We can bring together different messages and applications from different platforms and connect them through IBM Integration Bus."
"It's easy to develop things, and it's easy to handle."
"The most valuable thing is the loose coupling and making the change in only one stack of the ESB layer or the middleware layer."
"I recommend it for large enterprises but only for specific use cases. You need to have a relatively mature integration practice in your organization to leverage its capabilities fully."
"The most valuable features of the IBM Integration Bus are flexibility. It's also an alternative for integrating it with other projects, which we are not ready at this time to do, such as switching to tunnels. The tunnels would be used with other partners to make sure everything is secured."
"The solution is very easy to use. I can download the trial version and just give it a go."
"There are always continuous improvements that are happening."
"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."
"This product is not complicated and very easy to learn."
"Monitoring feature that allows tracking of the web's UI development."
"What I found most valuable in Oracle Service Bus is its time to market. It's excellent."
"It is lightweight and one can easily integrate with different applications, databases, JMS, or web services through different protocols."
"Overall it is a pretty good solution."
"The interface is fine and the solution is quite robust."
"The solution’s pricing could be improved."
"I don't mind the pricing."
"Development toolkit (based on Eclipse) should be improved in terms of responsiveness."
"I would like for them to make the training much easier."
"The price could be better. It would also be better if they simplified the code."
"The user interface could be improved in a future release."
"They need to come up with Integration Platform as a Service (iPaaS). It should also have a feature for integrating with those applications that are on the cloud."
"IBM Integration Bus could be easier to manage, but this is true of all vendors. It doesn't always do what it says on the box."
"The EPA, from what I understand, lacks a lot of features and it doesn't really know how to interface with legacy systems or how to develop APIs for legacy systems."
"It needs to support more adapters, because the integration points keep changing and new things keep coming up. It also needs to be more scalable."
"This solution should work better with RESTful services."
"The pricing of the product could be better. It's a bit high."
"It's very complex and hard to learn. There's a steep learning curve."
"Lacks sufficient cloud compatibility."
"We have faced a problem with the heap memory side, but that is stable now."
"There is significant room for improvement in the monitoring capabilities."
"The initial setup is likely complex for many organizations."
Earn 20 points