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.

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. 

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.

We use AMQ's event-driven architecture to exchange messages, and I can connect the AMQ Broker through various integrations. 

We are in the early stages of evaluating Red Hat AMQ for an OpenShift container platform because it can provide a very good Kubernetes platform using asynchronous data communication.

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.

I primarily use Red Hat AMQ for asynchronous communication and ticketing.