I have previously used Dell Boomi. One of the main differences in features when comparing the Mule Anypoint Platform to other solutions is the availability of connectors. 

Dell Boomi has a slight edge in MDM because it can easily connect. On the EPM side, they are much stronger, whereas, on the data integration side, the Mule Anypoint Platform is much stronger. If you are doing a complex integration, I would give higher marks to the Mule Anypoint Platform. However, if you are doing a medium-scale integration or a simple integration, then Dell Boomi has the edge.

We migrated from TIBCO.

I'm familiar with TIBCO. TIBCO has a PW container edition, and they're similar. However, PW is using expert language for internal and external transformation. Mule is using the database transformation. That database transformation, it's a totally new language. If you want to use the Mule, then you should have experience in that first.

Mule is a very good competitor of TIBCO, and Salesforce has acquired Mule. So the market has also grown drastically for Mule. 

We may have also moved based on the price, of which Mule's is better.

If they used XPath, XML query language, instead of DataWeave, it would be ideal. That way, our users don't need to worry about knowing a different language.

I have previously used Apache Camel and Dell Boomi but I am also currently using Ab Initio due to client requirements and the need for a faster time-to-market for clients' projects or products. Using a team of ten members, it took around 24 months to complete the migration of approximately 2,000 APIs with Anypoint Platform. Ab Initio only required nine months to accomplish a similar task.

Previously, we used Cisco in our company.

I have previously used IBM. 

The system we have is straightforward yet highly integrated. It is a single platform, unlike IBM, where they had multiple platforms and systems to deliver similar value. This complexity made the IBM system challenging to navigate as their technical resources had to learn various platforms, including integration and API gateway, which had different formats. Consolidating these platforms into one unified system would simplify management and reduce complexity.

Before switching to MuleSoft Anypoint Platform we were using Talend Data Integration. We ended up choosing Mule over Talend for a number of reasons. There was easier adaptability for our current resources. The most important reason was that we had a reason to believe that the compatibility would be better because we were strategically using Salesforce as one of our core frameworks. Salesforce acquired MuleSoft and we were trying to avoid more problems by staying with a competing product in this situation. We hoped there would be more integrations between the Salesforce and MuleSoft platforms and that played a role in our decision. After that, we had a little bit of a price break. For our use case, MuleSoft seemed to be a better fit. Talend, in general, is a great platform but just did not fit as well for our use case.

I used an open source tool. Red Hat Fuse. Switching from different tools and technologies depends on the project in hand.

I've used TIBCO and webMethods, but they are not as effective at cloud-based integration as MuleSoft Anypoint Platform is.

We didn't previously use a different solution.

Before this product, we used webMethods. We switch solutions due to a customer requirement. 

Point-to-point connections. An iPaaS and/or API management offers more advantages, such as shorter time-to-market, less staff required for development and maintenance, less incidents on support, etc.

MuleSoft has a pure and dedicated vertical focus on product development for integration with their API management and iPaaS offerings, which can be consider as a plus.