We performed a comparison between Mule ESB and webMethods Integration Server based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Service Bus (ESB) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I'm not using ESB directly. It is the integration layer, so it's running under the hood. However, the conversion and transformation performance is excellent. Anypoint Enterprise Security is also solid."
"The architecture based on events has several connectors which allow integration from external and internal applications of the company."
"The most valuable feature is the Salesforce integration."
"Scalability and load balancing."
"For complex cases, we employ the SSLi engine, whereas for simpler ones like healthcare or response data, such as EDI 270 or 271. We prefer to use an external XRT engine instead of handling it within the ESB for ease of management."
"The connectivity the solution provides is excellent. There are often too many systems that we have to integrate and this helps with that."
"It was pretty fast to develop APIs on this platform, which is something I liked about it. So, the time to value was pretty good."
"The solution has a good graphical interface."
"I like the stability of the webMethods Integration Server."
"All of the components are very independent but are tied together to give the business value."
"Segregation of deployment for the environments is the most valuable feature of the solution."
"They are the building blocks of EAI in SAG products, and they offer a very good platform."
"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."
"The synchronous and asynchronous messaging system the solution provides is very good."
"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."
"It is a bundled product stack for A2A and B2B usage. It is one of the best products which I have used during my integration career."
"We would like to have a built-in logging framework in which we can do auditing."
"It should have some amount of logging."
"In order to meet the new trend of active metadata management, we need intelligent APIs that can retrieve new data designs and trigger actions over new findings without human intervention."
"The stability could be improved."
"Documentation is cryptic, product releases are far too frequent, and upgrades become troublesome."
"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."
"It needs more samples. Also, the dependency on Maven should be removed."
"We would like the ability to use our own code. This would allow us to develop customizations with ease. Additionally, it would be nice to have more analytics or insights on the exchanged information between databases."
"We'd like for them to open up to a more cloud-based solution that could offer more flexibility and maybe a better rules engine or more integration with rules engines."
"It is quite expensive."
"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."
"There should be better logging, or a better dashboard, to allow you to see see the logs of the services."
"The learning curve is a little steep at first."
"I would like to see the price improve."
"For code version control, you need to use some external software."
"Large file handling is pretty hard comparatively to other middleware tools."
More webMethods Integration Server Pricing and Cost Advice →
Mule ESB is ranked 2nd in Enterprise Service Bus (ESB) with 46 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. Mule ESB is rated 8.0, while webMethods Integration Server is rated 8.0. The top reviewer of Mule ESB writes "Plenty of documentation, flexible, and reliable". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". Mule ESB is most compared with IBM Integration Bus, Oracle Service Bus, Oracle SOA Suite, Red Hat Fuse and IBM DataPower Gateway, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, TIBCO BusinessWorks, Boomi iPaaS and Oracle Service Bus. See our Mule ESB vs. webMethods Integration Server report.
See our list of best Enterprise Service Bus (ESB) vendors.
We monitor all Enterprise Service Bus (ESB) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
