RabbitMQ Messaging & Async Systems · Урок

Обменник Direct для маршрутизации

«Обменник Direct для маршрутизации» — бесплатный урок RabbitMQ Messaging & Async Systems на CoddyKit. Это урок 2 из 4. Ты можешь прочитать весь урок бесплатно ниже — а потом практиковать его прямо в браузере с встроенным редактором кода и ИИ-репетитором 24/7. Это часть пути обучения 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!

Часто задаваемые вопросы

Урок «Обменник Direct для маршрутизации» бесплатный?

Да — полный текст урока «Обменник Direct для маршрутизации» бесплатно доступен здесь в веб-версии. Чтобы практиковать его интерактивно (встроенный редактор кода и ИИ-репетитор 24/7) и разблокировать остальной курс RabbitMQ Messaging & Async Systems, подпишись на CoddyKit PRO. Курс RabbitMQ Messaging & Async Systems содержит 4 уроков всего.

Чему я научусь в уроке «Обменник Direct для маршрутизации»?

Научитесь использовать обменник Direct для точной маршрутизации сообщений на основе ключа маршрутизации. Направляйте сообщения в определённые очереди для целевой обработки. Ты практикуешь RabbitMQ Messaging & Async Systems с помощью реального кода, который запускаешь прямо в браузере, и ИИ-репетитор 24/7 отвечает на твои вопросы во время урока.

Нужен ли мне опыт, чтобы начать RabbitMQ Messaging & Async Systems?

Предыдущий опыт не требуется. RabbitMQ Messaging & Async Systems на CoddyKit структурирован для всех уровней — от новичков до продвинутых, поэтому ты можешь начать отсюда или с самого начала и учиться в своем темпе. Это урок 2 из 4.

Сколько времени занимает урок «Обменник Direct для маршрутизации»?

Большинство уроков CoddyKit занимают около 5–10 минут. Каждый из них компактный и интерактивный, поэтому ты постоянно делаешь прогресс и продолжаешь с того же места в веб-версии и приложении.

Можно ли писать и запускать код в этом уроке RabbitMQ Messaging & Async Systems?

Да. Каждый урок RabbitMQ Messaging & Async Systems включает встроенный редактор кода, поэтому ты пишешь и запускаешь реальный код прямо в браузере и получаешь моментальную обратную связь от AI — локальная установка не требуется.

Все уроки этого курса

← Назад к RabbitMQ Messaging & Async Systems