Mule ESB Reviews

• Routing
• Enrichment
• DataWeave
• Choice of connectors
• Light weight containers
• Packaging and deploying
• API management
• Scalability and load balancing

• Ability to integrate disparate systems with a seamless movement of data on-premises and in the cloud
• Gives the power to make decisions and quick market penetration
• Provides the time to build and release new features
• Has Agile driven builds

• Limitation on external subscribers to listen to the messages on the bus.
• VM queues and memory/thread management need more stability.

I have been using this solution for over five years.

Not major issues but there are some rare version compatibility issues with connectors.

We did not encounter any stability issues.

No issues with scalability. Especially the Cloud deployments can scale on demand and are seamless and reliable.

Customer SLAs are one of the top priorities at MuleSoft and they have been supportive in every situation.

I found technical support to be very resourceful and experts are at hand.

We switched because this solution was found to be cost effective, freely available for community edition, and an easy transition from any programming background.

The initial setup was pretty straightforward with few easy steps.

In-house

Get your basics right about your requirements and plan ahead especially w.r.t volumes, any premium connectors to be purchased and a rough estimate on integration touch points to get some idea on the overall cost.

Plan your licensing model (cloud or on-premises or hybrid) that will allow seamless integration with new partners.

We looked at Apache Camel, Fuse ESB, Dell Boomi, and TIBCO.

Plan your use cases and set your expectations on the features that need to be implemented.

It is an ESB that can deploy seamlessly on-premises and in the cloud with strong API management and governance and has a strong integration with open source products like JBPM and Drools if these features are part of your requirements.

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. 

The most valuable features are the connectors, DataWeave, and the way it simplifies the application development and deployable files.

Connectors:

• Being a Java developer, I have experienced how much logic and coding one needs to put in while accessing the database.
• With the DB Connectors developer, I just need to place the query, and in some cases the drivers, if Mule doesn't provide out-of-the-box support.
• With the HTTP Connector and the APIkit router with RAML, managing the resources and handling is made easy.
• With Mule's expected release in Q3 of 2017, generating RAML would also be made easy.

DataWeave:

• With good knowledge of DataWeave operators, anything can be achieved in a couple of lines of code, which otherwise would be time consuming in Java.

It has reduced interdependency.

The Mule IDE (Integrated Development Environment) could be more stable. For example, in Anypoint Studio, when we add some components and then remove them, they don't get deleted from XML in the background. It gives a duplicate error when we try to add them another time. However, this has been fixed with Anypoint Studio 6.

I have used this solution for around a year.

The older versions of Mule IDE, Anypoint Studio 5.x.x are more unstable.

There were no scalability issues.

I would give technical support a rating of 4.5/5.

The setup was pretty straightforward.

This is an affordable product.

Since most organizations are now going digital and opening up their resources via APIs, companies should explore using this solution.

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

I use ESB to do integrations for a company called Pelindo. Pelindo is a company that's a terminal operator. They are involved in logistics, have many partners, and require transaction detection and a payment gateway.

I like that Mule ESB provides fast and good technical support.

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.

I have been using Mule ESB since 2013, so nine years. 

Mule ESB is stable, but sometimes the traffic is unstable because the transaction rate increases and the server is obsolete.

Technical support is fast and good.

Positive

I think the initial setup was straightforward.

I have experience installing this solution for my company. I can also maintain  Mule ESB by myself.

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. 

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

We implemented the Mule solution for our orchestration. We use it to follow up with the customer so the online order gets orchestrated to the target automated system.

The features that I have found most valuable are that the product is updated regularly and Mule's framework. Overall the performance is good.

For our current solution, I think what Mule provides out-of-box is a sufficient product.

As for what can be improved, in my experience the SMPT connectors need some improvement. 

It definitely takes some amount of integration knowledge but it is still pretty easy to learn. But I would request that the documentation be more informative. That would help the development community to understand the solution better, to deal with whatever challenges they face and ensure they'll be able to solve them on their own. 

The integrations are complicated so maybe that aspect of the solution should also be made simpler to use so that it wouldn't require such experienced resources to build a more complex integration.

Additionally, there are limitations with the subscription model that comes with the product. If you subscribe to the platinum subscription, you get more benefits. Now there are limitations in keeping the logs and the ability to handle the max of 30 days. They could improve that.

Lastly, they could provide us a bit more coding features.

I have been using Mule ESB for past one and a half years.

In terms of stability, we did found some bugs which we reported to Mule support, but overall I would say it's good.

Mule ESB's scalability is pretty good. It performs well.

In terms of numbers of people using the solution, actually Mule ESB plays an integrated role, so none of the users directly use it. But otherwise if you ask the production team and the development team, I would say close to 20 members are using this platform.

We definitely plan on increasing usage for Mule ESB because our customer is starting to do more AP's on the platform.

I think customer support is good. The support team responds to us, but due to some challenges in the product core, we are still waiting for them to respond to some issues.

The initial setup was straightforward.

I know that the setup is straightforward, but I did not do it myself. One person from our team did it. Everything is straightforward and pretty easy, including the deployment and the promotion from one level to another level.

I would definitely recommend Mule ESB for others to evaluate when they are choosing a product.

On a scale of one to ten, I would definitely rate Mule ESB an eight.

For it to be a higher rating they would need to improve the recording logs and encoding feature.

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.