Headers Exchange の詳細
Routing Key ではなくヘッダー属性に基づいてメッセージをルーティングする Headers Exchange について学びます。より複雑で動的なルーティングルールを実装します。
「Headers Exchange の詳細」はCoddyKit上の無料RabbitMQ Messaging & Async Systemsレッスンです。 これはレッスン1/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはRabbitMQ Messaging & Async Systems学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 RabbitMQ Messaging & Async Systemsコースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
Headers Exchange: New Routing
Meet the Headers exchange! Unlike Direct or Topic exchanges that use a simple routing_key string, Headers exchanges route messages based on their header attributes.
Think of it as a more flexible way to filter messages, using key-value pairs attached to the message itself.
Routing by Message Headers
When a producer sends a message, it includes a map of key-value pairs (headers). A consumer binds its queue to a Headers exchange with its own set of header rules.
The exchange then compares the message headers to the binding rules to decide where to deliver the message.
Matching Logic: 'all' or 'any'
Headers exchanges use a special argument called x-match in the binding to define the matching logic:
"all": The message's headers must contain all the key-value pairs specified in the binding."any": The message's headers must contain at least one of the key-value pairs specified in the binding.
This gives you powerful control over message delivery!
Producing with Custom Headers
Let's see how a producer adds custom headers to a message. We'll send a simple text message with format: json and type: report headers.
Run this code to send a message:
import com.rabbitmq.client.*;
import java.util.HashMap;
import java.util.Map;
public class HeadersProducer {
private static final String EXCHANGE = "my_headers_exchange";
public static void main(String[] argv) throws Exception {
ConnectionFactory factory = new ConnectionFactory();
factory.setHost("localhost");
try (Connection conn = factory.newConnection();
Channel channel = conn.createChannel()) {
channel.exchangeDeclare(EXCHANGE, "headers");
Map<String, Object> headers = new HashMap<>();
headers.put("format", "json");
headers.put("type", "report"); // Add headers
String msg = "Report Data (JSON)";
AMQP.BasicProperties props = new AMQP.BasicProperties.Builder()
.headers(headers)
.build();
channel.basicPublish(EXCHANGE, "", props, msg.getBytes("UTF-8"));
System.out.println(" [x] Sent: '" + msg + "' with headers: " + headers);
}
}
}Consumer 'All' Match Example
This consumer will only receive messages if all its specified headers (format: json AND type: report) are present in the incoming message.
Run this consumer first, then the producer from the previous scene.
import com.rabbitmq.client.*;
import java.util.HashMap;
import java.util.Map;
public class HeadersConsumerAll {
private static final String EXCHANGE = "my_headers_exchange";
public static void main(String[] argv) throws Exception {
ConnectionFactory factory = new ConnectionFactory();
factory.setHost("localhost");
Connection conn = factory.newConnection();
Channel channel = conn.createChannel();
channel.exchangeDeclare(EXCHANGE, "headers");
String queueName = channel.queueDeclare().getQueue();
Map<String, Object> bindHeaders = new HashMap<>();
bindHeaders.put("x-match", "all");
bindHeaders.put("format", "json");
bindHeaders.put("type", "report"); // Requires both
channel.queueBind(queueName, EXCHANGE, "", bindHeaders);
System.out.println(" [*] Waiting for msgs with ALL: " + bindHeaders);
DeliverCallback dc = (ct, delivery) -> {
String msg = new String(delivery.getBody(), "UTF-8");
System.out.println(" [x] Received '" + msg + "' Headers: " + delivery.getProperties().getHeaders());
};
channel.basicConsume(queueName, true, dc, ct -> {});
}
}Consumer 'Any' Match Example
Now, let's create a consumer that receives messages if any of its specified headers (format: xml OR priority: high) are present.
Run this consumer. Then, try sending messages with different header combinations.
import com.rabbitmq.client.*;
import java.util.HashMap;
import java.util.Map;
public class HeadersConsumerAny {
private static final String EXCHANGE = "my_headers_exchange";
public static void main(String[] argv) throws Exception {
ConnectionFactory factory = new ConnectionFactory();
factory.setHost("localhost");
Connection conn = factory.newConnection();
Channel channel = conn.createChannel();
channel.exchangeDeclare(EXCHANGE, "headers");
String queueName = channel.queueDeclare().getQueue();
Map<String, Object> bindHeaders = new HashMap<>();
bindHeaders.put("x-match", "any");
bindHeaders.put("format", "xml"); // Matches if format is xml
bindHeaders.put("priority", "high"); // OR if priority is high
channel.queueBind(queueName, EXCHANGE, "", bindHeaders);
System.out.println(" [*] Waiting for msgs with ANY: " + bindHeaders);
DeliverCallback dc = (ct, delivery) -> {
String msg = new String(delivery.getBody(), "UTF-8");
System.out.println(" [x] Received '" + msg + "' Headers: " + delivery.getProperties().getHeaders());
};
channel.basicConsume(queueName, true, dc, ct -> {});
}
}More on `x-match` Values
While "all" and "any" are the primary x-match values, you can also omit x-match. If x-match is not provided, it defaults to "all".
Remember that the header values must match exactly. For example, "type": "report" won't match "type": "Report".
When to Use Headers Exchange
Headers exchanges are great for:
- Dynamic Routing: When routing logic changes often without code deployments.
- Complex Filtering: Routing based on multiple, non-hierarchical attributes.
- Policy-Based Routing: For example, routing high-priority messages to a dedicated queue.
It adds flexibility where routing keys might be too rigid.
Headers vs. Other Exchanges
How does Headers compare?
- Direct: Routes by exact
routing_keymatch. - Topic: Routes by
routing_keypatterns (wildcards). - Headers: Routes by arbitrary message header key-value pairs, offering more attribute-based flexibility.
Choose the exchange type that best fits your message routing needs!
Headers Exchange Quiz
A producer sends a message with headers {"color": "red", "size": "large"}.
Which consumer binding configuration(s) will receive this message?
Lesson Summary
In this lesson, we explored the powerful Headers exchange. You learned:
- It routes messages based on header key-value pairs.
- The
x-matchargument ("all"or"any") controls the matching logic. - How to use it for flexible, attribute-based message routing.
This exchange offers a robust alternative to routing keys for complex filtering scenarios.
よくある質問
「Headers Exchange の詳細」レッスンは無料ですか?
はい。「Headers Exchange の詳細」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し(組み込みコードエディタと24時間対応のAIチューター)、RabbitMQ Messaging & Async Systemsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 RabbitMQ Messaging & Async Systemsコースには全4レッスンが含まれています。
「Headers Exchange の詳細」で何を学びますか?
Routing Key ではなくヘッダー属性に基づいてメッセージをルーティングする Headers Exchange について学びます。より複雑で動的なルーティングルールを実装します。 ブラウザで直接実行するハンズオンコードでRabbitMQ Messaging & Async Systemsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
RabbitMQ Messaging & Async Systemsを始めるのに経験は必要ですか?
事前経験は必要ありません。CoddyKitのRabbitMQ Messaging & Async Systemsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン1/4です。
「Headers Exchange の詳細」レッスンにはどのくらい時間がかかりますか?
ほとんどのCoddyKitレッスンは約5~10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このRabbitMQ Messaging & Async Systemsレッスンでコードを書いて実行できますか?
はい。すべてのRabbitMQ Messaging & Async Systemsレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。
このコースのすべてのレッスン
- Headers Exchange の詳細
- Exchange 間の Binding
- Dead Letter Exchange(DLX)
- ルーティング不能メッセージのためのAlternate Exchange