Feature: adding support for RabbitMQ consistent hash exchange type #127
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why Consistent Hashing?
A RabbitMQ queue is running on at most 1 CPU core, feature of Erlang Beam VM architecture.
To achieve horizontal scalability, it is advised to have multiple queues.
One variant of such topology is declaring a [Consistent Hash Exchange] (https://github.com/rabbitmq/rabbitmq-server/blob/main/deps/rabbitmq_consistent_hash_exchange/README.md):
x-consistent-hash
, multipleN
queues, all bound to the same consistent hash exchange;i
in[0 .. N)
based on the hashed routing key;[0 .. N)