CODEWITHSUNDEEP
rabbitmq
ScottDPJ
ScottDPJ

Reputation: 443

RabbitMQ Message Lifetime Replay Message

We are currently evaluating RabbitMQ. Trying to determine how best to implement some of our processes as Messaging apps instead of traditional DB store and grab. Here is the scenario. We have a department of users who perform similar tasks. As they submit work to the server applications we would like the server app to send messages back into a notification window saying what was done - to all the users, not just the one submitting the work. This is all easy to do.

The question is we would like these message to live for say 4 hours in the Queue. If a new user logs in or say a supervisor they would get all the messages from the last 4 hours delivered to their notification window. This gives them a quick way to review what has recently happened and what is going on without having to ask others, "have you talked to John?", "Did you email him is itinerary?", etc.

So, how do we publish messages that have a lifetime of x hours from the time they were published AND any new consumers that connect will get all of these messages delivered in chronological order? And preferably the messages just disappear after they have expired from the queue.

Thanks

Upvotes: 1

Views: 2222

Answers (4)

Siraf
Siraf

Reputation: 1292

Consider using the new RabbitMQ Streams feature introduced in v3.9.0 (July 23, 2021). With RabbitMQ Streams you can save all you messages for a given retention time and replay these messages.

Check RabbitMQ Streams Docs

Upvotes: 0

Patrick
Patrick

Reputation: 2790

Queuing messages you do to get a message from one point to the other reliable. So the sender can work independently from the receiver. What you propose is working with a temporary persistent store.

A sql database would fit perfectly, but also a mongodb would work nicely. You drop a document in mongo, give it a ttl and let the database handle the expiration.

http://docs.mongodb.org/master/tutorial/expire-data/

Upvotes: 0

Simrandeep Singh
Simrandeep Singh

Reputation: 547

In addition to the above answer, it would be better to have the application/client publish messages to two queues. Consumer would consume from one of the queues while the other queue can be configured using per queue-message TTL or per message TTL to retain the messages.

Upvotes: 0

pinepain
pinepain

Reputation: 12859

There is Per-Queue Message TTL and Per-Message TTL in RabbitMQ. If I am right you can utilize them for your task.

Upvotes: 2

Related Questions