I would rate the solution's scalability as a seven out of ten.

Initially, we faced some issues with my setup in relation to TIBCO Enterprises Message Service. I had to set up or maybe activate standby. They were using an NSF as shared storage, but I experienced performance issues with that. However, these issues were not related to the product itself but rather to my infrastructure. If you can achieve scalability and have an active-active setup with three of us running concurrently, I believe that would be even better. I need to explore the possibilities of implementing an active setup.

Let me provide some information about my company. Initially, I was part of a larger organization, and recently we started another company in a different country. That's why I'm currently setting up Deepgram in South Africa. In our South African branch, we have around 40 developers. As for the new organization I'm setting up, we currently have around 15 developers. In my previous organization, we had a team of around 40 to 50 developers. So, this new organization acts as a subscriber to the previous one. We are starting fresh in a different country, specifically in Africa.

TIBCO is scalable. 

The scalability is good.

When I searched in Google, I found two other product comparisons like Mule ESB. If you want to scale, you can search for more integration products that are now coming in the market. TIBCO BusinessWorks is a very scalable product.

Most of our clients recommend using the TIBCO suite of products. It's highly recommended in many enterprise companies and very essential projects. It won't take much time.

Compared with other tools, we will take less time to develop with this. We can do continuous integration and continuous deployment as well.

No, with proper management it works perfectly.