My company did evaluate other options in the market, considering that we need to start any integration-related discussions by speaking about how complex integration can be for us before choosing the product that can be better for us.

The main difference I noticed between Mule and Red Hat Fuse was the licensing cost. Mule ESB was a more expensive solution. I haven't worked much on other ESBs but when I compare it with Spring Boot or other similar technologies, Mule is better in that it doesn't require much code writing.

We have used TIBCO.

We didn't evaluate other options.

We looked in to using Apache Camel and TIBCO.

Before choosing, we also evaluated:

• Oracle SOA Suite
• Open ESB
• JBoss ESB

Before moving to the licensed version of this solution, we had a meeting to discuss the IBM Oracle web method. After looking at everything, including our code and the capability that Oracle has, we decided to continue with Mule ESB because of the ease in moving from the older, open source version, to the newer one. All we had to do is download it and continue with our work.

We evaluated Oracle, AG webMethods, and Red Hat OpenShift. The final one was MuleSoft. I'm very impressed with MuleSoft because of the pricing and license.

You have to implement several components. Sometimes, according to your needs, you have to buy several licenses for each component. Those are the things we compared.

We looked at IBM IB and webMethods.

I've been in a consultancy environment for a long time and knew various frameworks and tools already.

We looked at other options, but this one is what our vendor recommended.

We evaluated Oracle ESB, Apache Camel, and ServiceMix.

I was not part of choosing this solution.

We looked at Apache Camel, Fuse ESB, Dell Boomi, and TIBCO.

I am working on frameworks/solutions such as Red Hat JBoss Fuse, Spring Integration, Apache Camel, and Apache ServiceMix.

We evaluated Dell Boomi, Informatica, and Talend. However, for the given use case, MuleSoft came out on top.