The most valuable feature is stability. The solution is a pretty stable product because it is an independent installation. Stable product, relying on stable technologies and is pretty quick. Again, we're talking about the messaging services, which are by themselves known for very quick performance, let's say, features. Performance and handling loads of data, as well as... A difference between Red Hat AMQ, let's say, and underlying technologies, you can actually deploy Apache Kafka and Active MQ by themselves and use them. So here, you are deploying those two technologies as part of the set, and there is probably easier handling of which technology will be used for which case.

It's pretty much a Red Hat thing to take the open-source technology, and wrap it up.

The most valuable feature for us is the operator-based automation that is provided by Streams for infrastructure as well as user and topic management. This saves a lot of time and effort on our part to provide infrastructure. For example, the deployment of infrastructure is reduced from approximately a week to a day.

This product is well adopted on the OpenShift platform. For organizations like ours that use OpenShift for many of our products, this is a good feature. The compatibility is good and it is well supported from an OCP perspective.

The official support from Red Hat is effective and responds in a timely manner, which is important to us.

AMQ is highly scalable and performs well. It can process a large volume of messages in one second. AMQ and OpenShift are a good combination.

The solution is very lightweight, easy to configure, simple to manage, and robust since it launched.

Red Hat AMQ's best feature is its reliability.