Persistent Messages & Queues

Imagine your RabbitMQ broker suddenly restarts. What happens to the messages and queues you've set up?

By default, many things are temporary. If your broker crashes or restarts, non-persistent messages and non-durable queues might be lost forever. This is where persistence comes in.

Persistence ensures that critical data—your queues and messages—survive broker restarts, making your messaging system robust and reliable.

The first step to reliability is making your queues durable. A durable queue will survive a RabbitMQ broker restart.

When you declare a queue, you pass a durable parameter. Setting this to true tells RabbitMQ to save the queue's definition to disk.

• Durable: Queue definition saved; survives restarts.
• Non-durable: Queue definition lost on restart.

Remember, once a queue is declared durable (or not), you can't change its durability later without deleting and re-creating it.