Mule ESB vs WSO2 Enterprise Integrator vs webMethods.io comparison

"Most of our use cases are for Salesforce. So, the connectors for Salesforce have been really helpful. They've made development two times faster."

"I like that it's user-friendly. Compared to other ESBs, I find it easier to use. I like it better than other ESBs. I like the connectors, which make calling the APIs through the routers easier."

"The most powerful feature is DataWeave, which is a powerful language where data can be transformed from one form into another."

"The cloud and integration abilities are most useful allowing us to use applications such as Salesforce and DataWeave."

"Mule ESB is a very easy-to-use and user-friendly solution."

"The transformation and the data format are the features that I like the most."

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

"The product is very stable."

"Application integrations are offered out-of-the-box, and that is extremely important to us. This is one of the main use cases that we have for it. It is about 60 to 70 percent of the workload in our application today."

"Segregation of deployment for the environments is the most valuable feature of the solution."

"The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation."

"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."

"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."

"The product is powerful, straightforward, and easy to use."

"The product is very stable."

"The most valuable feature of the webMethods Integration Server is its reliability. It has a lot of great documentation from the service providers. Additionally, it is easy to use."

"The solution basically conforms to our standards."

"It was mostly easy to set up the product."

"The stability is excellent."

"The drag-and-drop features for connectors are very valuable."

"The solution's customer service is good."

"It's a very complete product. It allows us to network security and add more layers of security to the system."

"The productivity is the most valuable feature. It is very easy to write remediations."

"The learning curve for this solution is very good."

"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."

"The current version will not be supported for much longer."

"The solution isn't as stable as we'd like it to be. There are some ongoing issues and therefore Mule has to provide frequent patches. Mule's core IP should be more stable overall."

"The price of Mule ESB could improve."

"I would like to see support for BPM in the next release of this solution."

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

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

"It needs more samples. Also, the dependency on Maven should be removed."

"Scalability and connectors to different cloud applications is lacking."

"webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience."

"​Large file handling is pretty hard comparatively to other middleware tools."

"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."

"It is quite expensive."

"The on-premises setup can be difficult."

"One area that needs improvement is the version upgrade process. Many customers I've worked with encounter challenges when transitioning from their current version, such as x or 9, to a newer version. The process is not smooth, and they must shift their entire website."

"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."

"WSO2 libraries are not mature enough. For example, if you want to integrate with Kafka using its Kafka library, it often has many bugs."

"The customization can be a bit difficult."

"There are a lot of security settings that when you apply you have to re-apply again every time you modify a setting. It is something that really needs to be enhanced."

"They should release upgrades more frequently."

"They should introduce better pricing for small companies."

"The server is very specific and it is very difficult to get experience with it."

"If I have to buy software, then it becomes expensive for me."

"I would like to see better documentation for the open-source version."

"This product is expensive, but it does offer value for money."

"The pricing must be improved."

"Regarding licensing and pricing, I find it somewhat flexible. They are more flexible with larger customers compared to small and medium ones, as their licensing model depends on ports and other factors. Large customers benefit from more flexibility in implementation and renewal compared to smaller ones."

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

"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."

"The various features and components for this solution are no longer free."

"Mule ESB is an expensive solution."

"The solution is expensive."

"Initialy good pricing and good, if it comes to Enterprise license agreements."

"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."

"Some who consider this solution often avoid it due to its high price."

"webMethods Trading Networks is a bit costly compared to others solutions."

"I would like to see better pricing for the license."

"webMethods.io Integration's pricing is high and has yearly subscription costs."

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

"It is a cost-effective solution."

"I rate the product price a six on a scale of one to ten, where one is low price and ten is high price."

"The solution costs about 20,000 or 30,000 euros per year, per instance."

"It is a low-cost solution."

"The cost is better than IBM Cloud Pak."

"The pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."

"The open-source, unsupported version is available free of charge."