Coming October 25: PeerSpot Awards will be announced! Learn more
Miriam Tover - PeerSpot reviewer
Service Delivery Manager at PeerSpot (formerly IT Central Station)
  • 0
  • 23

What needs improvement with Mule ESB?

Please share with the community what you think needs improvement with Mule ESB.

What are its weaknesses? What would you like to see changed in a future version?

PeerSpot user
21 Answers
PurbayanSaha - PeerSpot reviewer
Associate Consultant at Wipro
Top 20
23 June 22

MuleSoft isn't as mature as some other integration technologies out there like IBM WebSphere. There's room for growth, and MuleSoft is working toward that. They're already implementing a graph system, which should help organize the APIs in a branched way. It looks more like a relational database now. They're also working on MuleSoft Composer. These are the features that they're working on.

Santosh Solapurkar - PeerSpot reviewer
Manager at Deloitte
Real User
Top 20
08 June 22

The price of Mule ESB could improve.

Badrakh V - PeerSpot reviewer
Information System Architect at Astvision
Real User
Top 20
15 May 22

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.

Mahdy Zia Uzzaman - PeerSpot reviewer
System Integration Engineer at ILCS
Real User
Top 20
05 April 22

Mule ESB could be more user-friendly. I think users must learn about the architecture before they start coding. The price could be better. In the next release, I would like to see an EDIFACT integration.

Solutions Architect at a tech services company with 1,001-5,000 employees
Real User
27 December 21

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.

Senior Software Engineer at a computer software company with 5,001-10,000 employees
Real User
Top 5Leaderboard
21 December 21

It should have some amount of logging.

Learn what your peers think about Mule ESB. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
634,550 professionals have used our research since 2012.
Hashim Sharif - PeerSpot reviewer
Co Founder - Data Engineering Head at Sadeeem Knowledge
Real User
Top 20
21 October 21

I'd like to see more attention given to the community editions.

Senior Software Engineer at a tech services company with 10,001+ employees
Real User
12 July 21

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.

VenkatRaj - PeerSpot reviewer
Tech Lead at V-Soft
Top 20
18 February 21

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

Palavesam Subbiah - PeerSpot reviewer
Senior Consultant at a tech services company with 1-10 employees
Top 20
19 October 20

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.

Manager- Integration Services & BPM at a financial services firm with 1,001-5,000 employees
Real User
Top 20
11 October 20

There are some issues with both stability and scalability. I have experienced some issues with clustering.

Director - Projects at a consultancy with 51-200 employees
Real User
06 September 20

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.

Consultant, Architecture and Standards at a tech services company with 51-200 employees
30 August 20

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.

Amit Behere - PeerSpot reviewer
Software Engineer at a tech services company with 51-200 employees
Real User
19 August 20

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.

Ravi Gunda - PeerSpot reviewer
Senior Architect at Wipro Technologies
Real User
26 January 20

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.

JustinJames - PeerSpot reviewer
IT Consultant at a financial services firm with 5,001-10,000 employees
Real User
19 June 19

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.

Developer at a tech services company with 1,001-5,000 employees
Real User
30 May 19

This solution could be improved by making it more flexible, and more user-friendly. I would like to see support for BPM in the next release of this solution.

Misabh Ulhaq - PeerSpot reviewer
Software Engineer at ADM
Real User
Top 10
29 May 19

We would like to have a built-in logging framework in which we can do auditing. In our case, we are working on-premise. We are not using the cloud solution, so we have MMC, which is not enough in a high transaction environment.

Developer JAVA/JEE, Mule ESB at a tech vendor with 11-50 employees
Real User
28 May 19

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.

Technical Lead at a tech services company with 10,001+ employees
12 November 18

* Support, and with respect to licensing cost. * Many of the customers feel that the licensing cost is much.

it_user805440 - PeerSpot reviewer
Applications Architect at Informatica Delta
21 January 18

* The payment system * The accounting and financial areas * The provisioning and enrollment system, because the response time was short.

Related Questions
Netanya Carmi - PeerSpot reviewer
Content Manager at PeerSpot (formerly IT Central Station)
Nov 15, 2021
And why?
See 1 answer
Dovid Gelber - PeerSpot reviewer
Tech blogger
15 November 21
Our team ran a comparison of IBM’s Integration Bus vs. Mule ESB in order to determine what sort of ESB software was the best fit for our organization. Ultimately we decided to choose IBM Integration Bus to handle our integration needs. This solution approaches application integration from a user-oriented point of view. There is an intuitiveness to this program in that anyone can learn to use the software fairly quickly. Users are enabled to learn and develop applications that fit their needs. For a program so crucial to the functioning of an organization, this factor makes IBM’s Integration Bus incredibly valuable. Mule ESB is a software solution that allows organizations to connect and integrate applications with relative ease. However, when it comes to the intuitiveness of the product, Mule ESB lacks the ease of use that IBM Integration Bus offers. This takes multiple forms. As far as being able to integrate applications, the ease truly is relative. Troubleshooting is an area where we felt users were not really considered. In order to troubleshoot Mule ESB, an organization will need a dedicated team of experts. The process is complex and requires a great deal of technical knowledge to execute properly. In order to troubleshoot potential issues, either an expert would need to be brought on or employees would have to receive advanced technical training. IBM Integration Bus handles all of the API language conversions, code conversions, and log maintenance that a company may require. This drastically cuts the time and resources that your organization would need to devote to its projects in order to implement any integration changes to your systems. As is true with troubleshooting Mule ESB, unless you are someone who has years of experience, integrations can prove to be more challenging than a company might hope for. It is not feasible for just anyone to learn how to use this product, which means that you will need a team of dedicated experts to use it effectively. Mule ESB cannot match the automation that IBM Integration Bus can offer. Conclusion Both IBM Integration Bus and Mule ESB are products that aim to aid in the integration of users’ applications. However, IBM’s intuitiveness and automated features make it by far the superior solution.
Senior Project Manager - IT Services at a tech services company with 10,001+ employees
Jul 12, 2021
I'm a Senior Project Manager of IT Services at a large enterprise tech services company. What are the key areas to focus on when you need to plan migration from IBM Integration Bus to Mulesoft ESB?
See 2 answers
User at Sony Corporation of America
02 March 21
I have the same question. 
Narayanaa - PeerSpot reviewer
Senior Principal Architect at Invenio Business Solution Pvt Ltd
12 July 21
I was previously part of the Oracle SOA/OSB development team. In my current capacity I architected solutions using MuleSoft Anypoint Platform on cloud / on-premises and hybrid modes and on PCE/RTF on Self Managed Kubernetes and On-premise apart from regular CloudHub Deployment; I am presuming you already took the decision of going with MuleSoft; Hence I wouldn't be dwelling on why migration; I would be considering the following things: 1. ESB to API led connectivity: -- it would be a paradigm shift since its a layered approach w.r.t. the services System/ Process and Experience layers; If you are re-writing the whole stuff at a time that's one way but considering the business continuity that might not be a practical approach. 2. Deployment -- Cloud / On-Premises / Hybrid; 3. What is the type of deployment: Naked Mule / Runtime Fabric / Pure Cloud with CloudHub 4. If on Runtime Fabric -- is it self managed Kubernetes over AWS / Azure / GKE? 5. How are my previous integrations? -- Is it Monolithic? -- You need to consider the Strangler pattern to move -- start migrating few services first and the rest of them later so that you don't lose business continuity. 6. If yes, how do I break it down? -- What are business-critical systems -- how do you take care of them? 7. What is my Database / If I am moving to Microservices -- how do I take care of a single monolithic database -- What pattern would I be using -- Shared Database per service? -- If you have multiple data sources how would you take care? -- Like CQRS pattern? 8. Traditional ESB takes care of Transactions -- but in Microservices led world the services would be lightweight and less dependent and have disparate data sources -- you might need SAGA + CQRS patterns based on how are you managing the data. 9. Security: You need to consider based on deployment model and other deployment criteria security at different levels -- Infrastructure level i.e. firewall / Load balance level for DDoS, IP Whitelisting etc.. whereas at the API level you might look at Rate limiting / Client Id etc.. and At the Organization level you might go for SSO / OAuth with JWT tokens. 10. Microservices Architecture requires Message Queues for loose coupling -- on CloudHub you might have Anypoint MQ but in other cases you might need Active MQ or some other mechanism. 11. Batch Processes with Chron Jobs are another issue that you need to take care of. If you don't plan them properly they can eat up your CPU because they need a lot of memory. Since 4.x later streaming is supported -- orchestrate your Batch Jobs carefully 12. Transformations in Dataweave: This is another tricky thing -- if you have all your business logic here it would make your integrations non-portable- 13. Business Rule Engine Integration: -- Mule doesn't come with a BRE integrated so you have to use 3rd party BRE like Drools or Groovy-based Rule engine etc. 14. Work Flows: Mule doesn't have any workflow support that requires human intervention. hence you might look at something like Activity or Flowable or Apache Airflow to integrate a few of your scenarios.
Related Articles
Netanya Carmi - PeerSpot reviewer
Content Manager at PeerSpot (formerly IT Central Station)
Apr 26, 2022
PeerSpot’s crowdsourced user review platform helps technology decision-makers around the world to better connect with peers and other independent experts who provide advice without vendor bias. Our users have ranked these solutions according to their valuable features, and discuss which features they like most and why. You can read user reviews for the Top 5 Enterprise Service Bus (ESB) Tools...
Evgeny Belenky - PeerSpot reviewer
Director of Community at PeerSpot (formerly IT Central Station)
Jul 11, 2022
Hi community members, As usual, this new Community Spotlight shares with you the latest articles, questions and trending discussions from your peers. Trending See what is trending at the moment and chime in to discuss! Top 8 Extended Detection and Response (XDR) Tools 2022 Would you recommend replacing Cisco ASA Firewall with Fortinet FortiGate FG 100F due to cost reasons? What is the...
See 2 comments
Ravi Suvvari - PeerSpot reviewer
Performance and Fault-tolerance Architect with 1,001-5,000 employees
30 May 22
Good very informative
Jairo Willian Pereira - PeerSpot reviewer
Information Security Manager at a financial services firm with 5,001-10,000 employees
11 July 22
Analyze the wave of product at Gartner Hype Cycle. EDR was good in the past. After that, MDR joined the hype and now, XDR is the trend. Wait for more in a couple of months and (sic) know the ZDR!
Related Solutions
Related Articles
Netanya Carmi - PeerSpot reviewer
Content Manager at PeerSpot (formerly IT Central Station)
Apr 26, 2022
Top 5 Enterprise Service Bus (ESB) Tools 2022
PeerSpot’s crowdsourced user review platform helps technology decision-makers around the world to...
Evgeny Belenky - PeerSpot reviewer
Director of Community at PeerSpot (formerly IT Central Station)
Jul 11, 2022
Community Spotlight #14 - Top XDR Tools and More
Hi community members, As usual, this new Community Spotlight shares with you the latest articles...
Download Free Report
Download our free Mule ESB Report and get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
634,550 professionals have used our research since 2012.