I was working as an integration partner with Duo Java using GMSQ and GMS knowledge. But I didn’t use specific integration products.

However, with IBM, I am using IBM Business Process Manager, Message Brokers, and IBM App Connect Enterprise.

Although we didn't use another solution per se, we do use MuleSoft. 

MuleSoft is more lightweight. It's not as monolithic. We use MuleSoft and another IBM solution. However, we've been using IBM Integration Bus for such a long time at this point. It's been ten to 15 years or so. We've only used MuleSoft for the last three years. It has high productivity and a good number of integrations and the API exchange capabilities.

We run the solutions in parallel.

MuleSoft is a pretty good solution, however, we've noticed that the pricing over the last few years has gone up and it's become quite costly.

I have previously used databases to store and forward and C-programs to manipulate data. When this could no longer cope (sometime in the 1990s), I discovered IBM MQ and other messaging products, which are designed to do what we were building. The MQSI product of the time was simply magic and the latest incarnations (App Connect Enterprise) are far beyond anything that could be done with a database. 

I have reviewed other technologies, including Microsoft, open-source, and others. It remains my opinion and experience that this product delivers quicker development and more reliable outcomes.

Before we went to IBM, we didn't use a different solution, however, we checked in our industry and we checked how people felt about Microsoft middleware, and they didn't have a good experience. It's not robust, the support wasn't strong, et cetera. Therefore, we chose IBM. We were swayed by how other organizations, including banks in Nigeria, were mostly seeing success with IBM.

We are using WSO2 for some applications, however, we do not rely on it completely as it is open-source and if we run into issues we cannot rely on help from any support.

I have not worked with other solutions similar to IBM Integration Bus.

I previously used TIBCO and webMethods.

I also work with MuleSoft. Comparing IIB to MuleSoft, IIB is always used by big companies because it is a licensed solution, whereas MuleSoft is open source. So, small organizations use MuleSoft. Our clients in the USA, Canada, and Dubai preferred IIB over MuleSoft because they have more belief in IBM products, and they feel more secure and safe while using it.

Prior to this solution, we used TIBCO. I was not involved in the integration bus, so I don't know the history before we moved to IBM.

We previously used other solutions, including Oracle, specifically Oracle Fusion Middleware. IBM is much better. It has many more options and offers more functionality. IBM offers better customization, configuration, and options in general.

We did not switch. Wherever I have implemented it, it was either:

1. IIB/WMB was already there.
2. It was the preferred choice.

Our company has been using IBM technology from the beginning.

We did previously have another solution called BixTalk which we were using four to five years ago. One major problem with BizTalk was that we had very few people available who were actually trained on it. Secondly, there were some sever issues as well. We had a synchronization problem on top of that. Because it was so long ago I do not remember all the issues. Maybe we did have some other problems also. But we had a problem with the product support as well.  

I have not used another similar solution by another vendor, although I have been part of projects where other systems had been implemented.

When I started at the facility, they were using CORBA (Common Object Request Broker) for the integration. It was used very intensively, and the project to introduce this solution was the replacement.

We used to use client-service applications with strong integration between application. The company implemented many other applications with different interfaces and aimed to link with external services. So that we started using Integration bus for integration legacy application with new applications.

We previously used a local solution and replaced this with a new enterprise solution. 

I have not really used any other ESB solutions.

Previously, we were using Microsoft Biztalk Server for middleware and integrations. Because of the obsolete version of Biztalk and the end of the support agreement with Microsoft, we decided to switch to some new technologies with advanced features where we can implement SOA services. Hence we decided to go with IIB.

I have prior experience with Oracle. The work bus and the the word map is totally different from Oracle.  In Oracle you're doing the job management most of the time, in IBM product, their version, it's much easier. You just try to sync with it and that's all. IBM is an easier product to use.

I also have prior experience with Microsoft, but that was in 2008. At that time, there were issues with integration

I'm also familiar with Apache Kafka. Kafka is much faster. The performance is much greater than IIB. IIB is not as fast as Kafka.

I didn't previously use a different solution.

We did not use a similar product before implementing IBM Integration Bus. In some instances, we have used microservice applications instead.