Red Hat AMQ Previous Solutions

RH
DevOps Solution Architect at Helvetia Versicherungen

We were previously using a different asynchronous integration technology, not Kafka, which was IBM MQ. The reason that we switched was that we needed the new technology. Since we were running on an open-shift Kubernetes infrastructure and already Red Hat customers, AMQ Streams was the best fit for our requirements.

View full review »
MS
Sr. Enterprise Architect at a tech services company with 501-1,000 employees

We do use open-source versions of the same solutions, such as Kafka, for other implementations and commercial products. For example, we use AWS and Kafka, but not for governmental projects. For the government, we only use AMQ.

It is helpful that we are able to switch between AMQ and Kafka. That is a good feature to have. Most of these products have the asynchronous messaging capability, so that is not something that makes a product stand out.

For AMQ, what stands out for me are the different offerings that it has. For example, it is very cost-effective compared to other solutions, such as Confluence.

View full review »
CB
Solution Architect at Vlaanderen connect.

Prior to this solution, we used HornetQ. It is no longer supported, which is why we switched to this solution.

View full review »
Buyer's Guide
Message Queue (MQ) Software
March 2024
Find out what your peers are saying about Red Hat, Apache, VMware and others in Message Queue (MQ) Software. Updated: March 2024.
765,386 professionals have used our research since 2012.