Mule ESB Reviews

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.

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.

I have been using this solution for over nine years.

The stability is great compared to IBM.

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

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

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.

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.

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. 

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. 

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. 

I've been using this solution for five years. 

We use this solution every day and it is stable.

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

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

Positive

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

Licensing costs are relatively expensive. 

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.

I rate this solution eight out of 10. 

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.

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.

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.

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.

I am working on my third project that utilizes Mule.

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

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.

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.

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.

We looked in to using Apache Camel and TIBCO.

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.

We use this solution to get data.

The stability could be improved.

We have been using this solution for about two years.

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.

Technical support comes with the subscription plan.

We used Oracle ten years ago.

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

The subscription is annual.

I rate the solution a nine out of ten.

We used Mule ESB for the integration between two or three organizations.

The solution's drag-and-drop interface and data viewer helped us quite a lot.

It would be much more beneficial if the solution included AI and business process management.

We have been implementing the solution for three years now in our company.

Sometimes, we had to restart the servers from time to time because of some environmental issues.

I rate the solution a six out of ten for stability.

Mule ESB is a scalable solution. Our clients for Mule ESB are small and medium enterprises (SMEs).

The solution's initial setup is easy.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

The solution can be deployed in a few minutes.

Mule ESB is an expensive solution.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing an eight out of ten.

We were using the solution for the transformation of requests. So, it was good for us to exchange data and establish communication between different legacy and modern systems.

Mainly, we were using the transformers. Other than that, the process flows were very helpful for us to implement them. Earlier, the integration was done into the development and through the languages itself, like custom implementation. With Mule ESB, we could do many transformations and implement the process flows within the services itself.

We were having the same service which we had to distribute among the different clients. The proxy and role assignment was done through Mule ESB. This helped us with the distribution of services among different vendors and then validating them based on their roles.

Although we faced some challenges initially, we got the expertise by learning from Mule ESB itself. Eventually, everything got smooth, and we never had any issues with the deployment. Depending on the requirements and the size of the projects, I would recommend Mule ESB to other users.

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

When I worked for the Sprint telephone company, we used the solution as a bridge between their legacy systems and the front end. We developed a lot of the functionality, for example, logging into users' accounts and activating cell phones.

The solution improved the company by modernizing the way they offer services and improving the user experience.

In the next release, I would like to see improvement in the generator for the DataWeave language so that it's a little more graphic.

I've been using Mule ESB since 2016, so about six years.

The stability of the solution is great. In fact, the stability is another improvement that the solution brought to the company.

The solution has great scalability.

I previously used an eCommerce platform called Intershop, but it's not really an ESB. Intershop allows for the development of the whole eCommerce system, from the back end to the front end. I switched to Mule due to the needs of a new project that I was starting because it acts as a bridge between legacy systems and front-end systems.

It was kind of straightforward. We had to study their legacy systems and then make some kind of mapping between those legacy systems and the RESTful APIs handled by Mule.

We used a consultant directly from MuleSoft for deployment. It took about an hour or two to deploy the solution, plus time for testing. 

To those looking into implementing this solution, I would say that you will enjoy the experience of using Mule.

I would rate this solution as a ten out of ten. 

• Deployment strategies: Mule supports a wide variety of deployment strategies.
• SOA architectural style: Mule can embrace the architectural style and SOA practices in place where it’s deployed.
• Focused on higher-level concerns: It deals extensively with all the details of integration and provides a wide range of connectors. It has the ability to be an integration framework open to all sorts of protocols.
• They have comprehensive and up-to-date documentation, a subject on which the vendor has made huge progress recently.

It integrates between an ERP (J2EE inventory module), a CRM (PHP) and a new mobile development platform (Angular JavaScript web services).

The aim of the solution was to connect to the inventory application provided by the ERP system, read and send data to the CRM, then hook that to the smartphone with a user-friendly UI.

Some requirements:

• Integrate applications or systems on premise or in the cloud.
• Use out-of-the-box connectors to create SaaS integration applications.
• Build and expose APIs.
• Consume APIs.

I think using Anypoint Studio at the beginning can be seen as not straightforward, especially when dealing with the visual editor. A vertical representation of the flow can really improve the understanding of the case and a good mapping to the use case.

I have been using it for 1-2 years.

Like any application, Mule is constrained by the limits of memory size and CPU performance.

Threading profiles define the overall capacity of your Mule instance in terms of scaling and capacity. The performance of each moving part involved in processing each request will also impact the global throughput of your application.

Setup was realy straightforward as the product is well documented. Also, we should mention the efforts of a good and reactive community.

Before choosing, we also evaluated:

• Oracle SOA Suite
• Open ESB
• JBoss ESB

My advice to organisations looking to implement this product is to begin with the community version as a proof-of-concept and a way to avoid risks. You can then directly migrate to the enterprise edition as the Anypoint Platform offers tools that architects and developers across the enterprise can adapt quickly to design, build, and manage the entire lifecycle of their APIs, applications and products. With Mule as its core runtime engine, Anypoint Platform is built with open technologies to promote reusability, modularity and collaboration, increasing developer productivity and project speed.

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

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.

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.

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

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.

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.

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

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.

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

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.