RabbitMQ Messaging & Async Systems · 课时

持久化消息与队列

了解如何将消息和队列设为持久化，使其能够在代理重启后保留，确保关键数据即使在不稳定的环境中也不会丢失。

持久化消息与队列 是 CoddyKit 上的免费 RabbitMQ Messaging & Async Systems 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 RabbitMQ Messaging & Async Systems 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 RabbitMQ Messaging & Async Systems 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Persistence Matters

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.

Making Queues Durable

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.

Code: Declaring a Durable Queue

Here's how you declare a durable queue in Java. Notice the true for the second parameter in queueDeclare.

Try running this! Even if you stop and restart RabbitMQ, this queue named 'my_durable_queue' will still be there.

import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;

public class DeclareDurableQueue {
  private final static String QUEUE_NAME = "my_durable_queue";

  public static void main(String[] argv) throws Exception {
    ConnectionFactory factory = new ConnectionFactory();
    factory.setHost("localhost");
    try (Connection connection = factory.newConnection();
         Channel channel = connection.createChannel()) {
      
      // Declare a durable queue
      channel.queueDeclare(QUEUE_NAME, true, false, false, null);
      System.out.println("Queue '" + QUEUE_NAME + "' declared as durable.");
    }
  }
}

Understanding Message Persistence

Even if a queue is durable, messages sent to it are not automatically saved to disk. For messages to survive a broker restart, they must also be marked as persistent.

When a message is persistent, RabbitMQ writes it to disk as soon as it's received by the broker, before delivering it to consumers.

This ensures that if the broker goes down, the message can be recovered from disk when the broker restarts.

Code: Sending a Persistent Message

To send a persistent message, you need to set the deliveryMode to 2 (which means persistent) or use MessageProperties.PERSISTENT_TEXT_PLAIN for convenience.

Run this producer, then try to restart your RabbitMQ broker. After restarting, if you run a consumer, you should still receive this message!

import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
import com.rabbitmq.client.MessageProperties;

public class SendPersistentMessage {
  private final static String QUEUE_NAME = "my_durable_queue";

  public static void main(String[] argv) throws Exception {
    ConnectionFactory factory = new ConnectionFactory();
    factory.setHost("localhost");
    try (Connection connection = factory.newConnection();
         Channel channel = connection.createChannel()) {
      
      // Ensure the queue is durable first
      channel.queueDeclare(QUEUE_NAME, true, false, false, null);

      String message = "Hello, persistent world!";
      // Mark message as persistent
      channel.basicPublish("", QUEUE_NAME, 
                           MessageProperties.PERSISTENT_TEXT_PLAIN, 
                           message.getBytes("UTF-8"));
      System.out.println(" [x] Sent '" + message + "'");
    }
  }
}

The Persistence 'Gotcha'

It's crucial to understand a subtlety: even with durable queues and persistent messages, a message can still be lost.

This happens if the message is in transit from the producer to the broker, or if it has arrived at the broker but hasn't yet been flushed to disk, and the broker crashes at that exact moment.

For true reliability, where you know the broker has definitely received and saved your message, you need Publisher Confirms. We'll cover this in a future lesson!

When to Use Persistence

Persistence isn't free; it adds overhead because RabbitMQ has to write data to disk. So, when should you use it?

Critical Tasks: Orders, financial transactions, user sign-ups.
Long-running Processes: Image processing, video encoding.
System Integration: Ensuring data transfer between services is reliable.

If message loss is acceptable (e.g., real-time monitoring data that's quickly outdated), you can skip persistence for better performance.

Performance Impact

Writing data to disk takes more time than keeping it in memory. Therefore, enabling persistence for queues and messages will reduce your message throughput (messages per second).

Durable Queues: Minor impact, as it's just the queue definition.
Persistent Messages: More significant impact, as each message is written.

It's a trade-off: higher reliability versus higher performance. Always choose persistence for messages that you absolutely cannot afford to lose.

Recap: Persistence in Action

Let's briefly review the steps for a fully persistent setup:

Declare your queue as durable (durable=true).
Send your messages with a persistent delivery mode (MessageProperties.PERSISTENT_TEXT_PLAIN).
For ultimate reliability (knowing the broker received it), combine with Publisher Confirms (covered later).

Quick Check: Durable Queues

You want to ensure that a queue and its messages survive if the RabbitMQ broker restarts. Which of the following is absolutely necessary for the queue itself to survive a restart?

Recap & Next Steps

Great job! You've learned how to make your RabbitMQ queues and messages persistent, a crucial step towards building reliable messaging systems.

We covered:

The importance of persistence.
How to declare durable queues.
How to send persistent messages.
The performance trade-offs and the 'gotcha' with in-flight messages.

In the next lesson, we'll dive into Publisher Confirms, which provide an even higher level of reliability by ensuring the broker has truly received and processed your messages.

常见问题解答

「持久化消息与队列」课时是免费的吗？

是的 — 「持久化消息与队列」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 RabbitMQ Messaging & Async Systems 课程的其余内容，请升级到 CoddyKit PRO。 RabbitMQ Messaging & Async Systems 课程共包含 4 节课。

「持久化消息与队列」这节课中我会学到什么？

了解如何将消息和队列设为持久化，使其能够在代理重启后保留，确保关键数据即使在不稳定的环境中也不会丢失。你通过在浏览器中直接运行的动手代码来练习 RabbitMQ Messaging & Async Systems，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 RabbitMQ Messaging & Async Systems 需要有经验吗？

无需任何先前经验。CoddyKit 上的 RabbitMQ Messaging & Async Systems 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「持久化消息与队列」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 RabbitMQ Messaging & Async Systems 课中编写并运行代码吗？

能。每节 RabbitMQ Messaging & Async Systems 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 RabbitMQ Messaging & Async Systems