Loading...
Loading...
RabbitMQ message broker with AMQP protocol. Covers exchanges, queues, bindings, and messaging patterns. Use for reliable message delivery and complex routing scenarios. USE WHEN: user mentions "rabbitmq", "amqp", "exchanges", "routing patterns", "topic exchange", "fanout", asks about "message routing", "work queues", "request/reply", "flexible routing" DO NOT USE FOR: high-throughput streaming - use `kafka` or `pulsar`; cloud-native - use `nats`; AWS-native - use `sqs`; JMS required - use `activemq`; simple pub/sub - use `redis-pubsub`
npx skill4agent add claude-dev-suite/claude-dev-suite rabbitmqFull Reference: See advanced.md for producer patterns (Node.js, Java, Python, Go), consumer patterns, security configuration, and high availability setup.
Deep Knowledge: Usewith technology:mcp__documentation__fetch_docsfor comprehensive documentation.rabbitmq
services:
rabbitmq:
image: rabbitmq:3-management
ports:
- "5672:5672" # AMQP
- "15672:15672" # Management UI
environment:
- RABBITMQ_DEFAULT_USER=admin
- RABBITMQ_DEFAULT_PASS=admin| Concept | Description |
|---|---|
| Exchange | Routes messages to queues |
| Queue | Buffer that stores messages |
| Binding | Rule linking exchange to queue |
| Routing Key | Message attribute for routing |
Producer ──▶ Exchange ──binding──▶ Queue ──▶ Consumer
│
├── direct (exact routing key match)
├── topic (pattern matching)
├── fanout (broadcast to all)
└── headers (header-based routing)| Type | Routing | Use Case |
|---|---|---|
| direct | Exact key match | Task queues, RPC |
| topic | Pattern (*.#) | Event routing |
| fanout | Broadcast all | Notifications |
| headers | Header match | Complex routing |
# Topic exchange patterns
order.* → matches order.created, order.updated
order.# → matches order.created, order.item.added
*.created → matches order.created, user.created| Argument | Description |
|---|---|
| Message expiration (ms) |
| Max queue size |
| DLX for rejected messages |
| DLQ routing key |
| classic, quorum, stream |
| Anti-Pattern | Why It's Bad | Solution |
|---|---|---|
| No prefetch limit | Consumer overwhelmed | Set |
| Classic queues in HA | Data loss on node failure | Use quorum queues |
| No DLX configured | Poison messages loop forever | Configure dead letter exchange |
| Automatic acks | Message loss on crash | Use manual acks |
| No publisher confirms | Silent message loss | Enable confirms for critical messages |
| Issue | Likely Cause | Fix |
|---|---|---|
| Messages piling up | Slow/dead consumer | Check consumer count and processing |
| High memory usage | Too many unacked messages | Reduce prefetch, add consumers |
| Messages not routed | Wrong routing key | Check exchange-queue bindings |
| Duplicate messages | Consumer crashed before ack | Implement idempotent processing |
| Publisher confirms timeout | Broker overloaded | Reduce publish rate |
basicsexchangesqueuesconsumersclusteringproduction