RabbitMQ Messaging & Async Systems · Lección

Bindings entre exchanges

Aprenda a vincular exchanges con otros exchanges para crear cadenas de enrutamiento sofisticadas y patrones de distribución de mensajes. Construya flujos de mensajes complejos en su sistema.

Lección 2 de 411 pasos

Bindings entre exchanges es una lección gratuita de RabbitMQ Messaging & Async Systems en CoddyKit. Esta es la lección 2 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de RabbitMQ Messaging & Async Systems, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de RabbitMQ Messaging & Async Systems incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

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.
Gratis para empezar

Aprende RabbitMQ Messaging & Async Systems con un tutor de IA — gratis

Escribe y ejecuta código real en tu navegador, obtén ayuda instantánea de un tutor de IA disponible 24/7 y continúa donde lo dejaste en la web o en la aplicación.

Cursos
11
Lecciones
44

Preguntas frecuentes

¿La lección «Bindings entre exchanges» es gratis?

Sí — el texto completo de «Bindings entre exchanges» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de RabbitMQ Messaging & Async Systems, actualiza a CoddyKit PRO. El curso de RabbitMQ Messaging & Async Systems incluye 4 lecciones en total.

¿Qué aprenderé en «Bindings entre exchanges»?

Aprenda a vincular exchanges con otros exchanges para crear cadenas de enrutamiento sofisticadas y patrones de distribución de mensajes. Construya flujos de mensajes complejos en su sistema. Practicas RabbitMQ Messaging & Async Systems con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar RabbitMQ Messaging & Async Systems?

No se requiere experiencia previa. RabbitMQ Messaging & Async Systems en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 2 de 4.

¿Cuánto tiempo toma la lección «Bindings entre exchanges»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de RabbitMQ Messaging & Async Systems?

Sí. Cada lección de RabbitMQ Messaging & Async Systems incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

  1. Exchange Headers en profundidad
  2. Bindings entre exchanges
  3. Exchanges de mensajes no entregables (DLX)
  4. Exchanges alternativos para mensajes no enroutables
← Volver a RabbitMQ Messaging & Async Systems