Feature: Allows overriding a getServer method for using a hashring #159
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.
Continuing the conversation from #158.
This is a very simple addition to the codebase that will make it easy to hook in a consistent hashing ring.
I'd also like to suggest using node-hashring for performance instead of the 3rd-eden HashRing. Most notably, 3rd-Eden's implementation uses a 128-bit MD5 and then reduces it to a 32-bit uint and node-hashring uses the 32-bit MurmurHash algorithm which offers tremendous performance gains.
Usage