IT Central Station is now PeerSpot: Here's why

Mule ESB OverviewUNIXBusinessApplication

Mule ESB is #2 ranked solution in top Enterprise Service Bus (ESB) tools. PeerSpot users give Mule ESB an average rating of 8 out of 10. Mule ESB is most commonly compared to IBM Integration Bus: Mule ESB vs IBM Integration Bus. Mule ESB is popular among the large enterprise segment, accounting for 72% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 32% of all views.
Mule ESB Buyer's Guide

Download the Mule ESB Buyer's Guide including reviews and more. Updated: June 2022

What is Mule ESB?
For companies looking to modernize and unlock the value of existing on-premises systems and applications, an enterprise service bus (ESB) architecture serves as a critical foundation layer for SOA. When deployed as an ESB, the Mule runtime engine of Anypoint Platform combines the power of data and application integration across legacy systems and SaaS applications, with a seamless path to the other capabilities of Anypoint Platform and the full power of API-led connectivity.
Mule ESB Customers
Ube, PacificComp, University of Witwatersrand, Justice Systems, Camelot
Mule ESB Video

Mule ESB Pricing Advice

What users are saying about Mule ESB pricing:
  • "Most of the challenges that I had with this solution were for smaller customers. There is not a good licensing model or pricing model. It is more expensive than other solutions, and that's the downside of MuleSoft. I had to be creative to be able to sell it to the business, but we did. This is something they have to work on because for large companies, it's affordable, but for small and medium businesses, it's very hard to sell."
  • "The licensing is yearly, and there are additional fees for services."
  • Mule ESB Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    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
    Mule ESB
    June 2022
    Learn what your peers think about Mule ESB. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
    610,045 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.
    Flag as inappropriate
    Solutions Architect at a tech services company with 1,001-5,000 employees
    Real User
    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.
    Flag as inappropriate
    Buyer's Guide
    Mule ESB
    June 2022
    Learn what your peers think about Mule ESB. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
    610,045 professionals have used our research since 2012.
    Palavesam Subbiah - PeerSpot reviewer
    Senior Consultant at a tech services company with 1-10 employees
    Consultant
    Top 20
    Well performing and easy to use solution
    Pros and Cons
    • "What Mule provides out-of-box is a sufficient product."
    • "There are limitations with the subscription model that comes with the product."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    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.

    How are customer service and technical support?

    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.

    How was the initial setup?

    The initial setup was straightforward.

    What about the implementation team?

    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.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    Private Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Director - Projects at a consultancy with 51-200 employees
    Real User
    Provides many connectors to facilitate integration, and helpful community support is available
    Pros and Cons
    • "The most valuable feature for Mule is the number of connectors that are available."
    • "MuleSoft is not so strong in method-based integration, so they're not so functional in that regard."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    We have been working with this product for about a year.

    What do I think about the stability of the solution?

    No problems with stability have been brought to my attention, although once the system is in production, a different team handles it.

    What do I think about the scalability of the solution?

    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.

    How are customer service and technical support?

    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.

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

    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.

    How was the initial setup?

    The initial setup is very simple. The installation probably takes four hours, on average.

    What about the implementation team?

    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.

    What other advice do I have?

    I would rate this solution an eight 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?

    Amazon Web Services (AWS)
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Consultant, Architecture and Standards at a tech services company with 51-200 employees
    Consultant
    Top 20
    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.
    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
    Senior Software Engineer at a computer software company with 5,001-10,000 employees
    Real User
    Top 5Leaderboard
    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.
    Flag as inappropriate
    Jose-Ramirez - PeerSpot reviewer
    Software Developer at Softtek
    Real User
    Modernized the way my company offers services and improved the user experience
    Pros and Cons
    • "The solution improved my company by modernizing the way we 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."

    What is our primary use case?

    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.

    How has it helped my organization?

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

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    The solution has great scalability.

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

    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.

    How was the initial setup?

    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.

    What about the implementation team?

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

    What other advice do I have?

    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. 

    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.
    Flag as inappropriate
    Buyer's Guide
    Download our free Mule ESB Report and get advice and tips from experienced pros sharing their opinions.
    Updated: June 2022
    Buyer's Guide
    Download our free Mule ESB Report and get advice and tips from experienced pros sharing their opinions.