Привязки между обменниками
Научитесь связывать обменники друг с другом, создавая сложные цепочки маршрутизации и схемы разветвления сообщений. Создавайте детализированные потоки сообщений в своей системе.
«Привязки между обменниками» — бесплатный урок RabbitMQ Messaging & Async Systems на CoddyKit. Это урок 2 из 4. Ты можешь прочитать весь урок бесплатно ниже — а потом практиковать его прямо в браузере с встроенным редактором кода и ИИ-репетитором 24/7. Это часть пути обучения 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.
Часто задаваемые вопросы
Урок «Привязки между обменниками» бесплатный?
Да — полный текст урока «Привязки между обменниками» бесплатно доступен здесь в веб-версии. Чтобы практиковать его интерактивно (встроенный редактор кода и ИИ-репетитор 24/7) и разблокировать остальной курс RabbitMQ Messaging & Async Systems, подпишись на CoddyKit PRO. Курс RabbitMQ Messaging & Async Systems содержит 4 уроков всего.
Чему я научусь в уроке «Привязки между обменниками»?
Научитесь связывать обменники друг с другом, создавая сложные цепочки маршрутизации и схемы разветвления сообщений. Создавайте детализированные потоки сообщений в своей системе. Ты практикуешь RabbitMQ Messaging & Async Systems с помощью реального кода, который запускаешь прямо в браузере, и ИИ-репетитор 24/7 отвечает на твои вопросы во время урока.
Нужен ли мне опыт, чтобы начать RabbitMQ Messaging & Async Systems?
Предыдущий опыт не требуется. RabbitMQ Messaging & Async Systems на CoddyKit структурирован для всех уровней — от новичков до продвинутых, поэтому ты можешь начать отсюда или с самого начала и учиться в своем темпе. Это урок 2 из 4.
Сколько времени занимает урок «Привязки между обменниками»?
Большинство уроков CoddyKit занимают около 5–10 минут. Каждый из них компактный и интерактивный, поэтому ты постоянно делаешь прогресс и продолжаешь с того же места в веб-версии и приложении.
Можно ли писать и запускать код в этом уроке RabbitMQ Messaging & Async Systems?
Да. Каждый урок RabbitMQ Messaging & Async Systems включает встроенный редактор кода, поэтому ты пишешь и запускаешь реальный код прямо в браузере и получаешь моментальную обратную связь от AI — локальная установка не требуется.
Все уроки этого курса
- Подробно об обменнике Headers
- Привязки между обменниками
- Обменники недоставленных сообщений (DLX)
- Альтернативные обмены для ненаправляемых сообщений