If you were talking to someone whose organization is considering Mule ESB, what would you say?
How would you rate it and why? Any other tips or advice?
I rate Mule ESB a nine out of ten.
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.
I would rate this solution a six out of ten.
I would rate this solution an eight out of ten.
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.
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.
My opinion is that Mule ESB depends on the business and the continuity of their enrollment. If you are a system that has not much left to repair, then your products and your APIs are assets within your organization. Here in the bank, we are facing different kinds of issues when we are integrating different systems: * We are communicating with different card carriers like Mastercard and Visa. * Their standards are different according to the client requirements, i.e. exactly what kind of card they're looking for. * They can get the products according to their requirements as well as their budget. I would rate Mule ESB with 7.5 or 8 out of 10. * It's really easy to implement. * It's supporting our platforms: Windows, Linux, and Mac. * The performance. * It's free. I'm looking for an API platform that supports the whole technology as well as the next-gen. Mule ESB is lacking for self-support, self-training, and documentation. The documentation of the product is less because they're selling the training. You have to enroll for the training, then you'll get the full documentation. If you're an advanced user, you will not get much information from the public documentation.
I would rate this solution a seven out of ten.
My advice to others who are implementing this solution is to first become acquainted with the forums. There are always reports coming out about the software, and new technologies. The next thing is that I would suggest always starting with the latest version. Older versions are available, but you should install the most recent one. I would rate this solution an eight out of ten.
I will soon be migrating to version 4 of Mule ESB, although we are also interested in the WSO2 solution because it seems to be very complete. Using Mule ESB does not require somebody to be a Java developer, although there are some Java concepts that you need to know. For example, some people use JSON, and I find that they are scared of Mule ESB because it is based on Java. But really, it isn't a problem if they don't know it. This solution has good performance and support, but not everybody can use it because many of the features are expensive. Especially for application management, it is expensive compared to solutions such as WSO2. It is limiting for small and medium-sized companies. I would rate this solution a seven out of ten.
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?