message-broker-selection

Choosing between Kafka and RabbitMQ requires evaluating workload criteria like replay, retention, and ordering to determine if a log-based or queue-based broker fits your domain event patterns.

Log-based brokers provide immutable history retention for event streams, while queue-based brokers handle transient task-dispatch patterns, preventing the architectural anti-pattern of treating both models as swappable.

You need a log-based broker when your messaging workload demands replay capabilities and strict retention for domain events, rather than the transient task-dispatch capabilities of a queue.

Evaluate messaging workload requirements by applying replay, retention, and ordering questions to justify your infrastructure selection, explicitly aligning messaging models with domain event or task-dispatch patterns.

Treating log-based and queue-based brokers as interchangeable causes production failures because workloads requiring immutable event history fail when deployed on transient task-dispatch queue architectures.

Queue-based brokers lack the immutable history retention required for event replay, meaning you must select a log-based architecture to satisfy workloads with strict replay and retention criteria.