DevOps Solution Architect at Helvetia Versicherungen
Real User
2021-09-01T10:09:00Z
Sep 1, 2021
I would recommend trying it out. It is quite easy to set up. It takes a bit of knowledge of the Kubernetes stack, but it is something that can easily be tried out. Also, there is an open-source upstream, which is also very helpful. Change Data Capture technology is very important for us because this technology allows us to quickly add streams of data from our databases for processing in our streaming hubs. As one of our main use cases is data synchronization between systems, Change Data Capture is one of the technologies that we use to affect that. We use Change Data Capture technology to access data from legacy systems. We use CDC to access data from legacy systems and provide it within Kafka topics. We are quite happy with this solution. I think it is the best out there. I would give it a nine out of 10, because I don't know if it is the best financially.
We are just customers and end-users. We don't have a business relationship with Red Hat. We are using one of the most recent versions, as in addition, we purchased from Red Hat what's called Red Hat Integration, which includes the licenses for AMQ's latest version. I assume it would be the latest version. Since the solution is no longer separated out, I would advise a company considering the solution to look into the whole package. The package consists of the other products as well, that might not be of use, or will not be needed. A company will need to be aware of this part. I'd also advise companies to be aware of how resources are allocated. An organization must understand how resources are allocated, from the technical point of view. They need to understand what is covered under the subscription. Technical support can help discuss it with them if they have questions. Overall, I'd rate the solution at a nine out of ten.
My advice to anybody who is implementing this solution is to make sure that you get the clustering configuration right and that it actually works, and beware of message ordering problems. Simply, for us, there were a lot of features that did not work properly because of the clustering configuration. Unfortunately, that was not mentioned in the manual, or anywhere else, so we had to find out that certain things simply don't work when you go and cluster and when you scale it out. If I knew for sure that the technology didn't work and that was the cause of our problems then I would rate this product a three out of ten, but I know there are also other factors involved, so I can't really say that it's the technology. I would rate this solution a four out of ten.
I rate Red Hat AMQ 10 out of 10. I recommend AMQ if you are looking for an event-driven messaging solution.
I would recommend Red Hat AMQ for those looking for an industrial product. I'd give it a rating of eight out of ten.
I give the solution an eight out of ten. The solution is maintained by Red Hat.
I would rate this solution an eight out of ten.
I would recommend trying it out. It is quite easy to set up. It takes a bit of knowledge of the Kubernetes stack, but it is something that can easily be tried out. Also, there is an open-source upstream, which is also very helpful. Change Data Capture technology is very important for us because this technology allows us to quickly add streams of data from our databases for processing in our streaming hubs. As one of our main use cases is data synchronization between systems, Change Data Capture is one of the technologies that we use to affect that. We use Change Data Capture technology to access data from legacy systems. We use CDC to access data from legacy systems and provide it within Kafka topics. We are quite happy with this solution. I think it is the best out there. I would give it a nine out of 10, because I don't know if it is the best financially.
We are just customers and end-users. We don't have a business relationship with Red Hat. We are using one of the most recent versions, as in addition, we purchased from Red Hat what's called Red Hat Integration, which includes the licenses for AMQ's latest version. I assume it would be the latest version. Since the solution is no longer separated out, I would advise a company considering the solution to look into the whole package. The package consists of the other products as well, that might not be of use, or will not be needed. A company will need to be aware of this part. I'd also advise companies to be aware of how resources are allocated. An organization must understand how resources are allocated, from the technical point of view. They need to understand what is covered under the subscription. Technical support can help discuss it with them if they have questions. Overall, I'd rate the solution at a nine out of ten.
My advice to anybody who is implementing this solution is to make sure that you get the clustering configuration right and that it actually works, and beware of message ordering problems. Simply, for us, there were a lot of features that did not work properly because of the clustering configuration. Unfortunately, that was not mentioned in the manual, or anywhere else, so we had to find out that certain things simply don't work when you go and cluster and when you scale it out. If I knew for sure that the technology didn't work and that was the cause of our problems then I would rate this product a three out of ten, but I know there are also other factors involved, so I can't really say that it's the technology. I would rate this solution a four out of ten.