0Pricing
RabbitMQ Messaging & Async Systems · 강의

영속 메시지와 대기열

브로커가 다시 시작되어도 메시지와 대기열을 유지하는 방법을 이해합니다. 변동성이 큰 환경에서도 중요한 데이터가 손실되지 않도록 보장합니다.

영속 메시지와 대기열은(는) CoddyKit의 무료 RabbitMQ Messaging & Async Systems 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 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:

  1. Declare your queue as durable (durable=true).
  2. Send your messages with a persistent delivery mode (MessageProperties.PERSISTENT_TEXT_PLAIN).
  3. 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.

자주 묻는 질문

“영속 메시지와 대기열” 강의는 무료인가요?

네 — “영속 메시지와 대기열” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 RabbitMQ Messaging & Async Systems 강의 전체를 잠금 해제할 수 있습니다. RabbitMQ Messaging & Async Systems 강의에는 총 4개의 강의가 포함되어 있습니다.

“영속 메시지와 대기열”에서 뭘 배우나요?

브로커가 다시 시작되어도 메시지와 대기열을 유지하는 방법을 이해합니다. 변동성이 큰 환경에서도 중요한 데이터가 손실되지 않도록 보장합니다. 브라우저에서 직접 실행하는 실습 코드로 RabbitMQ Messaging & Async Systems을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

RabbitMQ Messaging & Async Systems을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 RabbitMQ Messaging & Async Systems은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.

“영속 메시지와 대기열” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 RabbitMQ Messaging & Async Systems 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 RabbitMQ Messaging & Async Systems 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

  1. 영속 메시지와 대기열
  2. 신뢰성을 위한 퍼블리셔 확인
  3. 소비자 확인 및 재큐잉
  4. 트랜잭션과 발행자 확인 비교
← RabbitMQ Messaging & Async Systems(으)로 돌아가기