We use the solution for event-driven programming. We have multiple queues and channels to provide scenarios for publishing into containers. You have to communicate the microservices, and consumers consume the services.
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
The use case involves the transferring of messages between services. It includes asynchronous messaging and I also need messages flowing to multiple microservices. In this case, it's basically a fan-out mechanism.
Sr Technical Consultant at a tech services company with 1,001-5,000 employees
Real User
2021-06-26T13:21:21Z
Jun 26, 2021
We use this product for general purpose messaging in cloud-based environments and as an implementation to MTP spec. We are customers of VMware and I'm a senior technical consultant.
I primarily use the solution for research purposes. I've utilized it for my academic studies for comparing HTTPS protocols. RabbitMQ supported the protocols I needed and I've read also that it's one of the most commonly used broker services.
Asynchronous messaging; supporting data integrations between multiple applications on behalf of our many customers. RabbitMQ allows us to elegantly fan-out data to a variable number of subscribers, with almost zero effort.
RabbitMQ is the most popular open source message broker, with more than 35,000 production deployments world-wide. RabbitMQ is lightweight and easy to deploy on premises and in the cloud and runs on all major operating systems. It supports most developer platforms, multiple messaging protocols and can be deployed in distributed and federated configurations to meet high-scale, high-availability requirements.
We use VMware RabbitMQ to transfer information from one point to another.
We can use the solution to move large amounts of data. Most of the functions have to be done manually.
We specifically use the solution for queuing purposes, and it has proven to be fantastic in that aspect.
We use the solution for event-driven programming. We have multiple queues and channels to provide scenarios for publishing into containers. You have to communicate the microservices, and consumers consume the services.
Our primary use case is as a messaging broker between enterprise applications. It makes for reliable and secure communication.
The use case involves the transferring of messages between services. It includes asynchronous messaging and I also need messages flowing to multiple microservices. In this case, it's basically a fan-out mechanism.
We primarily use the solution for consumers and publishers. It's for messaging and consumer publishing. That's it.
We use this product for general purpose messaging in cloud-based environments and as an implementation to MTP spec. We are customers of VMware and I'm a senior technical consultant.
We use the solution on our SaaS platform to speedup and simplify customer access across services.
We use RabbitMQ for tasks that need to communicate in real-time. I have used it as a microservices message broker.
I primarily use the solution for research purposes. I've utilized it for my academic studies for comparing HTTPS protocols. RabbitMQ supported the protocols I needed and I've read also that it's one of the most commonly used broker services.
* Transaction processing between microservices * Message queue integration with Spring and RPC over Rabbit.
Asynchronous messaging; supporting data integrations between multiple applications on behalf of our many customers. RabbitMQ allows us to elegantly fan-out data to a variable number of subscribers, with almost zero effort.