IBM B2B Integrator vs Mule ESB comparison

"The technical support on offer through the portal is very helpful and responsive."

"The solution is useful for transferring files from one format to another format. Also, the solution is useful in translation."

"It uses VMs, allowing us to enable horizontal scaling."

"It's highly stable, and the redundancy is amazing. B2B Integrator also has a high availability option to work in a cluster environment. You rarely have issues operating it because of the HA."

"B2B provides a secure communication channel."

"Everything from the order to fulfillment to the payment process, except for physical packing and shipping, is fully automated for some customer orders."

"It is easy of use and it's easy to maintain. It's also faster to on-board partners."

"The solution is fast and easy to use."

"I like that Mule ESB provides fast and good technical support."

"Everything runs in Java, which is a useful feature."

"Mule ESB helps a lot with our microservice architecture that we're trying to build, and it is still our go-to technology when it comes to that, so it's very promising for us."

"What Mule provides out-of-box is a sufficient product."

"The connectivity the solution provides is excellent. There are often too many systems that we have to integrate and this helps with that."

"The solution offers multiple deployment options."

"The most valuable feature is the Salesforce integration."

"Mule ESB has a user-friendly design, and everything is in one place. The API and architecture are popular right now. Also, MuleSoft has a large and supportive online community."

"The dashboard is not integrated and should be bundled by the product vendor."

"They do not have a solid partner ecosystem, and they do not have a clear roadmap for down the line; they're missing that clear roadmap."

"The user interface is outdated. B2B Integrator was developed in the United States in the nineties, and the graphical user interface hasn't improved since. It's tough because you have to program the software in XML. Nowadays, other methods are easier to work with."

"Map translator needs more enhancements."

"We often need to change property files for accounts, and I don't always have access to them. For core mapping, we need to install JDK"

"Patching or upgrading the product is a bit of a nightmare. It would be nice if they removed the installation manager port. We find it complicates upgrading and patching a great deal."

"The one thing that is lacking is easy visibility. It's hard to provide business users with a view into the statuses of their transactions."

"End-to-end visibility and monitoring application required. The control center is available and covers this area, but it still fails in many monitoring scenarios."

"It would be great to see implementing security modules as a feature."

"From an improvement perspective, there should be fewer coding challenges for users in Mule ESB."

"One area that could be improved is the way that policies are propagated when APIs are moved from one environment to another. It's an issue, but when you develop and test the rest APIs in a lower environment and need to move them, there's a propagation process. This process moves certain aspects of the APIs, like the basic features. But when we move them, the policies don't always move with them. The policies should be able to move so we don't have to redo them manually. There are some APIs we use, but it's a bit tedious."

"MuleSoft is not so strong in method-based integration, so they're not so functional in that regard."

"From my perspective, Mule ESB is lightweight, but it can be improved when it comes to the agility of the system."

"In India, particularly in the banking sector, clients do not prefer cloud solutions due to regulatory and compliance requirements."

"Documentation is cryptic, product releases are far too frequent, and upgrades become troublesome."

"There are limitations with the subscription model that comes with the product."

"The price of IBM B2B Integrator is too high. However, IBM may be willing to give a discount if there are negotiations. If they see that there is a good opportunity for them they can provide a discount."

"The pricing is based on how many cores are used and the type of cores."

"The product costs more than 40K."

"The solution is priced at $20,000 to $30,000 per year with no extra costs."

"We pay an annual fee based on the number of VPUs. It's fairly reasonable. We're in the middle of analyzing other products, and they're all pretty much in the same range."

"Licensing depends upon the package you opt for within the solution. The solution is a bit costly compared to the other integration tools in the market."

"The price of the Mule ESB commercial version is expensive. However, they have a free community version."

"This product is cheaper than some offered by other vendors, although there is a problem because you have to pay for some third-party adapters."

"Most of the challenges that I had with this solution were for smaller customers. There is not a good licensing model or pricing model. It is more expensive than other solutions, and that's the downside of MuleSoft. I had to be creative to be able to sell it to the business, but we did. This is something they have to work on because for large companies, it's affordable, but for small and medium businesses, it's very hard to sell."

"The licensing is yearly, and there are additional fees for services."

"Plan your licensing model (cloud or on-premises or hybrid) that will allow seamless integration with new partners."

"This is expensive. In my next project, we had to go to other vendor."

"Mule ESB is a costly solution. We pay approximately $80,000 annually for the system. The cost of the number of instances, annual subscription, and cloud hosting services are expensive."

"The solution is expensive."