Why this matters
- VaultCommerce still uses RabbitMQ for 200 admin alerts/day while Kafka handles 2M order events/day.
- Replay capability saved the analytics rebuild — impossible on SQS without a separate archive.
- Operational cost: Kafka cluster vs managed SQS — trade headcount for dollars at smaller scale.
- System design interviews pair this with the RabbitMQ/Kafka patterns article.
RabbitMQSmart broker, routing
SQSManaged, simple
Redis StreamsIn-memory speed
Apache KafkaDistributed log
PulsarMulti-tenancy
When VaultCommerce chose Kafka
Requirements: 7-day retention, 5 independent consumer teams, peak 50k events/sec, schema evolution with Avro. RabbitMQ hit head-of-line blocking at 8k/s with durable queues. SQS lacked ordering without FIFO shards. Kafka's partition model matched.
Key points
- Replay — new consumer group reads history; queues delete on ack
- Fan-out — multiple consumer groups on one Kafka topic vs multiple Rabbit queues bound to exchange
- Ordering — Kafka per-partition; Rabbit per-queue; SQS FIFO per message group
- Ops burden — self-managed Kafka vs managed SQS/Confluent Cloud
- Payload model — Kafka log retention vs queue message TTL
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- When queues still win
- VaultCommerce rollout checklist
Test yourself
Answer these before moving on — recall is what makes it stick.