RabbitMQ Messaging & Async Systems · レッスン

ルーティング向け Direct Exchange

Routing Key に基づいてメッセージを正確にルーティングする Direct Exchange の使い方を学びます。メッセージを特定のキューに送り、目的に応じて処理します。

レッスン 2/411 ステップ

「ルーティング向け Direct Exchange」はCoddyKit上の無料RabbitMQ Messaging & Async Systemsレッスンです。 これはレッスン2/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはRabbitMQ Messaging & Async Systems学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 RabbitMQ Messaging & Async Systemsコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Introduction to Direct Exchange

Welcome! In this lesson, we'll explore the Direct Exchange in RabbitMQ. It's a powerful tool for sending messages to specific queues based on a routing key.

Think of it like a postal service that delivers letters only to the exact address specified on the envelope.

What is a Routing Key?

A routing key is a string attribute that producers attach to messages. It's essentially an "address" for the message.

  • Producers specify a routing key when publishing.
  • Queues bind to an exchange with one or more routing keys.
  • Messages are delivered to queues whose binding key exactly matches the message's routing key.

How Direct Exchange Works

When a message arrives at a Direct Exchange, it looks at the message's routing key. The exchange then delivers the message to all queues that are bound to it with an identical routing key.

If no queue is bound with that specific routing key, the message is simply discarded by the exchange.

Producer's Role: Sending with Keys

As a producer, you decide the routing key for each message you send. This key determines which consumer (via its bound queue) will receive the message.

This allows for precise control over message delivery, ensuring only relevant consumers get specific types of messages.

Consumer's Role: Binding with Keys

Consumers define their interest in messages by binding their queues to a Direct Exchange using specific routing keys.

A single queue can be bound with multiple routing keys, allowing it to receive messages matching any of those keys.

Code: Producer Setup & Declare

Let's set up a basic producer that uses a Direct Exchange. We'll declare an exchange named "direct_logs" with type "direct".

This code establishes a connection and channel, then declares the exchange.

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

public class DirectProducerSetup {
    private static final String EXCHANGE_NAME = "direct_logs";

    public static void main(String[] argv) throws Exception {
        ConnectionFactory factory = new ConnectionFactory();
        factory.setHost("localhost"); // Assuming RabbitMQ is local

        try (Connection connection = factory.newConnection();
             Channel channel = connection.createChannel()) {

            channel.exchangeDeclare(EXCHANGE_NAME, "direct");
            System.out.println("Exchange '" + EXCHANGE_NAME + "' declared.");

            // In a real app, you'd send messages here
            // For this setup example, we just declare.
        }
    }
}

Code: Producer Sending Message

Now, let's send a message to our "direct_logs" exchange. We'll specify a routing key, for example, "error".

Run this code after ensuring your RabbitMQ server is running. It will publish a message with the specified key.

import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
import java.nio.charset.StandardCharsets;

public class DirectProducerSend {
    private static final String EXCHANGE_NAME = "direct_logs";

    public static void main(String[] argv) throws Exception {
        ConnectionFactory factory = new ConnectionFactory();
        factory.setHost("localhost"); // Assuming RabbitMQ is local

        try (Connection connection = factory.newConnection();
             Channel channel = connection.createChannel()) {

            channel.exchangeDeclare(EXCHANGE_NAME, "direct"); // Ensure exchange exists

            String routingKey = "error";
            String message = "A critical error occurred!";

            channel.basicPublish(EXCHANGE_NAME, routingKey, null, message.getBytes(StandardCharsets.UTF_8));
            System.out.println(" [x] Sent '" + routingKey + ":'" + message + "'");
        }
    }
}

Code: Consumer Setup & Binding

On the consumer side, we'll create a queue and bind it to the "direct_logs" exchange using the routing key "error".

This consumer will only receive messages published with the "error" routing key. Run this consumer first, then the producer.

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

public class DirectConsumerError {
    private static final String EXCHANGE_NAME = "direct_logs";

    public static void main(String[] argv) throws Exception {
        ConnectionFactory factory = new ConnectionFactory();
        factory.setHost("localhost"); // Assuming RabbitMQ is local

        Connection connection = factory.newConnection();
        Channel channel = connection.createChannel();

        channel.exchangeDeclare(EXCHANGE_NAME, "direct");

        String queueName = channel.queueDeclare().getQueue(); // Create a non-durable, exclusive, auto-delete queue
        String bindingKey = "error";
        channel.queueBind(queueName, EXCHANGE_NAME, bindingKey);

        System.out.println(" [*] Waiting for messages with routing key '" + bindingKey + "'. To exit press CTRL+C");

        DeliverCallback deliverCallback = (consumerTag, delivery) -> {
            String message = new String(delivery.getBody(), "UTF-8");
            System.out.println(" [x] Received '" + delivery.getEnvelope().getRoutingKey() + ":'" + message + "'");
        };
        channel.basicConsume(queueName, true, deliverCallback, consumerTag -> {});
    }
}

Multiple Bindings & Use Cases

A single queue can bind to the same Direct Exchange with multiple routing keys. For instance, a "critical alerts" queue might bind to both "error" and "warning" keys to receive both types of messages.

Direct exchanges are perfect for scenarios like:

  • Distributing logs based on severity (e.g., info, warn, error).
  • Routing internal system events to specific processing modules.
  • Targeting updates to particular user segments.

Quick Check: Direct Routing

Consider a Direct Exchange named "my_exchange".

  • Queue A is bound with routing key "report".
  • Queue B is bound with routing key "alert".
  • Queue C is bound with routing keys "report" and "update".

A producer sends a message to "my_exchange" with the routing key "report".

Recap: Direct Exchange

Great job! You've learned about the Direct Exchange in RabbitMQ.

  • It routes messages based on an exact match of the routing key.
  • Producers attach a routing key to each message.
  • Consumers bind their queues to the exchange with specific routing keys to receive relevant messages.
  • This pattern allows for precise, targeted message delivery.

Next, we'll explore the Fanout Exchange, which broadcasts messages to all bound queues, regardless of routing key!

無料で開始

AI チューターと学ぶ RabbitMQ Messaging & Async Systems — 無料

ブラウザでリアルコードを書いて実行し、24/7 の AI チューターから瞬時にサポートを受け、ウェブまたはアプリで続きから学習できます。

コース
11
レッスン
44

よくある質問

「ルーティング向け Direct Exchange」レッスンは無料ですか?

はい。「ルーティング向け Direct Exchange」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し(組み込みコードエディタと24時間対応のAIチューター)、RabbitMQ Messaging & Async Systemsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 RabbitMQ Messaging & Async Systemsコースには全4レッスンが含まれています。

「ルーティング向け Direct Exchange」で何を学びますか?

Routing Key に基づいてメッセージを正確にルーティングする Direct Exchange の使い方を学びます。メッセージを特定のキューに送り、目的に応じて処理します。 ブラウザで直接実行するハンズオンコードでRabbitMQ Messaging & Async Systemsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

RabbitMQ Messaging & Async Systemsを始めるのに経験は必要ですか?

事前経験は必要ありません。CoddyKitのRabbitMQ Messaging & Async Systemsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン2/4です。

「ルーティング向け Direct Exchange」レッスンにはどのくらい時間がかかりますか?

ほとんどのCoddyKitレッスンは約5~10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このRabbitMQ Messaging & Async Systemsレッスンでコードを書いて実行できますか?

はい。すべてのRabbitMQ Messaging & Async Systemsレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

  1. Pub/Sub 向け Fanout Exchange
  2. ルーティング向け Direct Exchange
  3. 柔軟なルーティング向け Topic Exchange
  4. Default Exchangeと暗黙的なBinding
← RabbitMQ Messaging & Async Systemsに戻る