When I came into the company, Mule ESB was already in use, although it was the older version. We needed to catch up and teach the new team members, so the exercise of microservice architecture for Mule ESB should be the bread and butter of our team. There were hardliners that didn't agree with it, and they left the company already, so we're fine now. We hired a bunch of young professionals that are very open to the microservice architecture, and we're doing fine with it at the moment.

I have experience with TIBCO ActiveMatrix Service Bus. I have fifteen years of experience with webMethods.io.

Compared to Mule ESB, you will find that there are fewer coding challenges in webMethods.io.

We work with various solutions for different clients, including both API and ESB solutions. We have not implemented Mule extensively in the banking sector due to preference for on-premises solutions.

I have little experience with Oracle Fusion. It's quite good, but the interface is pretty old-fashioned. I worked with IBM WebSphere as well. That was a big part of another project I worked on, but these are the two technologies I've used.

Currently, I'm working with Oracle Fusion. These solutions require elaborate coding, so you need to be extremely experienced in programming, with the ability to write tons of complex code. It's good to have a solid background in coding, but you shouldn't need to be an expert to work. 

We used Oracle ten years ago.

We have used webMethods, which is an on-prem solution. 

I previously used an eCommerce platform called Intershop, but it's not really an ESB. Intershop allows for the development of the whole eCommerce system, from the back end to the front end. I switched to Mule due to the needs of a new project that I was starting because it acts as a bridge between legacy systems and front-end systems.

We did not use another solution prior to this one. We started with the open source solution, version 3.1.0, and we implemented all of the services. We then paid for a licensed version.

I was previously using Talend ESB but it's more complex than Mule ESB to use. The commercial versions have more features than Talend ESB.

Prior to Mule ESB, we were using an IBM solution that was pretty good. Mule ESB is cheaper but I would choose the IBM product instead.

Some of my team members have worked on other ESB solutions in the past, but in this organization, we have not dealt with one other than MuleSoft.

One of the products that we are familiar with is a solution by IBM. This competing product is strong in terms of method-based integration.

We didn't previously use a different solution. We've only been working with MuleSoft.

We started with Mule ESB.

WebMethod is very expensive, but their support is awesome. I closely work with the operating technical support team. For retrieving the code from our bank, they are working with us very closely. Sometimes they are flying over here for conducting demos. 

Especially in the Middle East, MuleSoft is not doing like that. They are not doing much marketing in the industry. Maybe they are more focusing on South America or Asia. I'm not seeing much in the Middle East.

We were using a variety of technologies, but we use this solution because it is a very lightweight message processing system.

We switched because this solution was found to be cost effective, freely available for community edition, and an easy transition from any programming background.

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.

We used Oracle OSB before and some of our clients used TIBCO middleware or Java CAPS.

But we suggested that clients switch to Mule ESB due to:

• The lower licensing cost
• The availability of cloud connectors
• CloudHub platform (supporting iPaaS)
• A suite of 110+ connectors to use.

I did not use any ESB earlier, but this is the best Community Edition ESB available in the market. However, we abused it as a workflow engine.

Previously, we used Apache Camel and Spring Integration. However, they require more technical involvement than MuleSoft ESB.

I am working on a number of open-source integration platforms and MuleSoft ESB is an ideal choice for us. This tool makes it easier for the developers to deliver complex projects with the best quality.

Mule ESB is better than Oracle.