Try our new research platform with insights from 80,000+ expert users

Mule ESB vs OpenText Trading Grid comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Mule ESB
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
50
Ranking in other categories
Enterprise Service Bus (ESB) (2nd)
OpenText Trading Grid
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
1
Ranking in other categories
Business-to-Business Middleware (12th), Cloud Data Integration (36th), Integration Platform as a Service (iPaaS) (19th)
 

Mindshare comparison

While both are Application Integration solutions, they serve different purposes. Mule ESB is designed for Enterprise Service Bus (ESB) and holds a mindshare of 20.1%, down 22.3% compared to last year.
OpenText Trading Grid, on the other hand, focuses on Business-to-Business Middleware, holds 4.2% mindshare, up 3.9% since last year.
Enterprise Service Bus (ESB)
Business-to-Business Middleware
 

Featured Reviews

PurbayanSaha - PeerSpot reviewer
Has API-led architecture and provides a unique, user-friendly, and scalable architecture for hosting APIs
There's room for improvement in multi-file transfer functionality. It's not convenient when using MuleSoft, and it should have better capability for handling large amounts of data. For example, applications like GoAnywhere can handle huge chunks of data, so the tool should also have something to facilitate that aspect of integration.
VARUNKUMAR - PeerSpot reviewer
Industry-leading, easy to implement, and has good mapping specification guidelines
The good thing about OpenText is that we have the mapping specification guideline available, which is not there in a solution like SEEBURGER. Whenever you want to take a decision to move away from OpenText, you have already documented your mapping and what your mapping looks like. So you go to the next provider, provide them with that mapping specification, and it'll be very easy for them to develop a new map instead of just taking the data - input data, output data - and then looking for how the data is getting transformed. So you have the mapping spec level which is a very good feature of OpenText, which we do not have in SEEBURGER. It's very hard to move from SEEBURGER. The solution is easy to implement. It's stable and reliable. They are the industry leaders in the integration space.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I am impressed with the product's connectors and scalability."
"The solution doesn't require much code writing and we can develop APIs very easily."
"The most valuable feature of Mule ESB is data transformation, i.e. our interacting with different systems and orchestrating for our business needs."
"It is one of the best integration tools in the market."
"The solution's drag-and-drop interface and data viewer helped us quite a lot."
"The most beneficial features of Mule ESB are the control plane and runtime plane."
"Once it is started, we don't see any problems on a day to day basis."
"The product offers a community edition that is free of cost."
"The solution is easy to implement."
 

Cons

"The stability could be improved."
"I cannot say that installation with Kubernetes needs to be improved to be less tricky, but more information is needed from MuleSoft. They do not help much with Kubernetes, so we should have a person who is well-versed in Kubernetes to handle this."
"Improvements could be made in performance."
"Mule ESB could be more user-friendly. I think users must learn about the architecture before they start coding. The price could be better. In the next release, I would like to see an EDIFACT integration."
"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."
"From an improvement perspective, there should be fewer coding challenges for users in Mule ESB."
"There are some issues with both stability and scalability."
"In India, particularly in the banking sector, clients do not prefer cloud solutions due to regulatory and compliance requirements."
"Technical support needs to be better."
 

Pricing and Cost Advice

"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."
"Mule ESB is a costly solution. We pay approximately $80,000 annually for the system. The cost of the number of instances, annual subscription, and cloud hosting services are expensive."
"This is expensive. In my next project, we had to go to other vendor."
"I think the price is very high. If you use TIBCO BW, the license is for the CPU usage, then the IPS, and support. I also think the license for the product is a one-time expense."
"You will not get any support from Mule ESB's team for the tool's community edition...You can get support with the licensed version of Mule ESB."
"Mule ESB is an expensive solution."
"The pricing must be improved."
"The price of the Mule ESB commercial version is expensive. However, they have a free community version."
Information not available
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
855,164 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
15%
Manufacturing Company
8%
Government
6%
Computer Software Company
14%
Manufacturing Company
13%
Retailer
11%
Real Estate/Law Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Migration from IBM Integration Bus to Mulesoft ESB for a large enterprise tech services company
I was previously part of the Oracle SOA/OSB development team. In my current capacity I architected solutions using MuleSoft Anypoint Platform on cloud / on-premises and hybrid modes and on PCE/RTF ...
IBM Integration Bus vs Mule ESB - which to choose?
Our team ran a comparison of IBM’s Integration Bus vs. Mule ESB in order to determine what sort of ESB software was the best fit for our organization. Ultimately we decided to choose IBM Integratio...
What do you like most about Mule ESB?
The solution's drag-and-drop interface and data viewer helped us quite a lot.
Ask a question
Earn 20 points
 

Also Known As

No data available
Trading Grid, GXS Trading Grid
 

Overview

 

Sample Customers

Ube, PacificComp, University of Witwatersrand, Justice Systems, Camelot
Autoliv, Hella, Hutchinson, Michelin
Find out what your peers are saying about IBM, Salesforce, Oracle and others in Enterprise Service Bus (ESB). Updated: May 2025.
855,164 professionals have used our research since 2012.