When we started six or seven years ago, we could choose between TIBCO BusinessWorks or Office's Shell. The clear choice between the two was TIBCO BusinessWorks as it has more advantages.

But later on, as things improved in the IT world, Apache became a better solution as it is open source. At the same time, it's backed by Java. It has significantly more features compared to TIBCO BusinessWorks and, at the same time, its licensing cost is almost zero because it's open source.

I also have some experience with WSO2. From my perspective, TIBCO is easier to develop and, with this solution, I can make more specific solutions from a technical perspective. From a user perspective and developer perspective, this tool is more important. 

Previously, I was using a solution, and I switched to TIBCO BusinessWorks because of the good internal architecture.

We are also using TIBCO Enterprise Messaging Service (EMS).

I previously used RedHat and the open-source Jave Spring framework. We switched to TIBCO BusinessWorks primarily for the features, the cost, and the scalability.

There was a time we did a pilot with Oracle SOA (Service-Oriented Architecture). But in terms of a faster API tool, TIBCO is miles ahead of SOA in terms of functionality and setup. It is also better in terms of ease-of-use. Oracle is too complex. I find it unnecessarily complex and heavy.  

We didn't previously use a different solution before implementing TIBCO.

I have not used other solutions.

I've personally used a different solution previously. TIBCO was basically a client requirement. I've implemented multiple integration platforms according to the client's requirements and preferences.

Within the past year, I've explored MuleSoft. I haven't used it much but I know how it works. It has different advantages, and it's more API-based. It's a cloud-based solution.