- We can use Java expressions anywhere in the flow
- Provides API support out-of-the-box
- API management can be done using RAML
It is very easy to learn and implement. We were able to meet project deadlines on time.
It needs more samples. Also, the dependency on Maven should be removed.
I have used Mule ESB for one year.
We had issues in Munit but rarely any stability issues.
We have not had stability issues.
We have not had scalability issues.
We had few guys from their support team.
They were excellent.Technical Support:
I would give technical support a rating of 8/10.
Firstly, the project architecture team decided to go with Mule.
Secondly, the project was from scratch and we want only microservices exposed over API hence, Mule was a promising deal.
However, in my next project we weren't able to go with as it much pricier than its competitors. Actually, from all the other vendors.
The setup was complex, as I came from a different background (IBM products). However, it became smoother down the line.
We went for a training first and then it was in-house after that.
This is expensive. In my next project, we had to go to other vendor.
Apparently, this is the most expensive ESB solution out there as there is no more Community Edition.
We looked at IBM IB and webMethods.
Go for it, but first read their sample exercises.
It is a one stop solution and it is an amazing product.
1. It is an expensive product
2. Expensive support