Pub/Sub için Fanout Değiş Tokuşu
Mesajları bağlı tüm kuyruklara yayınlamak için Fanout değiş tokuşunu anlayın ve uygulayın. Bu yöntem basit yayımlama/abone olma senaryoları için idealdir.
Pub/Sub için Fanout Değiş Tokuşu, CoddyKit'te ücretsiz bir RabbitMQ Messaging & Async Systems dersidir. Bu, 4 dersinin 1. dersidir. Aşağıdan dersin tamamını ücretsiz okuyabilir, sonra tarayıcıda yerleşik kod editörü ve 7/24 yapay zeka koçu ile uygulamalı olarak pratik yapabilirsin. Bu, RabbitMQ Messaging & Async Systems öğrenme yolunun bir parçasıdır ve ilerlemeniz web ve CoddyKit uygulaması arasında senkronize olur. RabbitMQ Messaging & Async Systems kursu toplamda 4 dersten oluşur.
Bu dersin bazı bölümleri henüz çevrilmemiş olup İngilizce olarak gösterilmektedir.
Pub/Sub & Fanout Explained
Imagine you want to broadcast a message to everyone interested, without knowing who they are. This is the idea behind the Publish/Subscribe (Pub/Sub) messaging pattern.
In RabbitMQ, the Fanout exchange is perfect for this. It acts like a megaphone, shouting your message to all connected listeners.
How Fanout Exchanges Work
A Fanout exchange is the simplest type of exchange. When a message arrives at a Fanout exchange, it doesn't care about routing keys.
- It takes the message.
- It duplicates it for every queue that is bound to it.
- Then, it sends a copy of the message to each of those bound queues.
Think of it as a broadcast to all subscribers.
Key Components
Let's quickly recap the main players:
- Producer: Sends the message.
- Exchange: Receives messages from producers and routes them to queues. Fanout is one type.
- Queue: A buffer that stores messages until a consumer picks them up.
- Consumer: Receives messages from queues and processes them.
With Fanout, the exchange ensures all bound queues get the message.
Routing Keys Are Ignored
A crucial detail about Fanout exchanges: they completely ignore routing keys!
When a producer sends a message to a Fanout exchange, it might still provide a routing key (often an empty string), but the exchange simply disregards it.
Its only job is to broadcast to all queues bound to it, regardless of any key.
Setting Up the Fanout Exchange
First, our producer needs to declare the Fanout exchange. This tells RabbitMQ to create or ensure this exchange exists.
Notice the "fanout" type parameter. Try running this code to declare your exchange!
import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
public class FanoutProducerSetup {
private final static String EXCHANGE_NAME = "fanout_logs";
public static void main(String[] argv) throws Exception {
ConnectionFactory factory = new ConnectionFactory();
factory.setHost("localhost");
try (Connection connection = factory.newConnection();
Channel channel = connection.createChannel()) {
// Declare a fanout exchange
channel.exchangeDeclare(EXCHANGE_NAME, "fanout");
System.out.println("Fanout exchange '" + EXCHANGE_NAME + "' declared.");
}
}
}Binding a Queue to Fanout
Consumers don't receive directly from exchanges. They receive from queues. Each consumer needs its own queue, and that queue must be bound to the Fanout exchange.
queueDeclare() with no arguments creates a unique, exclusive, auto-delete queue. The routing key for binding is an empty string, as it's ignored by Fanout.
import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
public class FanoutConsumerSetup {
private final static String EXCHANGE_NAME = "fanout_logs";
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(EXCHANGE_NAME, "fanout");
String queueName = channel.queueDeclare().getQueue(); // A unique, auto-delete queue
channel.queueBind(queueName, EXCHANGE_NAME, ""); // Bind with empty routing key
System.out.println("Queue '" + queueName + "' declared and bound to '" + EXCHANGE_NAME + "'.");
System.out.println("Ready for messages (but not consuming yet).");
}
}Publishing to Fanout Exchange
Once the exchange is declared, the producer can send messages to it. Notice how the basicPublish method specifies the exchange name, but the routing key is an empty string.
Run this code after you've set up your exchange. It will publish one message.
import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
import java.nio.charset.StandardCharsets;
public class FanoutPublisher {
private final static String EXCHANGE_NAME = "fanout_logs";
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(EXCHANGE_NAME, "fanout"); // Ensure exchange exists
String message = "Hello everyone, this is a broadcast!";
// Publish to the exchange, routing key is ignored for fanout
channel.basicPublish(EXCHANGE_NAME, "", null, message.getBytes(StandardCharsets.UTF_8));
System.out.println(" [x] Sent '" + message + "'");
}
}
}Consuming Broadcasts
Now, let's make our consumer actually receive messages. The DeliverCallback defines what happens when a message arrives. Remember, each consumer has its own queue!
To see the broadcast in action, first run two separate instances of this consumer code. Then, run the publisher code from the previous scene. Both consumers should receive the message!
import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
import com.rabbitmq.client.DeliverCallback;
import java.nio.charset.StandardCharsets;
public class FanoutSubscriber {
private final static String EXCHANGE_NAME = "fanout_logs";
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(EXCHANGE_NAME, "fanout");
String queueName = channel.queueDeclare().getQueue(); // Exclusive, auto-delete queue
channel.queueBind(queueName, EXCHANGE_NAME, ""); // Bind to fanout exchange
System.out.println(" [*] Waiting for messages in queue '" + queueName + "'. To exit press CTRL+C");
DeliverCallback deliverCallback = (consumerTag, delivery) -> {
String message = new String(delivery.getBody(), StandardCharsets.UTF_8);
System.out.println(" [x] Received '" + message + "'");
};
// Auto-ack set to true for simplicity in this example
channel.basicConsume(queueName, true, deliverCallback, consumerTag -> {});
}
}Fanout in Action
When you ran two consumers and then the publisher, you observed the core concept of Fanout: every active consumer received a copy of the message.
This is because each consumer had its own unique queue, and both queues were bound to the same fanout_logs exchange. The exchange simply duplicated the message to all bound queues.
This makes Fanout ideal for scenarios like real-time logging, notifications, or broadcasting updates.
Test Your Knowledge
Time for a quick check on Fanout exchanges!
Fanout Recap
You've successfully learned about the Fanout exchange!
- It implements the Pub/Sub pattern.
- It broadcasts messages to all bound queues.
- It ignores routing keys when distributing messages.
- It's perfect for scenarios where multiple consumers need to receive the same message.
Next, we'll explore the Direct exchange, which uses routing keys for more precise message delivery!
Sıkça Sorulan Sorular
“Pub/Sub için Fanout Değiş Tokuşu” dersi ücretsiz mi?
Evet — “Pub/Sub için Fanout Değiş Tokuşu” dersin tüm metni burada web'de ücretsiz olarak okunabilir. Etkileşimli olarak pratik yapmak (yerleşik kod editörü ve 7/24 yapay zeka koçu) ve RabbitMQ Messaging & Async Systems kursunun geri kalanını açmak için CoddyKit PRO'ya yükselt. RabbitMQ Messaging & Async Systems kursu toplamda 4 dersten oluşur.
“Pub/Sub için Fanout Değiş Tokuşu” dersinde ne öğreneceğim?
Mesajları bağlı tüm kuyruklara yayınlamak için Fanout değiş tokuşunu anlayın ve uygulayın. Bu yöntem basit yayımlama/abone olma senaryoları için idealdir. RabbitMQ Messaging & Async Systems ile uygulamalı kodu tarayıcıda doğrudan çalıştırarak pratik yaparsın ve 7/24 yapay zeka koçu dersi çalışırken sorularını yanıtlar.
RabbitMQ Messaging & Async Systems öğrenmeye başlamak için deneyim gerekli mi?
Önceden deneyim gerekmez. CoddyKit'te RabbitMQ Messaging & Async Systems, başlangıçtan ileri seviyeye kadar yapılandırıldığı için buradan başlayabilir veya başından başlayıp kendi hızında ilerleme yapabilirsin. Bu, 4 dersinin 1. dersidir.
“Pub/Sub için Fanout Değiş Tokuşu” dersi ne kadar sürer?
Çoğu CoddyKit dersi yaklaşık 5–10 dakika sürer. Her biri kısa ve etkileşimli olduğu için sabit ilerleme yaparsın ve web ile uygulama arasında tam olarak bıraktığın yerden devam edebilirsin.
Bu RabbitMQ Messaging & Async Systems dersinde kod yazıp çalıştırabilir miyim?
Evet. Her RabbitMQ Messaging & Async Systems dersi yerleşik bir kod editörü içerir, bu sayede tarayıcıda gerçek kod yazıp çalıştırabilir ve anlık yapay zeka geri bildirimi alırsın — yerel kurulum gerekli değildir.
Bu kursun tüm dersleri
- Pub/Sub için Fanout Değiş Tokuşu
- Yönlendirme için Direct Değiş Tokuşu
- Esnek Yönlendirme için Topic Değiş Tokuşu
- Varsayılan Değiş Tokuş ve Örtük Bağlamalar