New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
My team wants a new event stream and everyone has a different opinion on whether it belongs on RabbitMQ or on Kafka.
What you'll have at the end
A one-page decision written down: which broker this event stream runs on and the two reasons that settled it
You need
A specific event stream with at least one producer and more than one downstream consumer already agreed on, even if neither the producer nor any consumer is built yet.
Not covered
A managed queue like SQS, a newer log like Pulsar, or any other broker isn't weighed here: this is a straight RabbitMQ-or-Kafka call for a team already leaning toward one of the two, and the wider field lives in the linked Message Queue Technologies table instead.
Leans on
Route each kind of event to the right service using a topic exchange
if the decision lands on RabbitMQ, this is the recipe for wiring the routing that decision depends on.
Keep every event about the same customer in the exact order they happened
if the decision lands on Kafka, this is the recipe for guaranteeing per-key order once the stream is running.
Checked 19 Aug 2026
Part of the Message Queues cookbook