We performed a comparison between Mule ESB, SEEBURGER Business Integration Suite, and webMethods Integration Server 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).
"Mule ESB is a very easy-to-use and user-friendly solution."
"Everything runs in Java, which is a useful feature."
"I am impressed with the product's connectors and scalability."
"The transformation and the data format are the features that I like the most."
"The most valuable feature of Mule ESB is data transformation, i.e. our interacting with different systems and orchestrating for our business needs."
"We can use Java expressions anywhere in the flow."
"The cloud and integration abilities are most useful allowing us to use applications such as Salesforce and DataWeave."
"The product offers a community edition that is free of cost."
"SEEBURGER has helped us to enable digital business transformation. Every time we add a new customer, there is a digital footprint. This is no longer a manual process."
"The stability is world-class. It is as good as any of the other options out there. They have addressed hiccups quickly, professionally, and with an excellent response."
"What would have been a manual process of transmitting data items around between us and third-parties has been automated. SEEBURGER BIS handles the automation and mapping side of the communications. The automation, along with the efficiency around time and cost, has improved our organization. Around 20,000 messages a month have been automated. These typically would be financial/order transactions and confirmations in invoicing that have been automated."
"In our landscape, we have a lot of AS/400s or iSeries and SEEBURGER Business Integration Suite (BIS) has a file service listener that allows data to seamlessly be transferred between the SEEBURGER solution and the AS/400."
"When orders come in they go into our ERP system directly, so there is integration there."
"The solution's capabilities in fulfilling our existing B2B integration requirements are brilliant. Among our multiple customers we connect to SAP systems, JDE, all the various ERPs that you can possibly get, Oracle procurement systems, etc. We haven't come across anything yet — and customers are trying to trip us up — that we can't do."
"The platform has been very consistent and responsive."
"The solution helps us automate processes, more on the insurance side. Where they used to have to babysit monthly files, because of size, they don't have to do that with SEEBURGER BIS. They just run the monthly process. Files get collected, translated, and sent to the proper systems, so the babysitting is gone."
"The messaging part is the most valuable feature."
"webMethods platform is used to build an EAI platform, enabling communication between many internal systems and third-party operators."
"High throughput and excellent scalability."
"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."
"webMethods Integration Server is an easy-to-use solution and does not require a lot of coding."
"It's very flexible and a good platform to use."
"Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine. We've had a really good experience with webMethods Integration Server."
"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."
"Community editions need more attention."
"From an improvement perspective, there should be fewer coding challenges for users in Mule ESB."
"The payment system needs improvement."
"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."
"Mule ESB isn't as secure as IBM. Financial companies go with IBM for that reason."
"MuleSoft is not so strong in method-based integration, so they're not so functional in that regard."
"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."
"Lacking some connectors that could be included."
"We don't have much access to the logs or what's happening. So we have to log a ticket with SEEBURGER. We only get a message that something has failed... we have to open a ticket with SEEBURGER for them to tell us exactly what the issue is... I would like us to be able to be more self-sufficient."
"There are a lot of service packs during the year. I know that part is the process for updating features, but sometimes it's difficult to update service packs every month."
"We wanted to use API. We were told that in 6.52 we could use API management. Later on, we found that API management wasn't that completely integrated into the 6.52 solution, and if you wanted to have the whole API suite you might have to go to 6.7, the latest one."
"I would've liked, from day one, to learn how to do my own mapping. That would have saved a lot of time and effort if that had been brought forward earlier. It's there, I just didn't know about it. Also, some tidier, easier-to-use interfaces would help."
"Their traditional model is a vendor flow. We are looking to do a customer-based flow, which which require significant development from SEEBURGER Business Integration Suite (BIS). We are working with them to do this using their WebEDI. It is a brand new area for them, but it could be an option in the future."
"In some of the other tools out there in the market, you can create one service and use that service without creating a copy. That kind of capability currently doesn't exist in this solution."
"The speed of development needs improvement. If you acquire any customization, it can be a slightly slow process. I would like to see more flexibility around customizations. The time frame right now depends on the sophistication and customization, but we have to go through a process of getting them to develop, implement, and test it. This might take a couple of weeks. If it was a simpler system to customize, the time could probably be cut by half or down by even 25 percent of what it would normally take."
"It's rather difficult to understand, from the application, what's broken and why it doesn't work. We typically need to get support from them directly, and it's usually in a consulting role, to fix issues."
"We got the product via a reseller, and the support from the reseller has been less than desirable."
"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."
"I would like to see the price improve."
"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."
"As webMethods Integration Server is expensive, that's its area for improvement."
"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."
"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."
"Technical support is an area where they can improve."
More SEEBURGER Business Integration Suite Pricing and Cost Advice →
More webMethods Integration Server Pricing and Cost Advice →
