We performed a comparison between Mule ESB and SEEBURGER Business Integration Suite 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)."The most valuable feature for Mule is the number of connectors that are available."
"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 solution offers multiple deployment options."
"Everything runs in Java, which is a useful feature."
"The cloud and integration abilities are most useful allowing us to use applications such as Salesforce and DataWeave."
"The architecture based on events has several connectors which allow integration from external and internal applications of the company."
"Mule Expression Language"
"The solution has a good graphical interface."
"SEEBURGER Business Integration Suite (BIS) has been good at communicating between two applications, changing formats and using the required protocols... We can have one site communicating in an old FTP or SFTP style, or via file transfer. And with other applications, we could have API or a web service call or some other protocol used to send information."
"Mapping Designer provides excellent flexibility."
"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."
"It is stable and reliable. We have not had any issues."
"The platform has been very consistent and responsive."
"We use Message Tracking, which is a very good feature. Message Tracking has about 300 to 400 business people who can find documents and ask the integration team about them. For example, they looking for a document that the vendor or trading partner tells them that they sent, but they don't see it in the ERP system yet. So, they go to SEEBURGER Message Tracking, which can tell them if we received it already from the outside and what happened, e.g., if it went to SEEBURGER BIS or if it's already in the ERP system. It's a very simple tool to use. They also can use that tool to see the source document."
"Among the most important [features] are the BIC 6 Converter and the communication protocols, which have the newer security features for certificates and encryption."
"We can code in Java, which is really good feature. There is very vast command available, which can be used in mapping."
"Mule ESB isn't as secure as IBM. Financial companies go with IBM for that reason."
"From the product perspective, it was sometimes hard to manage the dependencies. When we had to add dependencies on a couple of different packages, it was sometimes confusing. It was hard to update them with Anypoint Studio, as well as with MuleSoft. There were challenges with that. So, that's one of the areas that could be improved."
"The initial setup could be more straightforward."
"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."
"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 would be beneficial if users could navigate the UI easily without extensive training or learning curves."
"Limitation on external subscribers to listen to the messages on the bus."
"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 BIS Front End needs a little bit of refreshing, especially when it comes to setting up new trading partners and trading partner agreements or transactions. It can be a bit clumsy to copy and rename and then go in and modify."
"Some of the functionality for retriggering documents, where you have to step through a termination process and then retrigger it, versus just being able to restart or retrigger more easily, is a bit challenging, depending on the scenario."
"They have their own private cloud. That's the reason we did not go ahead with managing everything by ourselves or moving into the cloud. They said that they're going to be doing it within the next two years, having access to Azure and AWS. That would be something we would like to see."
"We occasionally get ZIP files. Sometimes the ZIP file has one file inside of it, and sometimes the ZIP file might have 30 files inside of it. We have been working with SEEBURGER to enhance their PKUNZIP process to be able to unzip multiple files in a single workflow instead of just one file. This is still something that is in process."
"We are a little locked in with understanding the errors that we receive. We are working with their support to prevent these issues when they come into the database. We use a SQL database and believe they can do better when it comes working with large databases. We have had few instances where the system is hanging, which are most likely from the database. We are working with their support to find out the problem and fix their system. We have tried to use their notification system to prevent these issues, but they need to improve their monitoring system."
"The initial set up was done by SEEBURGER consulting. It can be complex due to various factors, such as server settings, database settings, and security settings."
"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."
"Java is very old technology and they should move away from it, to anything that's better."
More SEEBURGER Business Integration Suite Pricing and Cost Advice →
Mule ESB is ranked 2nd in Enterprise Service Bus (ESB) with 46 reviews while SEEBURGER Business Integration Suite is ranked 5th in Business-to-Business Middleware with 37 reviews. Mule ESB is rated 8.0, while SEEBURGER Business Integration Suite is rated 8.4. The top reviewer of Mule ESB writes "Plenty of documentation, flexible, and reliable". On the other hand, the top reviewer of SEEBURGER Business Integration Suite writes "Gives us the flexibility to hook up to systems using any protocol out there". Mule ESB is most compared with IBM Integration Bus, Oracle Service Bus, Oracle SOA Suite, webMethods Integration Server and TIBCO ActiveMatrix Service Bus, whereas SEEBURGER Business Integration Suite is most compared with SAP Cloud Platform, IBM Sterling B2B Integration Services, IBM B2B Integrator, Microsoft Azure API Management and OpenText Trading Grid.
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.
