Skip to content

RabbitMQ vs Kafka

Not a benchmark. A comparison of the questions each one makes you answer: about ordering, replay, consumers and who owns the offset.

, 11 min read

Not a benchmark. A comparison of the questions each one makes you answer: about ordering, replay, consumers and who owns the offset.

Filed under

  • Messaging
  • Kafka
  • RabbitMQ

Related

  1. System design, , 9 min read

    Idempotent consumers, without the ceremony

    What actually happens when the same message arrives twice, and the smallest set of changes that makes a consumer safe to retry.

    • Messaging
    • Kafka
    • PostgreSQL
  2. Journal, , 8 min read

    Rebuilding the billing flow as events

    Why the second version of an event-driven design is usually the simpler one, and the retry question that decided the whole shape.

    • Building
    • Kafka
  3. System design, , 14 min read

    Designing a notification system

    Fan-out, user preferences and the retry budget — sketched end to end before building any of it.

    • Messaging
    • Distributed systems

Next

Have a system worth arguing about?

If this note raised a question, or you would have designed it differently, I would like to hear it.

Start a conversation