RabbitMQ Messaging & Async Systems · 课时

交换器之间的绑定

学习将交换器绑定到其他交换器，创建复杂的路由链和消息扇出模式，在系统中构建精细的消息流。

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

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

Why Chain Exchanges?

In RabbitMQ, you've learned how producers send messages to exchanges, which then route them to queues. But what if you need more complex routing?

Sometimes, a message needs to go through multiple "decision points" before reaching its final destination. This is where Exchange-to-Exchange (E2E) bindings come in handy!

Chaining Exchanges Together

Think of E2E bindings as connecting pipelines. Instead of an exchange sending messages directly to a queue, it sends them to another exchange.

The first exchange receives a message.
It routes the message to a second exchange based on its type and the binding.
The second exchange then routes the message further, either to queues or yet another exchange.

This creates powerful routing flows!

Anatomy of an E2E Binding

An E2E binding connects a source exchange to a destination exchange. Messages arriving at the source exchange will be routed to the destination exchange.

Just like exchange-to-queue bindings, E2E bindings also use a routing key. This key determines how messages are routed from the source exchange to the destination exchange, based on the source exchange's type.

Example: Direct to Fanout Chain

Let's consider a practical scenario: You want to route a message to a specific category, and then broadcast it to multiple services interested in that category.

A producer sends a message to a Direct Exchange with a routing key like "alerts.critical".
This Direct Exchange is bound to a Fanout Exchange with the same routing key.
The Fanout Exchange is then bound to several queues, ensuring all services receive the "alerts.critical" message.

Declaring Exchanges for E2E

First, we need to declare our two exchanges: a 'source' Direct exchange and a 'destination' Fanout exchange. The producer will send messages to the 'source' exchange.

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

public class ExchangeDeclarer {
    private static final String SOURCE_EXCHANGE = "my_direct_source";
    private static final String DEST_EXCHANGE = "my_fanout_destination";

    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(SOURCE_EXCHANGE, "direct");
            System.out.println("Declared source direct exchange: " + SOURCE_EXCHANGE);

            channel.exchangeDeclare(DEST_EXCHANGE, "fanout");
            System.out.println("Declared destination fanout exchange: " + DEST_EXCHANGE);

        }
    }
}

Binding Exchanges Together

Now, let's create the actual E2E binding. We'll bind our 'source' direct exchange to our 'destination' fanout exchange. We'll use a routing key "my.route" for this specific binding.

Messages sent to my_direct_source with routing key my.route will be forwarded to my_fanout_destination.

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

public class ExchangeBinder {
    private static final String SOURCE_EXCHANGE = "my_direct_source";
    private static final String DEST_EXCHANGE = "my_fanout_destination";
    private static final String BINDING_KEY = "my.route";

    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 exchanges are declared (or declare them here if not done)
            channel.exchangeDeclare(SOURCE_EXCHANGE, "direct");
            channel.exchangeDeclare(DEST_EXCHANGE, "fanout");

            // Bind source to destination with a routing key
            channel.exchangeBind(DEST_EXCHANGE, SOURCE_EXCHANGE, BINDING_KEY); // Note: bind(destination, source, key)
            System.out.println("Bound " + SOURCE_EXCHANGE + " to " + DEST_EXCHANGE + " with key: " + BINDING_KEY);

        }
    }
}

Sending Messages to the Source

Our producer will send a message to the my_direct_source exchange using the routing key my.route. This message will then be routed to our my_fanout_destination exchange due to the E2E binding.

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

public class E2EProducer {
    private static final String SOURCE_EXCHANGE = "my_direct_source";
    private static final String BINDING_KEY = "my.route";

    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 source exchange is declared
            channel.exchangeDeclare(SOURCE_EXCHANGE, "direct");

            String message = "Hello via E2E binding!";
            channel.basicPublish(SOURCE_EXCHANGE, BINDING_KEY, null, message.getBytes(StandardCharsets.UTF_8));
            System.out.println(" [x] Sent '" + message + "' with routing key '" + BINDING_KEY + "' to " + SOURCE_EXCHANGE);

        }
    }
}

Consuming from the Destination

Finally, a consumer will receive the message. Since my_fanout_destination is a fanout exchange, we'll bind a temporary queue to it. Any message arriving at the fanout exchange (from our E2E binding) will be delivered to this queue.

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

public class E2EConsumer {
    private static final String DEST_EXCHANGE = "my_fanout_destination";

    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(DEST_EXCHANGE, "fanout");

        String queueName = channel.queueDeclare().getQueue();
        channel.queueBind(queueName, DEST_EXCHANGE, ""); // Fanout ignores routing key

        System.out.println(" [*] Waiting for messages in queue '" + queueName + "'. To exit press CTRL+C");

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

Routing Keys and E2E Flow

When a message is routed from a source exchange to a destination exchange via an E2E binding, its original routing key is preserved.

The source exchange uses the binding key of the E2E binding to decide if it should forward the message to the destination exchange. Once forwarded, the destination exchange then uses the message's original routing key (not the E2E binding key) to route it to its own bound queues.

Direct Source: Matches message's routing key exactly to E2E binding key.
Topic Source: Matches message's routing key against E2E binding key (with wildcards).
Fanout Source: Ignores E2E binding key, forwards all messages.

Test Your E2E Knowledge

A Direct Exchange 'Source' is bound to a Fanout Exchange 'Dest' with the routing key "alerts.high".

A producer sends a message to 'Source' with the routing key "alerts.high".

'Dest' is bound to two queues: 'Q1' and 'Q2'.

Which queues will receive the message?

E2E Bindings: Summary

You've explored Exchange-to-Exchange (E2E) bindings, a powerful feature for creating sophisticated message routing paths in RabbitMQ!

E2E bindings allow an exchange to forward messages to another exchange, creating routing chains.
They use a binding key, just like exchange-to-queue bindings, to define the routing logic between exchanges.
The message's original routing key is preserved and used by the destination exchange for further routing to queues.
E2E bindings enable complex patterns like filtering then fanning out, or cascading messages through multiple processing stages.

常见问题解答

「交换器之间的绑定」课时是免费的吗？

是的 — 「交换器之间的绑定」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 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