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?
In an upcoming release, I would like to see more additional concept for exception handling, batch processing, and increased integration with other application.
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.
There are some issues with both stability and scalability. I have experienced some issues with clustering.
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.
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.
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.
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.
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.
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.
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.
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.
* Support, and with respect to licensing cost. * Many of the customers feel that the licensing cost is much.
* The payment system * The accounting and financial areas * The provisioning and enrollment system, because the response time was short.
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?