Vice President at a philanthropy with 1-10 employees
Real User
Scaled easily, had good ROI and time to value, and didn't require taking care of the infrastructure
Pros and Cons
  • "It was pretty fast to develop APIs on this platform, which is something I liked about it. So, the time to value was pretty good."
  • "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."

What is our primary use case?

We were using it for EDI. We were using it for integration between RFID portals and our ERP system. We were also using it for the integration of customer data between the CRM and the ERP systems. I am no longer using it because I changed the company.

We were using the cloud version.

What is most valuable?

When we bought the solution, it was an in-the-cloud or PaaS solution. Because of that, I didn't have to take care of the infrastructure, which was a big plus.

It was pretty fast to develop APIs on this platform, which is something I liked about it. So, the time to value was pretty good. 

What needs improvement?


Its licensing or pricing model should be improved. If I compare it to other solutions, it is very expensive for small and medium businesses.

Their support should also be improved. Some of the tickets took a long time to be resolved, and I had to escalate to my account manager.

For how long have I used the solution?

I used this solution for maybe five years.

Buyer's Guide
ESB (Enterprise Service Bus)
March 2024
Find out what your peers are saying about MuleSoft, IBM, Software AG and others in ESB (Enterprise Service Bus). Updated: March 2024.
765,234 professionals have used our research since 2012.

What do I think about the stability of the solution?

It is very stable.

What do I think about the scalability of the solution?

It is very scalable. It is also easily scalable.

I had about two developers internally, and they were taking care of its deployment and maintenance. In terms of the end users, it probably impacted hundreds or thousands of employees.

How are customer service and support?

It was okay. There is room for improvement. I had some tickets that were taking a long time to be resolved, and I had to escalate to my account manager to push them through. I would rate them a three out of five.

How was the initial setup?

In the latest implementation, we decided to start small with a very simple project that we had, which was customer integration between our CRM and ERP solutions. We started with a very small API. It was a small integration with only about three APIs, and that was it. We had success with it, and we ran it. 

What about the implementation team?

We did it in partnership with a third-party consultant, and then we took it from there. Our experience was very good.

What was our ROI?

Pretty good. I would rate it a four out of five.

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

Its licensing was yearly. There were minor fees additionally, but those were related to VPN's high availability. When you purchase MuleSoft, you purchase it because it is highly available. So, you have to make sure that your VPN can support that. That's pretty much it. The other tools that we picked were things to deploy the solution to build the CI/CD pipeline using MuleSoft. We picked the one that wasn't free. So, we had to pay for it, but it was a minor cost.

What other advice do I have?

They have a package to get you started. I would advise using at least a partner at the very beginning so that they can show you the best practices within MuleSoft and different layers of APIs. Sometimes, there are challenges around security and things like that. So, my advice is to get external help to get your developers started on it. Once they're taught the best practices, your intermediate to senior developers will pick it fairly quickly.

I would rate it a nine out of 10.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user

quando vemos uns com muitas habilidades 

PeerSpot user
IT Consultant at a financial services firm with 5,001-10,000 employees
Real User
Easy to implement and supports platforms like Windows, Linux, and Mac
Pros and Cons
  • "The most valuable feature of Mule ESB is data transformation, i.e. our interacting with different systems and orchestrating for our business needs."
  • "Mule ESB is more into the latest REST APIs, not much into the SOAP web services. Developing is all about web services and not easy with Mule."

What is our primary use case?

I'm a consultant in a bank in Kuwait. I suggest good products for companies that are seeking my advice.

How has it helped my organization?

One of the important features of Mule ESB as an enterprise architect is that it should be scalable. It should be customizable for different kinds of clients. 

For client A, we need only two products. For client B, I need to group one and three. The product must be customizable for each. 

The product should be able to identify who is calling and what the components are. We need to return them to the calling point. Mule ESB covers most of these requirements.

Last month, the Guardian had a post saying that Mule is one of the best products for enterprise applications.

What is most valuable?

The most valuable feature of Mule ESB is data transformation, i.e. our interacting with different systems and orchestrating for our business needs. 

For example, a customer has liabilities in loans and credit cards, maybe some other mortgages, like four liabilities which are split into four systems. 

I need to expose an API that can tune the data from four systems and expose it into one single API. For that, I have to call our services and complex security policies.

Mule ESB loads complex web service security policies. Sometimes, we have some FLAC files or maybe some messaging services. We need to consume those components and expose them as an API, which is nothing but some adjacent format, i.e. a REST API.

What needs improvement?

Technically, there are mainly two API standards. One we call SOAP and the other one is the REST API. SOAP is nothing but fully external. It's very old, but huge complex enterprise companies are still using SOAP-based web services. In the mobile smartphone era, most of the hand-held devices are using REST APIs. 

Mule ESB is more into the latest REST APIs, not much into the SOAP web services. Developing is all about web services and not easy with Mule. That is one of the disadvantages of Mule. In next-gen products, Mule is in a good position.

Normally, if you're declaring a parameter or a variable, you can have visibility until it's not operating the variable. As an architect, programmer, or developer, you know when it's available. Graphically, that's not been available until this tool appeared.

It is this kind of enhancement that I'm looking for from MuleSoft. Two weeks ago or a month back, they had a big release. With this package, they are saying that APIs are your products. 

You can sell your API to different organizations and the developers can register on their portal. It's available this fall. These are the best features I am looking for now. 

My product is an API. I need to market it through the internet. I can have my portal with all of the tools built-in. This kind of feature I didn't see with the competitors currently in the market.

For how long have I used the solution?

We have been using Mule ESB for around one year.

What do I think about the stability of the solution?

Mule ESB is very stable. I didn't face any issues. Recently I got a new version. I faced some other components issues, but not critical, i.e. easy to identify and rectify.

What do I think about the scalability of the solution?

I moved from Mule 4.1 to 4.2 and it was really easy if you are migrating only one or two applications. It's very fast. I'm doing some experiments on my workspace for around 20-25 applications. 

I'm opening all of my applications in one shot, and it is scaling for me. I didn't update them as a bulk application. I worked by importing them one by one and it was fine.

How are customer service and technical support?

I'm not into any official technical support. Their forum is pretty good and it's very active, but I cannot assure you that you will get a response within a day or two.

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

WebMethod is very expensive, but their support is awesome. I closely work with the operating technical support team. For retrieving the code from our bank, they are working with us very closely. Sometimes they are flying over here for conducting demos. 

Especially in the Middle East, MuleSoft is not doing like that. They are not doing much marketing in the industry. Maybe they are more focusing on South America or Asia. I'm not seeing much in the Middle East.

How was the initial setup?

Mule ESB is one of the best. It is easy to use and setup. You just need to install their Anypoint Studio. It's very safe for all this. It's in a good rank just for the setup.

Which other solutions did I evaluate?

We evaluated Oracle, AG webMethods, and Red Hat OpenShift. The final one was MuleSoft. I'm very impressed with MuleSoft because of the pricing and license.

You have to implement several components. Sometimes, according to your needs, you have to buy several licenses for each component. Those are the things we compared.

What other advice do I have?

My opinion is that Mule ESB depends on the business and the continuity of their enrollment. If you are a system that has not much left to repair, then your products and your APIs are assets within your organization. 

Here in the bank, we are facing different kinds of issues when we are integrating different systems:

  • We are communicating with different card carriers like Mastercard and Visa. 
  • Their standards are different according to the client requirements, i.e. exactly what kind of card they're looking for.
  • They can get the products according to their requirements as well as their budget. 

I would rate Mule ESB with 7.5 or 8 out of 10. 

  1. It's really easy to implement.
  2. It's supporting our platforms: Windows, Linux, and Mac.
  3. The performance.
  4. It's free.

I'm looking for an API platform that supports the whole technology as well as the next-gen. 

Mule ESB is lacking for self-support, self-training, and documentation. The documentation of the product is less because they're selling the training.

You have to enroll for the training, then you'll get the full documentation. If you're an advanced user, you will not get much information from the public documentation.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user1168560 - PeerSpot reviewer
it_user1168560Technical Manager at a tech services company with 1,001-5,000 employees
User

Thanks for your detailed information. This will definitely help me to make a decision between webMethods and MuleESB.

Buyer's Guide
ESB (Enterprise Service Bus)
March 2024
Find out what your peers are saying about MuleSoft, IBM, Software AG and others in ESB (Enterprise Service Bus). Updated: March 2024.
765,234 professionals have used our research since 2012.
Information System Architect at Astvision
Real User
Top 20
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
it_user1266102 - PeerSpot reviewer
Senior Architect at a tech services company with 10,001+ employees
Real User
Provides excellent connectivity but requires much better stability
Pros and Cons
  • "The connectivity the solution provides is excellent. There are often too many systems that we have to integrate and this helps with that."
  • "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."

What is our primary use case?

We primarily provide services using the Mule ESB. We use it to integrate multiple systems.

What is most valuable?

The connectivity the solution provides is excellent. There are often too many systems that we have to integrate and this helps with that.

The platform itself is very good.

What needs improvement?

I'm not sure of any areas Mule ESB needs to improve.

The price of the solution is a little bit high. It would be helpful if different sized businesses had access to different plans.

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.

For how long have I used the solution?

I've been familiar with the solution for two years.

What do I think about the stability of the solution?

We had a bit of an issue with stability when it came to running some large files. We kept getting an error. In the end, we had to divide the files and process it via multiple files because of the way we implemented them. Large file processing also seems to take up more memory.

How are customer service and technical support?

The technical support has been very good. It depends on the account we're working on, however. Good accounts get prompt responses in regards to queries.

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

We didn't previously use a different solution. We've only been working with MuleSoft.

How was the initial setup?

The initial setup was straightforward. We haven't faced any issues with implementation. They've recently simplified the processes. I recall, earlier it was not that easy to set up.

Deployment doesn't take too much time. Sometimes it can be done in minutes. It shouldn't take more than an hour.

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

I'm unsure of the licensing costs. I believe the total price is less than IBM, but it's still rather expensive.

What other advice do I have?

We're partners of MuleSoft. We provide the solution's service to our clients.

The solution would be useful for large organizations. If there are more than three or four systems, and if there is an expansion, it would work best. Small or medium enterprises with two or three systems, may find the solution a little bit unorganized.

I'd rate the solution seven out of ten. If the stability were more reliable, I'd rate it higher.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Senior Integration Consultant at a tech services company with 51-200 employees
Consultant
Provides API support and management.
Pros and Cons
  • "We can use Java expressions anywhere in the flow."
  • "It needs more samples. Also, the dependency on Maven should be removed."

What is most valuable?

  • We can use Java expressions anywhere in the flow
  • Provides API support out-of-the-box
  • API management can be done using RAML

How has it helped my organization?

It is very easy to learn and implement. We were able to meet project deadlines on time.

What needs improvement?

It needs more samples. Also, the dependency on Maven should be removed.

For how long have I used the solution?

I have used Mule ESB for one year.

What do I think about the stability of the solution?

We had issues in Munit but rarely any stability issues.

We have not had stability issues.

What do I think about the scalability of the solution?

We have not had scalability issues.

How are customer service and technical support?

Customer Service:

We had few guys from their support team.

They were excellent.

Technical Support:

I would give technical support a rating of 8/10.

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

Firstly, the project architecture team decided to go with Mule.

Secondly, the project was from scratch and we want only microservices exposed over API hence, Mule was a promising deal.

However, in my next project we weren't able to go with as it much pricier than its competitors. Actually, from all the other vendors.

How was the initial setup?

The setup was complex, as I came from a different background (IBM products). However, it became smoother down the line.

What about the implementation team?

We went for a training first and then it was in-house after that.

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

This is expensive. In my next project, we had to go to other vendor.

Apparently, this is the most expensive ESB solution out there as there is no more Community Edition.

Which other solutions did I evaluate?

We looked at IBM IB and webMethods.

What other advice do I have?

Go for it, but first read their sample exercises.

It is a one stop solution and it is an amazing product.
However,

1. It is an expensive product

2. Expensive support

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
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.

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
Tech Lead at V-Soft
MSP
Exceptional cloud features, good exception handling, and stable
Pros and Cons
  • "The cloud and integration abilities are most useful allowing us to use applications such as Salesforce and DataWeave."
  • "In an upcoming release, I would like to see more additional concept for exception handling, batch processing, and increased integration with other application."

What is our primary use case?

We normally use the API-led connectivity approach. We get the architecture and follow the basic rules and principles that Mule has.

How has it helped my organization?

We have had our research analysis team do six months of work looking into if this solution was going to benefit our organization and they determined it fit perfectly into our business. 

What is most valuable?

The cloud and integration abilities are most useful allowing us to use applications such as Salesforce and DataWeave. Additionally, the exception handling is good. We have experienced zero downtime since moving to this solution.

What needs improvement?

In an upcoming release, I would like to see more additional concept for exception handling, batch processing, and increased integration with other application.

For how long have I used the solution?

I have been using the solution for the past five years.

What do I think about the stability of the solution?

The solution is very stable we have not had any issues

What do I think about the scalability of the solution?

The scalability is good. We have a banking application running worldwide through the solution which attracts many users.

How was the initial setup?

The installation is straightforward.

What other advice do I have?

I rate Mule ESB a nine out of ten.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
Download our free ESB (Enterprise Service Bus) Report and find out what your peers are saying about MuleSoft, IBM, Software AG, and more!
Updated: March 2024
Buyer's Guide
Download our free ESB (Enterprise Service Bus) Report and find out what your peers are saying about MuleSoft, IBM, Software AG, and more!