You go for a run, and when you're done, your buddy, adidas Running, will tell you how you did. Behind the scenes there is a dedicated team of engineers relying on RabbitMQ.
We are proud to announce that three members of the CloudAMQP team will be speaking during the RabbitMQ Summit. Here is a summary of our talks and the time slots not to miss out on!
New to Message Queueing? In need of a crash course before the RabbitMQ Summit? CloudAMQP and Erlang Solutions have just the right meetup for you!
We're here to introduce you to LavinMQ, the new lightweight, resource efficient, easy-to-use message broker that is built to be faster and more approachable than existing options.
RabbitMQ has some built-in exchanges and some that are enabled via a plugin. Fanout exchange is built in to RabbitMQ and can be used to route one message to multiple users. Use a fanout exchange when you wish to broadcast data to multiple places.
In RabbitMQ, messages are published to an exchange and, depending on the type of exchange, the message gets routed to one or more queues. This blog post will be focusing on the Direct Exchange in RabbitMQ.
Need powerful routing capabilities and reliable message deliveries? Topic exchange is a built-in exchange in RabbitMQ, enabling the use of wildcards in the binding key.
Frontiers has made it its mission to make scientific publications free to access and available for everyone. A quest in which RabbitMQ plays an important role behind the scenes.
Multiple queues in our broker have a lot of messages. We tried to remove the piled-up messages by purging the queue, but only messages in a ready state got deleted. There are still queues with messages that are in an unacked state. How could these be deleted?
There seems to be two options available for “delivery mode” in AMQP, namely non-persistent and persistent. What does this actually mean?