RabbitMQ Messaging & Async Systems · レッスン

柔軟なルーティング向け Topic Exchange

ワイルドカードマッチングを使った複雑なルーティングパターンに対応する Topic Exchange を習得します。柔軟でスケーラブルなメッセージルーティングトポロジーを設計します。

レッスン 3/411 ステップ

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

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

Topic Exchange: Flexible Routing

Welcome to the Topic Exchange! This exchange type offers the most flexible message routing, letting you send messages to queues based on complex patterns.

Unlike the simple Fanout or direct-match Direct exchange, Topic exchanges use special wildcards in routing keys to match messages dynamically.

Understanding Topic Routing Keys

With a Topic exchange, routing keys aren't exact matches. They are strings made of words separated by dots (.), much like parts of a filename or URL.

Example: animal.rabbit.fast
Example: log.error.database

Each word provides a level of detail, allowing for hierarchical routing.

The Single-Word Wildcard: `*`

The asterisk (*) wildcard matches exactly one word in a routing key segment.

Binding key: animal.*.fast matches animal.rabbit.fast
Binding key: animal.*.fast does not match animal.dog.lazy.fast (too many words)
Binding key: *.error.* matches log.error.database

It's great for matching a specific position in the key.

The Zero-or-More Wildcard: `#`

The hash (#) wildcard matches zero or more words in a routing key. It's much more powerful than *.

Binding key: log.# matches log.error, log.info.web, log.debug.cache.entry
Binding key: animal.# matches animal.rabbit, animal.cat.sleepy

Use # to capture all messages that start with a certain pattern.

Producer: Declaring Topic Exchange

First, our producer needs to declare the Topic exchange. The type is simply "topic".

Try running this snippet to set up the exchange:

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

public class TopicProducerSetup {
    private static final String EXCHANGE_NAME = "topic_logs";

    public static void main(String[] argv) throws Exception {
        ConnectionFactory factory = new ConnectionFactory();
        factory.setHost("localhost"); // Connect to local RabbitMQ
        try (Connection connection = factory.newConnection();
             Channel channel = connection.createChannel()) {

            channel.exchangeDeclare(EXCHANGE_NAME, "topic");
            System.out.println("Topic exchange '" + EXCHANGE_NAME + "' declared.");
        }
    }
}

Producer: Sending Messages

Now, let's send some messages using different routing keys. The exchange will use these keys to decide which queues receive the messages.

Notice how the keys are dot-separated, allowing for detailed categories.

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

public class TopicMessageSender {
    private static final String EXCHANGE_NAME = "topic_logs";

    public static void main(String[] argv) throws Exception {
        ConnectionFactory factory = new ConnectionFactory();
        factory.setHost("localhost");
        try (Connection connection = factory.newConnection();
             Channel channel = connection.createChannel()) {

            channel.exchangeDeclare(EXCHANGE_NAME, "topic");

            sendMessage(channel, "animal.rabbit.fast", "A fast rabbit runs.");
            sendMessage(channel, "animal.cat.sleepy", "A sleepy cat naps.");
            sendMessage(channel, "log.error.db", "Database connection failed!");
            sendMessage(channel, "log.info.web", "User logged in.");

            System.out.println("Sent various topic messages.");
        }
    }

    private static void sendMessage(Channel channel, String routingKey, String message) throws Exception {
        channel.basicPublish(EXCHANGE_NAME, routingKey, null, message.getBytes(StandardCharsets.UTF_8));
        System.out.println(" [x] Sent '" + routingKey + ":'" + message + "'");
    }
}

Consumer: Binding with `*`

Consumers bind their queues to the Topic exchange using binding keys that can contain wildcards. This consumer uses *.orange.*.

It will receive messages like animal.orange.fast but not fruit.apple.sweet or animal.orange.

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

public class TopicConsumerOrange {
    private static final String EXCHANGE_NAME = "topic_logs";

    public static void main(String[] argv) throws Exception {
        ConnectionFactory factory = new ConnectionFactory();
        factory.setHost("localhost");
        Connection connection = factory.newConnection();
        Channel channel = connection.createChannel();

        channel.exchangeDeclare(EXCHANGE_NAME, "topic");
        String queueName = channel.queueDeclare().getQueue();

        String bindingKey = "*.orange.*"; // Matches e.g., 'animal.orange.fast'
        channel.queueBind(queueName, EXCHANGE_NAME, bindingKey);
        System.out.println(" [x] Waiting for messages matching: '" + bindingKey + "'");

        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 -> {});
    }
}

Consumer: Binding with `#`

This consumer uses the log.# binding key. This means it will receive all messages whose routing key starts with log., regardless of how many words follow.

This is extremely useful for systems like logging, where you might want a 'catch-all' listener for a category.

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

public class TopicConsumerLogs {
    private static final String EXCHANGE_NAME = "topic_logs";

    public static void main(String[] argv) throws Exception {
        ConnectionFactory factory = new ConnectionFactory();
        factory.setHost("localhost");
        Connection connection = factory.newConnection();
        Channel channel = connection.createChannel();

        channel.exchangeDeclare(EXCHANGE_NAME, "topic");
        String queueName = channel.queueDeclare().getQueue();

        String bindingKey = "log.#"; // Matches e.g., 'log.error.db', 'log.info.web'
        channel.queueBind(queueName, EXCHANGE_NAME, bindingKey);
        System.out.println(" [x] Waiting for messages matching: '" + bindingKey + "'");

        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 -> {});
    }
}

Topic Exchange Use Cases

Topic exchanges shine in scenarios requiring flexible and hierarchical routing:

Logging Systems: Route logs based on severity, source, and component (e.g., app.error.auth, app.info.payment).
Real-time Data Streams: Filter sensor data (e.g., sensor.room1.temp, sensor.room2.humidity).
Content Distribution: Deliver news articles to subscribers interested in specific categories or regions.

They provide fine-grained control over message flow.

Topic Routing Challenge

Consider the following messages and binding keys. Which messages will be delivered to a queue bound with the key animal.*.#.fast?

対話的なレッスンで答える

Recap: Topic Exchange Power

You've mastered the Topic exchange! It's an incredibly powerful tool for building flexible and scalable messaging architectures.

Uses dot-separated routing keys.
* matches exactly one word.
# matches zero or more words.
Ideal for logging, real-time analytics, and content filtering.

By using wildcards, you can create sophisticated routing rules to ensure messages go exactly where they're needed.

無料で開始

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

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

コース: 11
レッスン: 44

無料で学習を始めるコース全体を表示

よくある質問

「柔軟なルーティング向け Topic Exchange」レッスンは無料ですか？

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

「柔軟なルーティング向け Topic Exchange」で何を学びますか？

ワイルドカードマッチングを使った複雑なルーティングパターンに対応する Topic Exchange を習得します。柔軟でスケーラブルなメッセージルーティングトポロジーを設計します。ブラウザで直接実行するハンズオンコードでRabbitMQ Messaging & Async Systemsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

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

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

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

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

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

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

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

← RabbitMQ Messaging & Async Systemsに戻る