Most Helpful Review
Find out what your peers are saying about Mule ESB vs. webMethods Integration Server and other solutions. Updated: July 2019.
354,017 professionals have used our research since 2012.
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
The most valuable feature of Mule ESB is data transformation, i.e. our interacting with different systems and orchestrating for our business needs.
Once it is started, we don't see any problems on a day to day basis.
The most powerful feature is DataWeave, which is a powerful language where data can be transformed from one form into another.
The most valuable feature is the Salesforce integration.
The architecture based on events has several connectors which allow integration from external and internal applications of the company.
Scalability and load balancing.
We can use Java expressions anywhere in the flow.
Mule Expression Language
A product with good API and EDI components.
We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting.
It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine).
We have a reusable code that we can replicate for any new interfaces.
The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging.
The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)
Application integration, business process integration, and B2B partner integration are valuable. But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed.
I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well.
Mule ESB is more into the latest REST APIs, not much into the SOAP web services. Developing is all about web services and not easy with Mule.
We would like to have a built-in logging framework in which we can do auditing.
I would like to see support for BPM in the next release of this solution.
The Anypoint platform consumes a lot of memory, and it would be great for developers if it were more lightweight.
The payment system needs improvement.
Limitation on external subscribers to listen to the messages on the bus.
It needs more samples. Also, the dependency on Maven should be removed.
Documentation is cryptic, product releases are far too frequent, and upgrades become troublesome.
The interface needs some work. It is not very user-friendly.
We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics.
t doesn't represent OOP very well, just a method and proprietary interface called IData.
We got the product via a reseller, and the support from the reseller has been less than desirable.
Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion.
When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods.
The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that.
The product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution.
Pricing and Cost Advice
The various features and components for this solution are no longer free.
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.
It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one.
Some of the licensing is "component-ized," which is confusing to new users/customers.
Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client.
Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials.
out of 24 in ESB
Average Words per Review
out of 24 in ESB
Average Words per Review
Compared 24% of the time.
Compared 22% of the time.
Compared 11% of the time.
Compared 35% of the time.
Compared 8% of the time.
Compared 6% of the time.
|For companies looking to modernize and unlock the value of existing on-premises systems and applications, an enterprise service bus (ESB) architecture serves as a critical foundation layer for SOA. When deployed as an ESB, the Mule runtime engine of Anypoint Platform combines the power of data and application integration across legacy systems and SaaS applications, with a seamless path to the other capabilities of Anypoint Platform and the full power of API-led connectivity.|
The award-winning webMethods Integration Server, our Enterprise Service Bus (ESB), is a complete enterprise application integration solution. It's standards-based so it "speaks" any technology. You can integrate any technology from any vendor: ERP systems, databases, mainframes and legacy apps. SaaS platforms, Web services, JMS messaging systems and packaged apps.
Learn more about Mule ESB
Learn more about webMethods Integration Server
|Ube, PacificComp, University of Witwatersrand, Justice Systems, Camelot||Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt|
Financial Services Firm27%
Financial Services Firm14%