Speaking about the project or scenario where the solution improved the company's message processing capabilities of your system, I would say that working with microservices, you can allow the interaction between microservices in two different ways. One of the ways is synchronous, and the other one is asynchronous. For synchronous communication, my company uses RabbitMQ when microservices push messages into the queue. Asynchronous communication is used to collect and execute messages from queues. With the microservices in place, my company does not need to deal with the clustering feature. The features associated with microservices are considered to be resilient. Others who plan to use the solution should study the product behavior and the important thing is to be prepared in areas including important infrastructure components. VMware RabbitMQ is not a plug and play product, so there is a need to study about it from the partner and theory, while following the best practices. With most of the products from VMware, users get minimal access to the user interface, but it is enough to deal with the projects we have in our company. I rate the overall tool a ten out of ten.
Overall, I would rate the solution an eight out of ten. If you are starting, you can have RabbitMQ on-prem. If you scale up, you can still maintain on-prem, but with higher availability, maybe a few more nodes. When you are processing extremely high traffic, you can now go to the cloud – AWS and so on. And when you become an enterprise, you now need to look for an enterprise-managed commercial queue. An example is the one offered by IBM.
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.
People who want to use the product must not choose a stretched cluster. They must implement it as two separate clusters. We chose stretched clusters, but it caused some issues for us. Overall, I rate the solution a seven out of ten.
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.
Speaking about the project or scenario where the solution improved the company's message processing capabilities of your system, I would say that working with microservices, you can allow the interaction between microservices in two different ways. One of the ways is synchronous, and the other one is asynchronous. For synchronous communication, my company uses RabbitMQ when microservices push messages into the queue. Asynchronous communication is used to collect and execute messages from queues. With the microservices in place, my company does not need to deal with the clustering feature. The features associated with microservices are considered to be resilient. Others who plan to use the solution should study the product behavior and the important thing is to be prepared in areas including important infrastructure components. VMware RabbitMQ is not a plug and play product, so there is a need to study about it from the partner and theory, while following the best practices. With most of the products from VMware, users get minimal access to the user interface, but it is enough to deal with the projects we have in our company. I rate the overall tool a ten out of ten.
Overall, I would rate the solution an eight out of ten. If you are starting, you can have RabbitMQ on-prem. If you scale up, you can still maintain on-prem, but with higher availability, maybe a few more nodes. When you are processing extremely high traffic, you can now go to the cloud – AWS and so on. And when you become an enterprise, you now need to look for an enterprise-managed commercial queue. An example is the one offered by IBM.
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.
People who want to use the product must not choose a stretched cluster. They must implement it as two separate clusters. We chose stretched clusters, but it caused some issues for us. Overall, I rate the solution a seven out of ten.