What is the architectural difference between a queue (RabbitMQ) and an append-only log (Kafka)?
Queues track message state per consumer and delete messages once acknowledged. Append-only logs retain messages immutably for days or weeks, allowing multiple independent consumer groups to read and replay the log at distinct offsets.
Answered in
Message Brokers Demystified: Append-Only Logs, Consensus Replication, and Delivery GuaranteesAn architectural deep dive into message brokers: log-structured storage, Raft/Paxos consensus replication, temporal buffering, and delivery guarantees.
Read the full analysisOther questions this article answers
More system design & architecture questions
- What is the architectural difference between an API Gateway and a Reverse Proxy?
- When should an architecture use Layer 4 instead of Layer 7 load balancing?
- How do edge ingress layers prevent backend cascading thundering herds?
- What algorithm is best for sticky sessions without breaking even distribution?
- How can a CDN improve performance for dynamic requests?
- What is the hardest part of operating behind a CDN?
- How can a CDN help with traffic surges or DDoS attacks?
- What is the difference between a Push CDN and a Pull CDN?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.