For use cases for Red Hat AMQ, let's take banking purposes. This depends upon the firm or the service or product company. For example, let's take HDFC Bank or any other bank. Whenever a customer deposits some money, they get some notification or alert. Second, when a customer withdraws some amount, they receive alerts in the form of SMS or email, or maybe both. A different example would be a logistics or courier company such as FedEx, which is one of the biggest courier companies in the world. I actually deployed that application in that environment and now it is running successfully.
We just started working with Red Hat AMQ. We selected it as the ESB (Enterprise Service Bus) platform for a new airport project. I manage the entire Master System Integration (MSI) project for one of the new airports.
Sr. Enterprise Architect at a tech services company with 501-1,000 employees
Real User
Top 20
Nov 14, 2022
Red Hat AMQ is a platform for asynchronous messaging and underneath, under the hood, it implements Apache Kafka and Active MQ. They employ two, open-source technologies to implement different cases of asynchronous messaging and they're giving kind of a unified integrated interface to both of them.
Sr. Enterprise Architect at a tech services company with 501-1,000 employees
Real User
Top 20
Dec 19, 2021
When we started with Red Hat, we were using AMQ for asynchronous messaging between different applications. We began using 3scale and Fuse but these days, these solutions are packaged as one product called Red Hat Integration. They are bundled and you cannot acquire them separately. Now that this is the case, we use the entire package. Vaguely, Red Hat AMQ is a wrapper over Apache Kafka and ActiveMQ, made and supported by Red Hat. There are plenty of use cases. Essentially, we use it for whatever use case you can think of for asynchronous messaging. As an example, it is responsible for populating data lakes with relevant data.
DevOps Solution Architect at Helvetia Versicherungen
Real User
Sep 1, 2021
Our main use cases are data synchronization between systems, real-time data synchronization, and event-driven microservices. It is important to us that Red Hat Integration includes transformation, routing, connectors, and a distribution of Apache Kafka, all built to run on Kubernetes. This is one of the core use cases that we are implementing. We have a hybrid environment, where we have on-premise and cloud technologies in our company as well as synchronous and asynchronous integration needs. This is a key component why we choose the technologies that we choose. For us, it is a very valid use case to be operating in this area.
Sr. Enterprise Architect at a tech services company with 501-1,000 employees
Real User
Top 20
Jun 3, 2021
Specifically, the system performs long-running queries. We needed to find a mechanism for messaging, and that was AMQ. Underneath all of this technology, it's a combination of Apache Kafka and ActiveMQ, which are two different mechanisms of messaging that could be used for different use cases whenever it's needed. AMQ is a combination of two products, Apache Kafka and ActiveMQ, and designed into a new product that basically gives users the opportunity to work with both of them on one product.
We use this solution for message queuing. We have been having a great deal of trouble with this solution. However, I have to point out that I do not really trust our infrastructure, as I have just discovered that it is worthless. This leaves us with the question as to which degree these problems are AMQ's or our own.
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).
For use cases for Red Hat AMQ, let's take banking purposes. This depends upon the firm or the service or product company. For example, let's take HDFC Bank or any other bank. Whenever a customer deposits some money, they get some notification or alert. Second, when a customer withdraws some amount, they receive alerts in the form of SMS or email, or maybe both. A different example would be a logistics or courier company such as FedEx, which is one of the biggest courier companies in the world. I actually deployed that application in that environment and now it is running successfully.
We just started working with Red Hat AMQ. We selected it as the ESB (Enterprise Service Bus) platform for a new airport project. I manage the entire Master System Integration (MSI) project for one of the new airports.
We use AMQ's event-driven architecture to exchange messages, and I can connect the AMQ Broker through various integrations.
I primarily use Red Hat AMQ for asynchronous communication and ticketing.
Red Hat AMQ is a platform for asynchronous messaging and underneath, under the hood, it implements Apache Kafka and Active MQ. They employ two, open-source technologies to implement different cases of asynchronous messaging and they're giving kind of a unified integrated interface to both of them.
When we started with Red Hat, we were using AMQ for asynchronous messaging between different applications. We began using 3scale and Fuse but these days, these solutions are packaged as one product called Red Hat Integration. They are bundled and you cannot acquire them separately. Now that this is the case, we use the entire package. Vaguely, Red Hat AMQ is a wrapper over Apache Kafka and ActiveMQ, made and supported by Red Hat. There are plenty of use cases. Essentially, we use it for whatever use case you can think of for asynchronous messaging. As an example, it is responsible for populating data lakes with relevant data.
Our main use cases are data synchronization between systems, real-time data synchronization, and event-driven microservices. It is important to us that Red Hat Integration includes transformation, routing, connectors, and a distribution of Apache Kafka, all built to run on Kubernetes. This is one of the core use cases that we are implementing. We have a hybrid environment, where we have on-premise and cloud technologies in our company as well as synchronous and asynchronous integration needs. This is a key component why we choose the technologies that we choose. For us, it is a very valid use case to be operating in this area.
Specifically, the system performs long-running queries. We needed to find a mechanism for messaging, and that was AMQ. Underneath all of this technology, it's a combination of Apache Kafka and ActiveMQ, which are two different mechanisms of messaging that could be used for different use cases whenever it's needed. AMQ is a combination of two products, Apache Kafka and ActiveMQ, and designed into a new product that basically gives users the opportunity to work with both of them on one product.
We use this solution for message queuing. We have been having a great deal of trouble with this solution. However, I have to point out that I do not really trust our infrastructure, as I have just discovered that it is worthless. This leaves us with the question as to which degree these problems are AMQ's or our own.