Try our new research platform with insights from 80,000+ expert users
Chandra Manohar - PeerSpot reviewer
CTO and Head of Strategy, Technology & Innovation at Cashapona
Real User
Top 5
We utilize data transformation capabilities extensively
Pros and Cons
  • "For complex cases, we employ the SSLi engine, whereas for simpler ones like healthcare or response data, such as EDI 270 or 271. We prefer to use an external XRT engine instead of handling it within the ESB for ease of management."
  • "It would be beneficial if users could navigate the UI easily without extensive training or learning curves."

What is our primary use case?

Mule ESB excels in orchestrating workflows and seamlessly integrating with business implementations while keeping technical details hidden. It also offers protocol transformation, converting between different protocols, and supports service exposure to customers while maintaining technical invisibility.

What is most valuable?

We utilize data transformation capabilities extensively. For complex cases, we employ the SSLi engine, whereas for simpler ones like healthcare or response data, such as EDI 270 or 271. We prefer to use an external XRT engine instead of handling it within the ESB for ease of management. For smaller data transformations, we rely on DSPS.  

What needs improvement?

One notable drawback is the user experience aspect, particularly in terms of self-service functionality within Mule ESB. It would be beneficial if users could navigate the UI easily without extensive training or learning curves.

For how long have I used the solution?

I have been using Mule ESB for the last five years.

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?

The solution is generally stable. We ensure proper sizing and memory management, which helps avoid glitches and slowdowns.

What do I think about the scalability of the solution?

Mule ESB is scalable because it can be easily scaled in a cloud deployment and is containerized, making scaling up or down straightforward. This shouldn't be a major concern nowadays.

How are customer service and support?

MuleSoft's customer support is excellent.

How would you rate customer service and support?

Positive

How was the initial setup?

Setting up Mule ESB is relatively easy, although it depends on factors like account categorization and whether you're using Docker or Kubernetes. 

What about the implementation team?

Typically, installation and configuration take around three to four days initially, but subsequent deployments or updates are quicker. One engineer or developer is usually sufficient for deployment, but implementation complexity may vary based on the use case.

What was our ROI?

The ROI of Mule ESB is greatly influenced by the design and governance of the solution, particularly focusing on reusability and adherence to microservices architecture. Properly designing and implementing these aspects can significantly enhance ROI.

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

Regarding licensing and pricing, I find it somewhat flexible. They are more flexible with larger customers compared to small and medium ones, as their licensing model depends on ports and other factors. Large customers benefit from more flexibility in implementation and renewal compared to smaller ones.

What other advice do I have?

Working with Mule ESB has taught us the value of experience with different ESBs, making it easier to adapt to new solutions.

Overall, I would rate the solution a ten out of ten. 

Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Flag as inappropriate
PeerSpot user
Not specified ( Team Lead ) at ADP
Real User
Simple language for writing transformations; easy to develop APIs with minimal coding required
Pros and Cons
  • "The solution doesn't require much code writing and we can develop APIs very easily."
  • "The current version will not be supported for much longer."

What is our primary use case?

We use this solution when we have integrations and need to connect to SAP or to some Q mechanisms like ActiveMQ or RabbitMQ. The applications we develop are for administrators. We are customers of Mule ESB. 

What is most valuable?

The HTTP, SAP and RabbitMQ connectors that we use are very easy to connect. The language for writing the transformations is also very simple. This is a useful solution. The solution doesn't require much code writing and we can develop APIs very easily. 

What needs improvement?

The main issue we currently have is that the version we are using will not be supported for much longer and we'll have to migrate to the newer version. 

For how long have I used the solution?

I've been using this solution for five years. 

What do I think about the stability of the solution?

We use this solution every day and it is stable.

What do I think about the scalability of the solution?

The solution is scalable although we don't need to scale for now. 

How are customer service and support?

The support is pretty good. We raise a ticket when we need something and the response time is good. 

How would you rate customer service and support?

Positive

How was the initial setup?

We had some initial hiccups following deployment, but since then it's been good. We deployed in-house. 

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

Licensing costs are relatively expensive. 

Which other solutions did I evaluate?

The main difference I noticed between Mule and Red Hat Fuse was the licensing cost. Mule ESB was a more expensive solution. I haven't worked much on other ESBs but when I compare it with Spring Boot or other similar technologies, Mule is better in that it doesn't require much code writing.

What other advice do I have?

I rate this solution eight out of 10. 

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
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.
reviewer933312 - PeerSpot reviewer
Senior Software Engineer at a computer software company with 5,001-10,000 employees
Real User
Best for microservices-based architecture and easy to deploy and manage
Pros and Cons
  • "It is easily deployable and manageable. It has microservices-based architecture, which means that you can deploy the solution based on your needs, and you can manage the solution very easily."
  • "It should have some amount of logging."

What is our primary use case?

This is an enterprise service bus, and it is mainly used for transferring data. For example, it is used when System A has the data that needs to be sent to System B. 

Our use case is transferring the enterprise data from one enterprise to a different enterprise. We use different types of connectors or connections to get the data, transform the data, and send it to a system. Almost all the integrations work in the same manner.

It can be deployed on-premise, but nowadays, most of us prefer cloud-based solutions.

What is most valuable?

It is easy to use and easy to understand. 

It is easily deployable and manageable. It has microservices-based architecture, which means that you can deploy the solution based on your needs, and you can manage the solution very easily.

What needs improvement?

It should have some amount of logging.

For how long have I used the solution?

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

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

It can scale based on your needs. It is scalable vertically and horizontally.

We have used it in many projects. Its usage might increase. It depends on the high-level management. If new products are coming, they're going to use it for sure.

How are customer service and support?

Their response is based on the subscription. If you are experiencing any production-related issues, they're immediately available. 

There are various levels of tech support, and the service depends upon the level of support to which you have subscribed. Titanium support is at the highest level.

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

We have used webMethods, which is an on-prem solution. 

How was the initial setup?

For a cloud-based deployment, there is no need for us to manage anything. It is directly deployable. We build and deploy it. That's all. 

For an on-prem deployment, a lot more installation is required, but it is a very easy process.

What about the implementation team?

We can do an on-prem deployment ourselves. Developers mainly focus on the development aspect of the solutions, and admins manage all deployments.

Which other solutions did I evaluate?

We didn't evaluate other options.

What other advice do I have?

I would recommend this solution to others. It is the best integration platform for those who are looking to implement or are going for API-based architecture and microservices-based architecture.

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
Technical Architect at a tech services company with 51-200 employees
Real User
Improves integration with robust data transformation and asynchronous processing
Pros and Cons
  • "The product is very stable."
  • "Improvements could be made in performance."

What is our primary use case?

Mostly, we use Mule ESB for an integration piece where the source and destination need to be integrated with user-defined logic in between. This integration involves an API-led connectivity approach, which is a major component in MuleSoft.

What is most valuable?

The most valuable features of Mule ESB are DataWeave, which is the core of MuleSoft, and batch processing methods, such as batch processing for bulk loads and parallel processing for asynchronous tasks.

What needs improvement?

Improvements could be made in performance. MuleSoft has integrated more than 170 connectors, however, fine-tuning the runtime engine to handle more records in one go, like around 500,000, would be beneficial. More R&D is needed in the MuleSoft runtime engine for better performance.

I would rate it a nine out of ten.

For how long have I used the solution?

We have been using Mule ESB for nearly ten years.

What do I think about the stability of the solution?

The product is very stable; I would rate its stability as nine out of ten.

What do I think about the scalability of the solution?

I can give Mule ESB a scalability rating of nine out of ten. It scales very well.

How are customer service and support?

Technical support from MuleSoft is satisfactory, with a rating of eight out of ten. Their response time and quality of support meet our needs.

How would you rate customer service and support?

Positive

How was the initial setup?

For development, Mule ESB has a simple setup process. You simply download a zip file, extract it, and start using it immediately. However, if you want to deploy it on servers, that's a different case and requires following some standards.

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

Pricing is on the higher side due to licensing costs. It is more suited for large-cap companies that can afford this cost. I would rate pricing as a seven out of ten.

Which other solutions did I evaluate?

Spring Integration is one of Mule ESB's main competitors. Others include WSO2, although that is on the lesser side. We also consider Dell Boomi.

What other advice do I have?

The main benefits of Mule ESB are its scalability and reusability. In terms of functionality, everything seems to be in place, yet future needs depend on business use cases.

I'd rate the solution nine 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?

Other
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Saranjit Charoenmuang - PeerSpot reviewer
Technology Advisory, Integration Practice Leader at Slalom Consulting
Real User
Top 10
A great solution to get data with a straightforward setup and good scalability
Pros and Cons
  • "The setup is straightforward."
  • "The stability could be improved."

What is our primary use case?

We use this solution to get data.

What needs improvement?

The stability could be improved.

For how long have I used the solution?

We have been using this solution for about two years.

What do I think about the scalability of the solution?

The scalability is good, and I rate it a nine out of ten. We have about 20 users using this solution. We do not have plans to increase the number of users, as it depends on the number of use cases we deploy. We have developers, managers and business users using this solution.

How are customer service and support?

Technical support comes with the subscription plan.

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

We used Oracle ten years ago.

How was the initial setup?

The setup is straightforward. It was a fast deployment and took one week.

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

The subscription is annual.

What other advice do I have?

I rate the solution a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Gowtham Thotapalli - PeerSpot reviewer
Solutions Architect at Persistence System
Real User
Top 20
Easy and intuitive tool for developers but should have more customization capabilities
Pros and Cons
  • "This tool has exceptional API management and integration connectors in addition to multiple out of the box connectors."
  • "We would like the ability to use our own code. This would allow us to develop customizations with ease. Additionally, it would be nice to have more analytics or insights on the exchanged information between databases."

What is our primary use case?

I am a solution architect where I design solutions by leveraging integration tools, low-code platforms, and BPM platforms. We are using Mule EBS for transformation purposes.

How has it helped my organization?

Mule allows us to transform our data into our desired outcome and then translate it. This allows it to be moved forward for further processing.

What is most valuable?

This tool has exceptional API management and integration connectors in addition to multiple out of the box connectors. 

The UI is good. From a development perspective, it's pretty easy and pretty intuitive for the developers to work with. We have fresh graduates who have started picking up MuleSoft. Its user interface is pretty intuitive.

What needs improvement?

We would like the ability to use our own code. This would allow us to develop customizations with ease. Additionally, it would be nice to have more analytics or insights on the exchanged information between databases.

For how long have I used the solution?

I am working on my third project that utilizes Mule.

What do I think about the stability of the solution?

The solution is quite stable. We have not experienced any stability related issues as of now.

What do I think about the scalability of the solution?

We have not had any issues regarding up-scaling and other things. We are in the process of increasing the usage of Mule so that it can take up to two thousand requests per unit minute.

How are customer service and support?

The last time I raised a ticket with them where we needed additional guidance, they were pretty good and responsive. On one of my previous projects that I worked with where we needed some information or we needed some additional guidance from them, we were able to collaborate with them and solve the issue pretty quickly.

How was the initial setup?

The initial setup was straightforward as we chose to go with the Mule cloud where the infrastructure was taken care of by them. We only needed to ensure connectivity between on-premise databases/systems and Mule cloud.

Because it's their cloud, the setup is much easier. It would be interesting to see what the setup is like for an on-premise or hybrid environment. It might be a completely different setup. It would probably be more complex because you have to go through certain process to ensure the compliance and the security standards of the organization are met, and that the connectivity is established.

Which other solutions did I evaluate?

We looked in to using Apache Camel and TIBCO.

What other advice do I have?

It’s a pretty good tool to have it when you try to go with a microservices type of an architecture where you want to decouple your systems and where you want all the systems to talk to each other, share that knowledge, and create those experiences that you want as part of your digital transformation journey. This tool perfectly fits that. It's a good tool to have as part of your digital transformation journey.

I would rate it a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud

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

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1504908 - PeerSpot reviewer
Senior Software Engineer at a tech services company with 10,001+ employees
Real User
Offers multiple deployment options
Pros and Cons
  • "The solution offers multiple deployment options."
  • "It would be great to see implementing security modules as a feature."

What is our primary use case?

At the moment, we are using MuleSoft 4, for which I am a certified developer. We use version 4.3. 

What is most valuable?

We can do very fast development of the orchestrations of MuleSoft. The design patents which we use for integration patents are also a nice feature. 

The solution also offers multiple deployment options. I like the endpoint time manager and the access policies. 

What needs improvement?

In respect of the UI or the interface, a concept such as that offered by Microgateway would be preferable. We basically use ESB for the gateways. Yet, sometimes when we make use of on-premises standard applications, we require a Microgateway or sidecar proxy products or sidecar proxy-type gateways. This should be addressed. 

A Microgateway type of application should be available for lending support to MuleSoft. When it comes to standalone applications, it would be better if a sidecar proxy were available, rather than the security models being implemented inside the application. The sidecar proxies make things very simple in respect of microservices.

It would be great to see implementing security modules as a feature. 

For how long have I used the solution?

I have been working with MuleSoft for the past seven years. 

What do I think about the stability of the solution?

Our current requirements are not great. The version we currently use, 4.3, is much more stable at present. It has good stability. 

What do I think about the scalability of the solution?

The scalability is good. It varies with the request I receive or the application size. It can be done with much ease. 

How are customer service and technical support?

Technical support is more in the purview of developers. 

How was the initial setup?

The installation time depends on the product being deployed and the size of the application. What we are using at the moment would not require installation of more than an hour. We usually would receive a zip file that we would insert into the server, at which point we could start with the deployment. We have a command for the installation of the licenses and even this depends on the type of job involved. That is all. I would put the installation time at no more than 35 to 40 minutes. 

What about the implementation team?

I have done the installation on my own many times. I have this product on my personal laptop, as well and usually install it on my small machines. 

What other advice do I have?

As with our other applications, MuleSoft is on-premises, but we make use of a hybrid strategy involving the use of an endpoint cloud and agent. While our initial deployment was on-premises, our control plane is on endpoint in the cloud. 

I am a MuleSoft developer and am working for a client. The company which I work for is a partner with MuleSoft.

I would recommend MuleSoft to others. 

While what we are using for our current project is more than sufficient, it would be nice to see Microgateway added as a feature. 

I rate the solution as an eight out of ten. 

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
DhivakarSekar - PeerSpot reviewer
Enterprise Software Engineer at Wolters kluwer
Real User
Allows us to integrate with other software applications but could be more secure
Pros and Cons
  • "It's open source, and there are a lot of community resources. Mule ESB makes it easy to connect to other software applications."
  • "Mule ESB isn't as secure as IBM. Financial companies go with IBM for that reason."

What is our primary use case?

We use this solution to integrate with other software applications.

Now, we are running almost 50 integration APIs, and will have over 1 million billable transactions.

The solution can be deployed on cloud or on-premises. I'm using version 4.2.

What is most valuable?

It's open source, and there are a lot of community resources. Mule ESB makes it easy to connect to other software applications.

What needs improvement?

Mule ESB isn't as secure as IBM. Financial companies go with IBM for that reason.

For how long have I used the solution?

I have been using this solution for over nine years.

What do I think about the stability of the solution?

The stability is great compared to IBM.

What do I think about the scalability of the solution?

The scalability is amazing. You can increase the horizontal perspective or the increase the vertical perspective. It depends on your business needs.

How are customer service and support?

We have a dedicated support person from the MuleSoft tech support.

How was the initial setup?

Development is very easy. Initial setup took two days. We needed to open a firewall, download the necessary things, clean the server, file storage, network storage, and we needed to work on the installation of the servers.

For deployment, we had one person for admin and one person for development.

What other advice do I have?

I would rate this solution seven out of ten. 

I would recommend this solution for those who want to use it. It will depend on the customer's needs and what they want to use it for.

Which deployment model are you using for this solution?

Hybrid Cloud
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.