Rabbit MQ vs Kafka: When, Which, Where?
summary
Compares concrete behaviors: Kafka acts as a transaction log backed by Zookeeper, keeps messages for replay via offsets, and requires increasing partitions to scale parallel consumers; demo sends 20 messages and shows seeking to offset 0 and multiple consumer groups replaying the stream. RabbitMQ uses an exchange and queues, deletes messages on ack, supports prefetch tuning for fair distribution and horizontal scaling by adding consumers, and offers priority queues (0–255) plus built‑in dead‑letter routing; Kafka needs explicit exception topics for failed messages.
AI-written summary · about
chapters (8)
- 0:00Introduction to frameworks
- 7:48RabbitMQ basics demo
- 11:18Kafka basics demo
- 21:52Scaling architectures
- 39:23Exception handling
- 51:31Message prioritization
- 56:12PubSub model comparison
- 58:43Summary and use cases
related talks
59mComparative Review of Polling Mechanisms in Kafka and Pub/Sub in RabbitMQ
32mRabbitMQ in Real Life - Tips and Tricks
35mMigrating from Kafka to RabbitMQ at SimpleBet: Why and How
53mDemystifying Kafka
01h 03mChoosing the Right Messaging Solution for Your Architecture
39mKafka as a Platform: The Ecosystem from the Ground Up
30mUsing MongoDB with Kafka - Use Cases and Best Practices
41mKafka as a Platform: The Ecosystem from the Ground Up