Sharding adapter #20
Merged
Sharding adapter #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@TorstenDittmann great review! Addressed all comments! |
TorstenDittmann
approved these changes
Sep 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Sharding adapter allows to shard cache across multiple adapters in a consistent way. Using sharding we can increase cache size and balance the read and write load between multiple adapters.
Each cache key will be hashed and the hash will be used to determine which adapter to use for fetching or storing this key. Only one adapter will always match a specific key unless a new adapter is added to the pool.
When adding a new adapter to the pool, cached will gradually get re-distributed to fill the new adapter, this might cause a significant drop in hit-rate for a short period of time.