ActiveMQ is not automatically scalable. You have to provision a server in order to scale to different regions, deploying another messaging queue.

ActiveMQ's scalability meets our project needs well. Our application doesn't require rapid message delivery, so we haven't encountered scalability issues. The frequency of code updates isn't extremely high, so ActiveMQ effectively handles our messaging requirements without any significant challenges.

I have not encountered any scalability issues.

We don't see the solution used as much as Apache Kafka by our customers, but it is scalable.

ActiveMQ is scalable.

That capability is included in the product, but it is also limited to the use cases of our applications because we are using it as part of the middleware services, which will scale it when the application scales up.

The Mule versions we are currently using do not have that horizontal scalability. It is vertically scalable, which means that you can use it for that type of scalability, but it also supports horizontal scalability, which is very important in today's world.

People are primarily using the solution as part of a middleware application, there are many of our, major clients, which are internal applications that consume it, such as credit or credit systems, and so on. 

They intend to make extensive use of it as part of their message dissemination efforts.

The production engineer, application support technicians, application developer, and lead designer are the people who use it. This is the group of people who are actively participating or have the authority to know who is contracting with us.

It's absolutely scalable. We are using the broker technology.

There were no scalability issues. With a good strategy, we can scale onto large systems using ActiveMQ.

We have not tested scalability.

Setting up a network of brokers is problematic. The best thing is to do master-slave with a cold backup.

We have around 300 applications for the solution.

My company has more than 1000 users for the solution.

We did not encounter many scalability issues.

We have not encountered any scalability issues.

We have not yet encountered any scalability issues. Currently, we are receiving 1000 messages per second (on an average).

We did have scalability issues.

The documentation is very good. Since this is a widely used product, there are plenty of good examples of how to solve various tasks. We have not used any other technical support.

There were no scalability issues up to the point when I was involved in the project.

There have been no issues with scalability, but we had a pretty low message throughput.

We did have scalability issues. It does not scale out well.

The only issue we had concerned the practical limit of 2000 messages per broker, per second. The next step, which is multiplying brokers, worked well though.