Mule ESB Reviews

We are an IT consulting company and we have built our security on Mule ESB. We work for different customers for whom we develop projects for application integration using MuleSoft.

Our use cases involve connecting backend systems like Salesforce, SAP, and other custom applications. We also expose these APIs to external customers. We have also integrated it with a system of engagement, for example, Qooper.

The most valuable feature for Mule is the number of connectors that are available. There are a lot of connectors to different systems so if you want to connect to SAP or Salesforce, there are readily available connectors that are of great help. It saves a lot of time using this system.

The level of integration that this product offers is quite far ahead of the competition.

They have a very strong developer community, interacting at an informal level on a daily basis.

MuleSoft is not so strong in method-based integration, so they're not so functional in that regard. It seems that it has not been their priority.

We have been working with this product for about a year.

No problems with stability have been brought to my attention, although once the system is in production, a different team handles it.

This product is hosted on the AWS cloud, so it has inherent scalability.

We have implemented this solution for between three and five customers in the past year. It is suitable for medium to large companies, where we have clients in each category including some that are quite big.

They have a wonderful, modern concept of community-based support. It is not a formal meeting. Rather, they often interact using technologies such as WhatsApp. They share problems and get solutions from all over the world. Surely, this is a very strong area of MuleSoft.

Some of my team members have worked on other ESB solutions in the past, but in this organization, we have not dealt with one other than MuleSoft.

One of the products that we are familiar with is a solution by IBM. This competing product is strong in terms of method-based integration.

The initial setup is very simple. The installation probably takes four hours, on average.

Our in-house teams do the implementation for our clients.

From a developer's perspective, it does not require much effort for maintenance. After we develop, the DevOps team takes it over for deployment and maintenance. When it comes to issues in production, my team would not be responsible.

I would rate this solution an eight out of ten.

We use the solution to create integration with different systems. 

I am impressed with the product's connectors and scalability. 

The solution's setup needs to be a bit more straightforward and its support needs to respond faster. 

I have been working with the product for three years. 

I would rate the solution's stability a nine out of ten.

I would rate the solution's scalability a nine out of ten. We have a few hundred users for the product. 

I would rate the solution's setup a six out of ten and took around three to four days to complete. 

I would rate the product's pricing a nine out of ten. It is a pricy solution. 

I would rate the solution an eight out of ten. The solution is a good and stable product with great community support.

We use Mule ESB to integrate different products like SAP and Salesforce. We also use it to transform data and communicate it in different versions. 

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 initial setup could be more straightforward.

I have used Mule ESB for about a year and a half.

Mule ESB is better than Oracle.

The initial setup is complex because of the Maven part.

On a scale from one to ten, I would give Mule ESB an eight.

We use this solution for payment integration. We are customers of Mule ESC and I'm a co-founder and the data engineer head.

The solution has helped us to develop more quickly and improve our time to market. 

I like the graphical interface and the number of connectors. The solution is easy to maintain. 

I'd like to see more attention given to the community editions.  

I've been using this solution for 10 years. 

The solution is scalable and stable. 

The initial setup wasn't that complex, we did it ourselves.

We're using the open-source version. 

I rate the solution nine out of 10. 

In order of importance:

- Connectors

- Data Weave

- Mule Expression Language

It has changed our approach towards integration, making plumbing functions such as HTTP/Messaging listener services, data transformation and connection handling redundant.

Documentation is cryptic, product releases are far too frequent, and upgrades become troublesome.

1 year as a developer and architect.

Deployment of custom flows is troublesome and fraught with difficulty

DataWeave: It allows for complex mappings using a simple DSL (Domain Specific Language).

Integration between systems can often take several days. However, with MuleSoft ESB, it can take as little as fifteen minutes.

The CloudHub offering requires some time to mature. However, it is a good overall solution.

Some further details:

1. The AnypointMQ offering is not very stable, as such can cause issues
when dealing with high volume burst messages.

2. The CloudHub offering is EC2 instance based and does not run in
containers.

3. The speed of the CloudHub user interface is poor.

4. Deployment takes several minutes (due to Ec2 architecture as opposed to
containerization).

5. There is currently no cross application object store.

I have used MuleSoft ESB for six years.

CloudHub stability has been an issue. However, this is being worked on.

The product scales very well.

Technical support is superb. The engineers that support customers are Java developers and have a deep understanding of the issues and resolutions. This is one of the biggest selling points for MuleSoft.

Previously, we used Apache Camel and Spring Integration. However, they require more technical involvement than MuleSoft ESB.

The setup is done with a simple deployable .zip file. It is very simple to set up and run.

Pricing is tailored to the customer. As such, I would recommend speaking with your account representative.

We evaluated Dell Boomi, Informatica, and Talend. However, for the given use case, MuleSoft came out on top.

Focus on the business problem you want to solve, as the technical integration in MuleSoft is relatively simple.

• API integration with many backend systems, deployment options, testing. 
• It helps me to manage API as well.

• For API creation and integrations in agile mode.
• Reduces the development cost and time as we work in agile mode.

Connectors: It has many connectors and components that really help to complete the development very quickly.

• Support, and with respect to licensing cost.
• Many of the customers feel that the licensing cost is much.

• Service Mediation: This is an abstraction layer in between the service consumer and the service provider.
• Message Routing: This feature consumes messages. It filters, enriches, and performs necessary operations on a message. It redirects them to the appropriate target endpoint, based on a certain decision making criterion.
• Data Transformation: The process of converting/transforming data or information from one format to another.

I am providing the service for MuleSoft ESB. My company has delivered solutions such as travel portals, retailer engines, application integration, and a wide range of other scenarios, where ESB can be utilized.

MuleSoft ESB is a wonderful product. However, in order to help the developers utilize it extensively, I would suggest adding some scenario-based and audio-visual tutorials.

I have been using this solution for four years.

I am working on a number of open-source integration platforms and MuleSoft ESB is an ideal choice for us. This tool makes it easier for the developers to deliver complex projects with the best quality.

The initial/basic setup for the development and production environments was fairly easy and straightforward. For complex requirements, you may need some assistance from the experts.

I am working on frameworks/solutions such as Red Hat JBoss Fuse, Spring Integration, Apache Camel, and Apache ServiceMix.