Sr. Enterprise Architect at a tech services company with 501-1,000 employees
Real User
2022-11-14T18:47:16Z
Nov 14, 2022
The turnaround of adopting new versions of underlying technologies sometimes is too slow. The solution is always running a number of versions behind the latest version. They need to run plenty of tests and have confidence in the version to give their commercial support for it. If the solution can release new versions quicker, it would be great, because the features are not coming quickly for Red Hat AMQ.
Sr. Enterprise Architect at a tech services company with 501-1,000 employees
Real User
2021-12-19T13:22:00Z
Dec 19, 2021
This product needs better visualization capabilities in general. The toolset should be improved to better support developer productivity. This is a point that would be greatly appreciated. They're moving in the right direction but it needs to improve. The licensing structure is good but it takes a little bit to understand. As such, it should be more clear.
DevOps Solution Architect at Helvetia Versicherungen
Real User
2021-09-01T10:09:00Z
Sep 1, 2021
There are some aspects of the monitoring that could be improved on. There is a tool that is somewhat connected to Kafka called Service Registry. This is a product by Red Hat that I would like to see integrated more tightly.
Sr. Enterprise Architect at a tech services company with 501-1,000 employees
Real User
2021-06-03T22:06:21Z
Jun 3, 2021
AMQ is not offered as a separate offering anymore. It comes only as a part of the Red Hat Integration package. Therefore, if you would like to purchase a specific product, you can't do that. You need to go with a larger package, which is sometimes not desirable. In our case, we actually upgraded this to the bigger package from Red Hat, so this works in our favor.
There are several areas in this solution that need improvement, including clustering multi-nodes and message ordering. There should be better support for having messages be ordered per bucket. Technical support for this solution needs improvement.
To respond to business demands quickly and efficiently, you need a way to integrate the applications and data spread across your enterprise. Red Hat JBoss A-MQ—based on the Apache ActiveMQ open source project—is a flexible, high-performance messaging platform that delivers information reliably, enabling real-time integration and connecting the Internet of Things (IoT).
We are interested in a better monitoring tool for all the messages exchanged. We expect a very good monitoring tool for maintenance.
The product needs to improve its documentation and training.
AMQ could be better integrated with Jira and patch management tools.
Red Hat AMQ's cost could be improved, and it could have better integration.
The turnaround of adopting new versions of underlying technologies sometimes is too slow. The solution is always running a number of versions behind the latest version. They need to run plenty of tests and have confidence in the version to give their commercial support for it. If the solution can release new versions quicker, it would be great, because the features are not coming quickly for Red Hat AMQ.
This product needs better visualization capabilities in general. The toolset should be improved to better support developer productivity. This is a point that would be greatly appreciated. They're moving in the right direction but it needs to improve. The licensing structure is good but it takes a little bit to understand. As such, it should be more clear.
There are some aspects of the monitoring that could be improved on. There is a tool that is somewhat connected to Kafka called Service Registry. This is a product by Red Hat that I would like to see integrated more tightly.
AMQ is not offered as a separate offering anymore. It comes only as a part of the Red Hat Integration package. Therefore, if you would like to purchase a specific product, you can't do that. You need to go with a larger package, which is sometimes not desirable. In our case, we actually upgraded this to the bigger package from Red Hat, so this works in our favor.
There are several areas in this solution that need improvement, including clustering multi-nodes and message ordering. There should be better support for having messages be ordered per bucket. Technical support for this solution needs improvement.