RabbitMQ Concepts

TL;DR

Explanation

RabbitMQ architecture: Producers send to Exchanges. Exchanges route to Queues via Bindings. Consumers read from Queues. Exchange types: Direct (exact routing key), Topic (pattern matching: orders.#), Fanout (broadcast to all bound queues), Headers (route by header values). Key features: acknowledgements (manual ack for reliability), dead letter exchanges (DLX — failed messages routed), message TTL, queue TTL, priority queues, delayed messages (plugin), publisher confirms. Shovel/Federation for multi-broker topology. PHP: php-amqplib, Symfony Messenger AMQP transport.

Common Misconception

Why It Matters

Common Mistakes

• Not marking queues and messages as durable — lost on broker restart.
• Not using manual acknowledgements — auto-ack loses messages on consumer crash.
• Ignoring the dead letter exchange — failed messages silently disappear.

Code Examples

// Auto-ack + non-durable — messages lost on crash:
$channel->queue_declare('orders');
$channel->basic_consume('orders', '', false, true); // auto-ack!

// Durable queue + manual ack:
$channel->queue_declare('orders', false, true); // durable=true
$channel->basic_consume('orders', '', false, false, false, false,
    function($msg) use ($channel) {
        try {
            processOrder($msg->body);
            $msg->ack();
        } catch (Exception $e) {
            $msg->nack(false, false); // Dead letter
        }
    }
);

References

• ↗ https://www.rabbitmq.com/tutorials/amqp-concepts.html

Tags

Related Terms