We use the solution for the asynchronous call and POPS mechanism.

We use it to achieve what we call asynchronous processing. Asynchronous processing is where applications need to communicate with each other, but they don't need to rely on failures, maybe network failures, or dependencies between them. So how you do it: one application publishes a message to VMware RabbitMQ , and another application will consume that message from VMware RabbitMQ. And so do much, its processing. 

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. 

We can use the solution to move large amounts of data. Most of the functions have to be done manually.

We use VMware RabbitMQ to transfer information from one point to another. 

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.

We use RabbitMQ for tasks that need to communicate in real-time. I have used it as a microservices message broker.

We primarily use the solution for consumers and publishers. It's for messaging and consumer publishing. That's it.

We use the solution on our SaaS platform to speedup and simplify customer access across 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.

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.

I am still comparing RabbitMQ and Kafka, but based upon the information I have gathered RabbitMQ is an awesome tool.

Our primary use case is as a messaging broker between enterprise applications. It makes for reliable and secure communication.

• Transaction processing between microservices
• Message queue integration with Spring and RPC over Rabbit.