RabbitMQ Messaging & Async Systems · 课时

用于路由的直连交换器

学习如何根据路由键使用直连交换器进行精确的消息路由，将消息发送到指定队列进行定向处理。

第 2 / 4 课11 个步骤

用于路由的直连交换器 是 CoddyKit 上的免费 RabbitMQ Messaging & Async Systems 课时。这是第 2 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 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 — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 11
课程: 44

免费开始学习查看完整课程

常见问题解答

「用于路由的直连交换器」课时是免费的吗？

是的 — 「用于路由的直连交换器」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 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 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 4 节。

「用于路由的直连交换器」课时需要多长时间？

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

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

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

此课程中的所有课时

← 返回 RabbitMQ Messaging & Async Systems