Pattern dei consumer concorrenti
Implementi il pattern dei consumer concorrenti per consentire a più consumer di elaborare i messaggi provenienti da una singola coda. Aumenti la capacità di elaborazione aggiungendo altri consumer.
Pattern dei consumer concorrenti è una lezione RabbitMQ Messaging & Async Systems gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento RabbitMQ Messaging & Async Systems, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso RabbitMQ Messaging & Async Systems include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Scaling with Competing Consumers
Welcome! In distributed systems, you often need to process many tasks efficiently. The Competing Consumers pattern is a powerful way to achieve this.
It allows you to scale your message processing capacity by simply adding more workers.
How Competing Consumers Work
Imagine a single queue of tasks. Instead of one worker taking all tasks, multiple workers (consumers) listen to this same queue.
- Each message is delivered to only one of the competing consumers.
- Consumers "compete" to receive the next available message.
- This distributes the workload automatically.
Key Benefits of the Pattern
The Competing Consumers pattern offers several advantages:
- Scalability: Easily increase processing power by adding more consumer instances.
- Reliability: If one consumer fails, others can pick up its share of messages.
- Load Balancing: Messages are spread across available consumers, balancing the workload.
- Decoupling: Producers don't need to know how many consumers there are or where they are.
Producer: Sending Tasks
Let's set up a basic producer that sends messages (tasks) to a queue named task_queue. Each message will be a simple string.
Run this code to send a few messages:
import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
public class TaskProducer {
private final static String QUEUE_NAME = "task_queue";
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()) {
// Declare a durable queue
channel.queueDeclare(QUEUE_NAME, true, false, false, null);
for (int i = 0; i < 10; i++) {
String message = "Task " + (i + 1);
channel.basicPublish("", QUEUE_NAME, null, message.getBytes("UTF-8"));
System.out.println(" [x] Sent '" + message + "'");
Thread.sleep(100); // Small delay to visualize
}
}
}
}Consumer 1: Processing Tasks
Now, let's create our first consumer. It will connect to task_queue and start processing messages. Each message will be acknowledged after simulating work.
Run this consumer in a terminal:
import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
import com.rabbitmq.client.DeliverCallback;
public class TaskConsumer {
private final static String QUEUE_NAME = "task_queue";
public static void main(String[] argv) throws Exception {
ConnectionFactory factory = new ConnectionFactory();
factory.setHost("localhost");
Connection connection = factory.newConnection();
Channel channel = connection.createChannel();
channel.queueDeclare(QUEUE_NAME, true, false, false, null);
System.out.println(" [*] Consumer 1 waiting for messages.");
// Basic QoS: Prefetch 1 message at a time to ensure fair dispatch
channel.basicQos(1);
DeliverCallback deliverCallback = (consumerTag, delivery) -> {
String message = new String(delivery.getBody(), "UTF-8");
System.out.println(" [C1] Received '" + message + "'");
try {
Thread.sleep(1000); // Simulate work
} finally {
System.out.println(" [C1] Done '" + message + "'");
channel.basicAck(delivery.getEnvelope().getDeliveryTag(), false);
}
};
channel.basicConsume(QUEUE_NAME, false, deliverCallback, consumerTag -> {});
}
}Running Multiple Consumers
To truly see the competing consumers pattern in action, open a new terminal window and run the exact same TaskConsumer code again.
You'll now have two consumer instances listening to the task_queue. Run the producer code (from Scene 4) once more. Observe how messages are now distributed between both consumer instances, demonstrating how they compete for messages and share the workload!
RabbitMQ's Dispatching Logic
By default, RabbitMQ uses a round-robin dispatching mechanism when multiple consumers are connected to the same queue. This means messages are sent to consumers sequentially.
- Consumer 1 gets message 1.
- Consumer 2 gets message 2.
- Consumer 1 gets message 3, and so on.
The basicQos(1) setting in our consumer code is crucial here. It tells RabbitMQ not to send more than one unacknowledged message to a consumer at a time, ensuring fair dispatch even if consumers process at different speeds.
Common Use Cases
The Competing Consumers pattern is ideal for scenarios like:
- Image processing: Multiple workers resizing images from a queue.
- Email sending: Sending bulk emails without overwhelming a single service.
- Log processing: Analyzing large volumes of logs in parallel.
- Background jobs: Any task that can be processed independently by multiple workers.
Important Considerations
When using competing consumers, keep these in mind:
- Message Ordering: If strict message order is critical, this pattern might not be suitable directly, as messages can be processed out of order by different consumers.
- Idempotency: Consumers should ideally be idempotent. This means processing the same message multiple times should have the same effect as processing it once. This is vital for fault tolerance and retries.
Competing Consumers Quiz
Test your understanding of the Competing Consumers pattern.
Recap: Competing Consumers
Great job! You've learned about the Competing Consumers pattern:
- It enables multiple consumers to process messages from a single queue.
- It's excellent for scaling and load balancing message processing.
- RabbitMQ's default round-robin dispatch and QoS settings facilitate fair distribution.
- Consider idempotency and potential out-of-order processing for specific use cases.
Next, we'll dive deeper into optimizing consumer efficiency with prefetch counts!
Domande Frequenti
La lezione «Pattern dei consumer concorrenti» è gratuita?
Sì — il testo completo di «Pattern dei consumer concorrenti» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso RabbitMQ Messaging & Async Systems, passa a CoddyKit PRO. Il corso RabbitMQ Messaging & Async Systems include 4 lezioni in totale.
Cosa imparerò in «Pattern dei consumer concorrenti»?
Implementi il pattern dei consumer concorrenti per consentire a più consumer di elaborare i messaggi provenienti da una singola coda. Aumenti la capacità di elaborazione aggiungendo altri consumer. Eserciti RabbitMQ Messaging & Async Systems con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare RabbitMQ Messaging & Async Systems?
Non è richiesta alcuna esperienza precedente. RabbitMQ Messaging & Async Systems su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.
Quanto tempo richiede la lezione «Pattern dei consumer concorrenti»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione RabbitMQ Messaging & Async Systems?
Sì. Ogni lezione RabbitMQ Messaging & Async Systems include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Pattern dei consumer concorrenti
- Numero di prefetch (QoS)
- Consumer esclusivi e priorità dei consumer
- Single Active Consumer