Ankur Mhatre
e7e64a047b
Kafka, RabbitMQ and Pulsar measured side by side on ordering, replay and consumer scaling by driving the three client libraries directly, plus an operational-footprint measurement of each broker's own distribution. Nine tests, three brokers started without Docker, and every number in the documentation regenerated by scripts/run-all.sh.
13 lines
516 B
Plaintext
13 lines
516 B
Plaintext
== RabbitMQ: there is nothing to replay ==
|
|
|
|
first drain of the queue : 12 messages
|
|
second drain of the queue : 0 messages
|
|
queue depth afterwards : 0
|
|
|
|
Acknowledging a message deletes it. The broker is a router with buffers,
|
|
not a log: there is no offset to rewind and no second reader that can see
|
|
what the first one consumed. Reading the same message twice means
|
|
arranging it in advance -- a second queue bound to the same exchange, or a
|
|
copy written somewhere else -- and it cannot be arranged after the fact.
|
|
|