Try our new research platform with insights from 80,000+ expert users
Software Engineer at a tech services company with 51-200 employees
Real User
Easy connectivity which allows for fast integration; lacking some connectors
Pros and Cons
  • "Easy connectivity and easy integration."
  • "Lacking some connectors that could be included."

What is our primary use case?

I used the free trial account to test the product, it allows 10 days free trial.  

I'm a software engineer and a user of Mule ESB

What is most valuable?

The best feature for me was the easy connectivity and easy integration. In comparison, if you go through code license for APN, it will require more configuration or more code but if you're going to Anypoint Studio and using Mule ESB, you just drag and drop the connectors, configure the credentials and complete your process as per your requirements. The product helps me a lot to integrate quickly. 

What needs improvement?

I think there are some connectors that are not available that should be included. Supports like Salesforce Connector that are available in APN could be included. It's possible that this requires more configuration in our system. I've also found that running Mule Anypoint Studio ESB can slow things down. 

They have good documentation but it's better to have a video explanation for some of the demos, something basic that runs for 10 minutes or so. If you have that and combine it with the documentation, it would simplify the learning process. 

For how long have I used the solution?

I have used the solution for one year. Really helpful tool for integration with multiple system.

Buyer's Guide
Mule ESB
November 2024
Learn what your peers think about Mule ESB. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.

What do I think about the stability of the solution?

This is a stable solution.

What do I think about the scalability of the solution?

The solution is scalable.

How are customer service and support?

I haven't used technical support, I tend to check the documentation when there are problems. It's actually quite good. There is a video which explains integration in only three minutes, and that helped me understand the documents.

How was the initial setup?

I used some of the notes and YouTube tutorials that explain the setup. They've simplified the process with the latest version which is a good thing. 

Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
Developer JAVA/JEE, Mule ESB at a computer software company with 11-50 employees
Real User
Integrates well with Salesforce, but needs support for more datatypes and file formats
Pros and Cons
  • "The most valuable feature is the Salesforce integration."
  • "The Anypoint platform consumes a lot of memory, and it would be great for developers if it were more lightweight."

What is our primary use case?

We use Salesforce to store the most valuable information in our system. We have many clients that request this data, and we send it to them using the Mule ESB solution.

What is most valuable?

The most valuable feature is the Salesforce integration.

The drag and drop feature makes it very easy for transformation, and to use the Anypoint platform.

It is very easy to manage the flow using Anypoint.

What needs improvement?

I would like to see the transformation component improved such that they can support the integration of more datatypes. For example, in version 3.7 they do not support the Excel format, and some companies using that version cannot do transformation with Excel input. As a workaround, they have to manually write Java code to do it.

The Anypoint platform consumes a lot of memory, and it would be great for developers if it were more lightweight.

It would be great if they extended the free trial of the API designer to two months.

For how long have I used the solution?

Four years.

What do I think about the stability of the solution?

The version that I am using, 3.8, is quite stable. My understanding of version 4 is that it is not stable, yet, because it is new, and it will take some time.

What do I think about the scalability of the solution?

This solution is very scalable, and we can use it however we like. It can connect to every kind of system.

There are approximately two hundred people using the system, directly and indirectly.

How are customer service and technical support?

We have used technical support for some issues that we could not figure out by ourselves. They are fast and don't take a long time to respond.

Which solution did I use previously and why did I switch?

We started with Mule ESB.

How was the initial setup?

The Anypoint platform is based on Eclipse, so anyone who has worked in Java will find it easy.

What about the implementation team?

I performed the installation myself.

What's my experience with pricing, setup cost, and licensing?

The various features and components for this solution are no longer free.

What other advice do I have?

I will soon be migrating to version 4 of Mule ESB, although we are also interested in the WSO2 solution because it seems to be very complete.

Using Mule ESB does not require somebody to be a Java developer, although there are some Java concepts that you need to know. For example, some people use JSON, and I find that they are scared of Mule ESB because it is based on Java. But really, it isn't a problem if they don't know it.

This solution has good performance and support, but not everybody can use it because many of the features are expensive. Especially for application management, it is expensive compared to solutions such as WSO2. It is limiting for small and medium-sized companies.

I would rate this solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Mule ESB
November 2024
Learn what your peers think about Mule ESB. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
it_user647418 - PeerSpot reviewer
Senior IT Consultant at a tech services company with 11-50 employees
Consultant
There are already defined endpoint components such as HTTP, JMS, and FTP.

What is most valuable?

There are many already defined endpoint components such as HTTP, JMS, FTP, etc., and these are the main tools for communicating with various services. By having these, developers just need to concentrate on the functionalities instead of making modules to talk to other services.

How has it helped my organization?

I am not sure about how it has improved the way my organization functions but certainly with regard to simple integration, development speed is faster than writing from scratch.

What needs improvement?

The HTTP request connector should have the ability to change the hostname on the fly instead of the URL endpoint only.

For how long have I used the solution?

I've used this product for eight years from Mule v3.0 to v3.8.

What do I think about the stability of the solution?

We had an issue in v3.4 with clustering but as of v3.7, MuleSoft has fixed the problem.

What do I think about the scalability of the solution?

Scalability depends on how an application using Mule ESB is designed and so far, we haven't had any issues with the scalability.

How is customer service and technical support?

The technical support is OK and I've never really needed it.

How was the initial setup?

The setup is straightforward in terms of deployment and environment setup.
Just download the "mule-esb runtime environment" zip file and unzip under a particular directory. Then a Mule setup is done. To deploy an application, just drop a Mule app into ${MULE_HOME}/apps along with the properties file under class path, then done.

What's my experience with pricing, setup cost, and licensing?

It is getting expensive and I recommend clients to use Camel ESB if enterprise support is not required.

If a cluster is not required, then just buy the non-clustered version.

Which other solutions did I evaluate?

I've been in a consultancy environment for a long time and knew various frameworks and tools already.

What other advice do I have?

Make an architectural plan in depth before implementing a solution based on this product. Otherwise, it might cost far more than expected.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Information System Architect at Astvision
Real User
User-friendly, reliable, and online information available
Pros and Cons
  • "Mule ESB is a very easy-to-use and user-friendly solution."
  • "There are some features on the commercial version of the solution that would be great if they were on the community version. Additionally, if they added more authorization features it would be helpful."

What is our primary use case?

I use Mule ESB to exchange data between four or five systems at one time. We exchange government organizations' data.

What is most valuable?

Mule ESB is a very easy-to-use and user-friendly solution.

What needs improvement?

There are some features on the commercial version of the solution that would be great if they were on the community version. Additionally, if they added more authorization features it would be helpful.

For how long have I used the solution?

I have been using Mule ESB for approximately two years.

What do I think about the stability of the solution?

The stability of Mule ESB is very good.

What do I think about the scalability of the solution?

Mule ESB is a highly scalable solution.

I am the only one using Mule ESB in my organization and I use it daily.

How are customer service and support?

The community version of Mule ESB does not have support. I  find information online if I need it.

Which solution did I use previously and why did I switch?

I was previously using Talend ESB but it's more complex than Mule ESB to use. The commercial versions have more features than Talend ESB.

How was the initial setup?

Mule ESB was very easy to set up. I did three months of testing Mule ESB before I went into production.

What about the implementation team?

I did the implementation of Mule ESB myself. There is no maintenance required for Mule ESB.

What's my experience with pricing, setup cost, and licensing?

The price of the Mule ESB commercial version is expensive. However, they have a free community version.

What other advice do I have?

I recommend this solution to others. If you have any data exchanges with other systems, Mule ESB is very useful and easy to use, even if it's the commercial version.

I rate Mule ESB a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
FranciscoSantos - PeerSpot reviewer
Director at Pixel Studio PTY
Real User
Top 5
Programmer-friendly solution that offers good value for money
Pros and Cons
  • "The most valuable feature is that it's programmer-friendly, so it's very easy to develop APIs."
  • "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."

What is our primary use case?

My primary uses are asset maintenance and data management.

What is most valuable?

The most valuable feature is that it's programmer-friendly, so it's very easy to develop APIs.

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

For how long have I used the solution?

I've been using this solution for almost three years.

What do I think about the stability of the solution?

It's very stable and reliable.

What do I think about the scalability of the solution?

This solution is scalable.

How are customer service and support?

The technical support is reliable and quick to resolve any block we have.

How was the initial setup?

The initial setup is straightforward and only takes a day, but it looks at many data sources, so you have to be specific about what you need. 

What's my experience with pricing, setup cost, and licensing?

This product is expensive, but it does offer value for money.

What other advice do I have?

I would give this product a rating of ten out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer833937 - PeerSpot reviewer
Consultant, Architecture and Standards at a tech services company with 51-200 employees
Consultant
Good data transformation and formatting features, but it is not easy to troubleshoot
Pros and Cons
  • "The transformation and the data format are the features that I like the most."
  • "It's not easy to troubleshoot and we still can't make it work."

What is our primary use case?

It's used for regional implementation, where several systems are integrated and contributing to a central on-premises system.

What is most valuable?

The transformation and the data format are the features that I like the most.

What needs improvement?

There are several areas that need improvement. It's not easy to troubleshoot and we still can't make it work. It starts then stops. We are still trying to make it work using other tools that we have in-house, such as Kubernetes. So far, we have not found the proper way to connect them.

Stability is an issue as well as scalability. Both of these need improvement.

Pricing is always an area that can be improved. It's everyone's wish.

For how long have I used the solution?

I have been using Mule ESB for five years.

What do I think about the stability of the solution?

It starts and stops, so we haven't had a chance to test it in production.

How are customer service and technical support?

We have not reached out to technical support. Our case was so complex that we had to reach out to the architect to come on-site and help us with it here. This type of support is definitely expensive.

How was the initial setup?

The initial setup was complex.

Deployment took a week. We were waiting for the team to be onsite.

What about the implementation team?

We had a team from Mulesoft to help us.

What's my experience with pricing, setup cost, and licensing?

The licensing is yearly, and there are additional fees for services. For example, having the help of the architect was a separate fee.

What other advice do I have?

It's definitely allowed us to develop everything but we are stuck in testing. It works then it stops working, and now we are trying to figure out why. It's not related to the software but related to the teams that work with it. It's a new technology for us.

I am still trying to discover the benefits. I know that it has many connectors, that it's a tool to integrate with Salesforce. That's when they say we cannot do what we need to without MuleSoft. We didn't use it for that purpose. For our purposes, custom integration as ESB, we are still trying to discover where our benefits are. I don't have a good idea yet.

We were able to develop what we were planning to. It's highly configurable. We were able to configure the workflows and orchestrations, but we are not able to run it yet.

I don't want to give people the wrong impression because of my experience so far because it may not be an accurate one. It may not be the fault of the solution.

When I worked with IBM in the past, it was easier.

Due to the complexities, I would rate MuleSoft a six out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Developer at a tech services company with 1,001-5,000 employees
Real User
Powerful data transformation technology, but it needs to be more user-friendly
Pros and Cons
  • "The most powerful feature is DataWeave, which is a powerful language where data can be transformed from one form into another."
  • "I would like to see support for BPM in the next release of this solution."

What is our primary use case?

Our primary use for this solution is API driven related management and lightweight message processing.

What is most valuable?

The most powerful feature is DataWeave, which is a powerful language where data can be transformed from one form into another. 

What needs improvement?

This solution could be improved by making it more flexible, and more user-friendly.

I would like to see support for BPM in the next release of this solution.

For how long have I used the solution?

One year.

What do I think about the stability of the solution?

This solution is very good, and it is stable.

What do I think about the scalability of the solution?

In terms of scalability, it is very good.

How are customer service and technical support?

Technical support for this solution is very good, and very interactive. If I have any questions then I reach out to them and they respond very quickly.

Which solution did I use previously and why did I switch?

We were using a variety of technologies, but we use this solution because it is a very lightweight message processing system.

How was the initial setup?

I would say that this initial setup was moderate.

What about the implementation team?

Our DevOps handled the implementation.

Which other solutions did I evaluate?

We looked at other options, but this one is what our vendor recommended.

What other advice do I have?

I would rate this solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user641259 - PeerSpot reviewer
Co Founder & Principal Architect at a tech vendor with 1-10 employees
Vendor
Some of the valuable features are parallel processing support and integration with other products.

What is most valuable?

  • Salesforce connector
  • Enterprise JDBC
  • SAP connector and other connectors like FTP and SFTP
  • Parallel processing support
  • JMS integration

How has it helped my organization?

We are a technology consulting company specialized in Systems Integration using Mule ESB. (www.app-integrators.com)

Through App Integrators, we have integrated disparate Enterprise Applications for different customers across the globe. Most of our integrations for clients are:

  • Hybrid Integration Model: On-premises and cloud based applications
  • Large volume data handling: Handled batch applications supporting up to 20 million records to Salesforce.
  • Support for Enterprise Batch Applications: We have used Mule ESB for running 120 batch applications on different scheduled intervals.
  • SAP based Integrations with manufacturing systems

What needs improvement?

  • SOA governance of ESB
  • Versioning and exception handling
  • Easier development
  • Documentation/good design guidelines are not sufficient

For how long have I used the solution?

I have used this solution since 2012.

What do I think about the stability of the solution?

There were stability issues. It is very complex to set up an Enterprise grade application and it is not easy to use.

What do I think about the scalability of the solution?

Like a typical Java application, one should know how to tune a Java based server.

However, we have experienced issues when handling massive volumes of 20 million records to Salesforce (from on premises systems). We also experienced issues when we executed batch jobs of up to 120 jobs in a cluster of Mule ESB instances and when handling large volume of data (in the millions).

Nevertheless, many connectors like Enterprise JDBC and DataWeave support the streaming of data.

How are customer service and technical support?

Technical support has been excellent. They are very helpful through their customer support tool and/or through their forums.

Which solution did I use previously and why did I switch?

We used Oracle OSB before and some of our clients used TIBCO middleware or Java CAPS.

But we suggested that clients switch to Mule ESB due to:

  • The lower licensing cost
  • The availability of cloud connectors
  • CloudHub platform (supporting iPaaS)
  • A suite of 110+ connectors to use.

How was the initial setup?

It is complex to set up because any Enterprise grade middleware needs hardening. This is why we need to set up clusters, integrate with source control tools for continuous integration in different environments like DEV, QA, TEST, and also consider firewalls and internet security.

So other than a DEV Server, the setup is not straightforward. It depends on the organization security/development methodologies and policies.

What's my experience with pricing, setup cost, and licensing?

It is cheaper than competitors in pricing and licensing. We have an open source option available as well.

Most of the licenses can be added as entitlements on top of a basic Enterprise license. Licenses are renewed every year and there is no perpetual license.

Which other solutions did I evaluate?

We evaluated Oracle ESB, Apache Camel, and ServiceMix.

What other advice do I have?

I would recommend this solution due to its support for multiple integration options.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Mule ESB Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2024
Buyer's Guide
Download our free Mule ESB Report and get advice and tips from experienced pros sharing their opinions.