I would recommend using it. The only thing is that RabbitMQ can be used with any programming language, and we can use any web portals. H owever, Anypoint MQ is exclusively for MuleSoft and is not available outside of the MuleSoft platform. Overall, I would rate the solution a nine out of ten.
Packaged App development Senior Analyst at Accenture
Real User
Top 5
2024-03-13T15:23:00Z
Mar 13, 2024
We configure the monitoring and alerting for the RabbitMQ setup. We transfer the message to the designated queue if there are any errors or similar issues. We use a Spring Boot application and microservices for this purpose, making it easy to route the message. If you want to use this solution, you first need to understand the concept of exchange queues. Certain clusters require specific knowledge. The configuration may vary depending on the application type. For instance, the configuration was relatively straightforward in our case with microservices. We only needed to provide authentication and the correct URL. If it ran on a cloud environment, we would provide the instance, username, and password, and the configuration would be handled automatically. It would depend on the language and the specific type of microservice or application for more advanced customization, such as writing code. The solution is easy to use, configure, and install. Overall, I rate the solution an eight or nine out of ten.
I rate VMware RabbitMQ an eight out of ten. You should know how to configure and deploy it on the servers. If they provide good documentation, it will be easier to use.
If you are looking for a queuing system for your application that guarantees insured delivery and ensures single delivery without duplicates, RabbitMQ is the right solution as it provides all these capabilities with ease of use. With RabbitMQ, your application doesn't need to worry about receiving duplicate messages as the solution handles that internally, ensuring that each message goes through a single process for one delivery. I highly recommend the solution and would rate it an eight out of ten.
I am using the latest version of the solution. I'm not sure of the version number. I've used this on multiple projects, and it has proven to be quite useful. I'd rate the solution nine out of ten. It is a very good tool.
I would give the following advice prepare a demo, with the vendor and check if it really applies to their needs. I would rate VMware RabbitMQ a nine out of ten.
Independent Technology Consultant - Financial Softwares at a tech services company with 51-200 employees
Real User
Top 5
2022-01-30T06:33:58Z
Jan 30, 2022
My advice for anybody who is implementing this product is to establish your users and exchanges properly. In general, I'm quite comfortable with RabbitMQ. It satisfies my requirements and the main complaint I have is about the security. I would rate this solution a seven out of ten.
Assistant Student at a retailer with 5,001-10,000 employees
Real User
2021-12-27T19:08:00Z
Dec 27, 2021
We're using a few different versions. It depends on the department. Some departments have the latest, some don't, some use a very old version. I'm using 3.8. We do have plans to make an upgrade. It was a few years ago now when I learned this process of separating publishers versus consumers in terms of messages and communicating between departments. This was the biggest game changer for myself. I'd advise new users study that aspect and understand it. I'd rate the solution at an eight out of ten. It's a very good tool and we use it all the time.
Sr Technical Consultant at a tech services company with 1,001-5,000 employees
Real User
2021-06-26T13:21:21Z
Jun 26, 2021
My advice would be to have the messaging topology mapped out before you deploy to make the process from installation to a functioning solution more efficient. If you start looking at the topology from the revenue perspective, it usually ends up with more iterations to implement the correct topology, whereas if you start off mapping and then install, it's a more efficient way to go about it. I rate this solution an eight out of 10.
CTO, CIO, Chief Architect at a tech services company with 11-50 employees
Real User
2021-01-21T19:16:00Z
Jan 21, 2021
There are many different use cases for each technology, as well as many approaches. So have the architecture team graph and document every solution. Have a few training days to clarify the goal, the solution and the implementation. One of the things we do in our training is to actually create prototypes, the abstract model of our ideal state. This demonstrates exactly what we all need to do. Developers understand more quickly with a model. It flattens their learning curve and they are more productive more quickly. I rate VMware RabbitMQ a ten out of ten.
My advice for anybody who is implementing this product is to learn the concept of message queuing and study the AMQP 0-9-1 protocol. If you study this then you won't have any problem learning the system and working with it. In summary, this is a good product that I will continue to use, and I recommend it. I would rate this solution a seven out of ten.
I would recommend it, but I think there should be a proof of concept for the developer team to get their hands around it and have full control of it before they go into production. I would rate RabbitMQ a seven out of ten. In the next release, I would like for them to improve the UI.
I'm only really using the solution for the purposes of research. I've just installed and am working on the latest version. My interest in the solution is purely academic, so I can't speak to how it would function within an organization. I'd definitely recommend the solution, especially over HTTP in the Nico services platform. I've done my research and have discovered it's two times faster and more commonly used. It's also really easy to use on the Nico services platform because all of the components are in the cloud. I'd rate the solution eight out of ten.
I would recommend that anyone who intends to deploy RabbitMQ on Windows should first consider whether a Linux implementation is a viable option for their situation.
VMware Tanzu is a robust platform tailored for data warehousing, complex analytics, BI applications, and predictive analytics. It excels in scalability, performance, and parallel processing, enhancing data handling efficiency. Users report significant productivity improvements and streamlined operations, making it ideal for comprehensive data solutions.
I would recommend using it. The only thing is that RabbitMQ can be used with any programming language, and we can use any web portals. H owever, Anypoint MQ is exclusively for MuleSoft and is not available outside of the MuleSoft platform. Overall, I would rate the solution a nine out of ten.
We configure the monitoring and alerting for the RabbitMQ setup. We transfer the message to the designated queue if there are any errors or similar issues. We use a Spring Boot application and microservices for this purpose, making it easy to route the message. If you want to use this solution, you first need to understand the concept of exchange queues. Certain clusters require specific knowledge. The configuration may vary depending on the application type. For instance, the configuration was relatively straightforward in our case with microservices. We only needed to provide authentication and the correct URL. If it ran on a cloud environment, we would provide the instance, username, and password, and the configuration would be handled automatically. It would depend on the language and the specific type of microservice or application for more advanced customization, such as writing code. The solution is easy to use, configure, and install. Overall, I rate the solution an eight or nine out of ten.
You should use the solution if you want to store your details in the queue and start taking inputs from the queue. I rate it a nine out of ten.
I rate VMware RabbitMQ an eight out of ten. You should know how to configure and deploy it on the servers. If they provide good documentation, it will be easier to use.
If you are looking for a queuing system for your application that guarantees insured delivery and ensures single delivery without duplicates, RabbitMQ is the right solution as it provides all these capabilities with ease of use. With RabbitMQ, your application doesn't need to worry about receiving duplicate messages as the solution handles that internally, ensuring that each message goes through a single process for one delivery. I highly recommend the solution and would rate it an eight out of ten.
I am using the latest version of the solution. I'm not sure of the version number. I've used this on multiple projects, and it has proven to be quite useful. I'd rate the solution nine out of ten. It is a very good tool.
I would give the following advice prepare a demo, with the vendor and check if it really applies to their needs. I would rate VMware RabbitMQ a nine out of ten.
My advice for anybody who is implementing this product is to establish your users and exchanges properly. In general, I'm quite comfortable with RabbitMQ. It satisfies my requirements and the main complaint I have is about the security. I would rate this solution a seven out of ten.
We're using a few different versions. It depends on the department. Some departments have the latest, some don't, some use a very old version. I'm using 3.8. We do have plans to make an upgrade. It was a few years ago now when I learned this process of separating publishers versus consumers in terms of messages and communicating between departments. This was the biggest game changer for myself. I'd advise new users study that aspect and understand it. I'd rate the solution at an eight out of ten. It's a very good tool and we use it all the time.
My advice would be to have the messaging topology mapped out before you deploy to make the process from installation to a functioning solution more efficient. If you start looking at the topology from the revenue perspective, it usually ends up with more iterations to implement the correct topology, whereas if you start off mapping and then install, it's a more efficient way to go about it. I rate this solution an eight out of 10.
There are many different use cases for each technology, as well as many approaches. So have the architecture team graph and document every solution. Have a few training days to clarify the goal, the solution and the implementation. One of the things we do in our training is to actually create prototypes, the abstract model of our ideal state. This demonstrates exactly what we all need to do. Developers understand more quickly with a model. It flattens their learning curve and they are more productive more quickly. I rate VMware RabbitMQ a ten out of ten.
My advice for anybody who is implementing this product is to learn the concept of message queuing and study the AMQP 0-9-1 protocol. If you study this then you won't have any problem learning the system and working with it. In summary, this is a good product that I will continue to use, and I recommend it. I would rate this solution a seven out of ten.
I would recommend it, but I think there should be a proof of concept for the developer team to get their hands around it and have full control of it before they go into production. I would rate RabbitMQ a seven out of ten. In the next release, I would like for them to improve the UI.
I'm only really using the solution for the purposes of research. I've just installed and am working on the latest version. My interest in the solution is purely academic, so I can't speak to how it would function within an organization. I'd definitely recommend the solution, especially over HTTP in the Nico services platform. I've done my research and have discovered it's two times faster and more commonly used. It's also really easy to use on the Nico services platform because all of the components are in the cloud. I'd rate the solution eight out of ten.
I would recommend that anyone who intends to deploy RabbitMQ on Windows should first consider whether a Linux implementation is a viable option for their situation.