Please share with the community what you think needs improvement with Mule Anypoint Platform.
What are its weaknesses? What would you like to see changed in a future version?
1. Clarity w.r.t. Licensing Model: Mule is a complex licensing model -- There are 4 types of connectors -- Select, Premium, MuleSoft Certified, Community
2. Unclear/incomplete documentation: Like for example in the case of Mongo DB there is no way you can understand the significance of "connection string" based connectivity like LDAP based Authentication or X509 kind of connectivity.
3. High price / vCore; you are an enterprise and have enough money then they can afford Mule; ETL sort of transformations if not understood properly will increase the Memory and core count.
4. Community support and Open Source camaraderie can for sure be improved.
5. Limited configurability on cloud and RTF deployments.
6. Dataweave is another language to learn and transformations are CPU intensive in nature. There is no portability for your scripts or interoperability if I want to port from other languages into Dataweave if I am newly coming onto the cloud;
6. Auto mapping features like in the case of Salesforce connector to other connectors as well.
The solution is very expensive. They need to work on the pricing. Technical information is not always easy to find. They should work to make it more accessible.
One should have hands-on experience on the DataWeave. If somebody knows MuleSoft and is planning to work closely with the solution, they should be comfortable with DataWeave. Pricing is one aspect of the solution that is troublesome. There should be a lot of improvement in general, as this is a premium product, I can say. Most of the customers like to go ahead with MuleSoft implementation, but at the end of the day what is happening is when they go ahead and see the pricing, they get scared. Performance-wise also they need to improve a lot. Basically, the number of ports is lacking. When you have ETL kind of transformation, ideally it will be supported, however, we end up using a large number of ports. That will drastically increase the cost to the customer, however. They need to be able to allow for an increase in ports without expanding the price. Everybody's now integrating with AI and ML kinds of features. They need to add more of these features into their offering as well. The scalability on offer could be better.
Its documentation needed a little bit of work to make it more usable. It is a platform that is used mainly by developers and other people for connecting systems. Its documentation was confusing in some areas and was not very helpful in other areas. I had to go to a consultant to get some work done, which ideally shouldn't be required.
Better documentation, in particular with respect to the initial setup, would be helpful.
It has different types of subscriptions. For platinum or lower subscriptions, there are not too many things that can be done. We don't see many features. They should release a basic version that has logging and monitoring features. These features should come with Mule Anypoint Platform for free instead of making customers pay separately for these features. Its dashboard can be improved to have a lot of charts so that it is easy to visualize information. The utilization part can be improved. The dashboard is good currently, but it can be better. Other solutions like Elastic have a good dashboard, and they allow you to administer the product from the UI. Currently, for RTF, there is a different dashboard or utility. It would be good to include the same utility in the cloud solution. It would be good if there is a centralized repository that includes the links to the information about various troubleshooting issues. The documentation is there currently, and it is good, but the troubleshooting information is too scattered. We have to go to different links to find troubleshooting information. This kind of centralized repository would be helpful for new customers who are implementing this solution. It will be helpful to see different kinds of issues that can occur.
With regard to the integrations, I'd like to see something similar to the features you find in Dell Boomi related to the intelligent management data and intelligent mappings. Those would be helpful improvements that would help developers. For beginner users with little technical knowledge, some low code would help. The solution is Java oriented but doesn't require Java knowledge which is good. But when you are debugging something or when you have other issues, it's important to know a little bit about that. I'd like to see some simplification. Anything that can be automated in the Data V area would also be helpful.
In terms of improvement, customer support is a bit slow. I emailed the sales team for a pricing comparison, still no response. The developer community is far more generous on the other hand. Pricing model is very expensive, Mule should consider Pay as You go model. It will help on-boarding new clients in Asia region. Mule should have better B2B integration. Mule supports the idea of API Led Architecture and system of records approach. When it comes to broad perspectives such as B2B, competitive tools have better EIPs.
Overall, I think they're keeping pace with the changes that are happening. I don't have any complaints about anything. They could just improve implementing the integration. I would also like to see some kind of monetization of A-P-S. That's important.
As far as improvements, the runtime management in MuleSoft can be much better. It has some issues, or we have issues with it. As for additions, the first thing that I want is for them to create their own connectors. That is very important. Other things beyond that are hard for me to imagine right now especially because they have a lot of features already that we are not yet using.
Technical support needs to be improved, especially when you need help with more technical aspects of the solution.
MuleSoft's release calendar is rather conventional with two major, two minor releases and hotfixes in between. The competition sometimes offer more rapid release cycles and provides improved and new functionality with a faster time-to-market.
Some improvements are required in the batch component in case of errors in the batch steps and when processing a large volume of data.
How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
Let the community know what you think. Share your opinions now!