"ActiveMQ is very lightweight and quick."
"This solution has improved and influenced the communication between different applications, then standardized that communication."
"Offers good performance as well as scalability and stability."
"The solution is very stable."
"The solution can scale well."
"The solution is stable."
"The solution allows one to easily configure an IBM MQQueueManager."
"It is useful for exchanging information between applications."
"IBM is still adding some features and coding some other systems on the security end. However, it has the most security features I've seen in a communication solution. Security is the most important thing for our purposes."
"From the TPS point of view, it's like 100,000 transactions that need to be admitted from different devices and also from the different minor small systems. Those are best fit for Kafka. We have used it on the customer side, and we thought of giving a try to ActiveMQ, but we have to do a lot of performance tests and approval is required before we can use it for this scale."
"I would like to see message duplication included."
"It's not always easy for applications to connect to IBM MQ, but I think it's fine in general."
"The licensing fees should be more cost-effective so that we can better pitch the product to our clients. With the pricing as it is, they tend to move away from IBM products."
"There are things within the actual product itself that can be improved, such as limitations on message length, size, etc. There is no standardized message length outside of IBM. Each of the implementations of the MQ series or support of that functionality varies between various suppliers, and because of that, it is very difficult to move from one to the other. We have IBM MQ, but we couldn't use it because the platform that was speaking to MQ didn't support the message length that was standard within IBM MQ. So, we had to use a different product to do exactly the same thing. So, perhaps, there could be more flexibility in the standards around the message queue. If we had been able to increase the message queue size within the IBM MQ implementation, we wouldn't have had to go over to another competing product because the system that was using MQ messaging required the ability to hold messages that were far larger than the IBM MQ standard. So, there could be a bit more flexibility in the structuring. It has as such nothing to do with the IBM implementation of MQ. It is just that the standard that is being put out onto the market doesn't actually stipulate those types of things."
"The main issue we are having with the solution is due to the connection dropouts which have been going on for a long time now."
"There are many complications with IBM MQ servers."
"I don’t like legacy view of MQ."
"There could be a better front-end GUI interface for us, where we can see things more easily."
ActiveMQ is ranked 4th in Message Queue (MQ) Software with 1 review while IBM MQ is ranked 1st in Message Queue (MQ) Software with 26 reviews. ActiveMQ is rated 10.0, while IBM MQ is rated 8.0. The top reviewer of ActiveMQ writes "Lightweight and quick solution for microservices intercommunication". On the other hand, the top reviewer of IBM MQ writes "Reliable and stable software with good integration but the file transfer process needs improvement". ActiveMQ is most compared with Apache Kafka, VMware RabbitMQ, Anypoint MQ, Red Hat AMQ and PubSub+ Event Broker, whereas IBM MQ is most compared with Apache Kafka, VMware RabbitMQ, Anypoint MQ, PubSub+ Event Broker and Amazon SQS.
See our list of best Message Queue (MQ) Software vendors.
We monitor all Message Queue (MQ) Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
From my Experience so far i will go for RabbitMQ its rock solid and robust with a simple learning curve. Its free and has great documentation available