keva-dev / keva-dev/keva

Explore possibility of sharding the keyspace for reducing lock scope

Open
#93 3 comments 0 reactions 5 assignees Claimed by @the123saurav View on GitHub
enhancement
Dominant language
Java
Stars
109
Forks
11
PR merge metrics
No merged PRs in 30d

Description

# Issue
Currently we are taking a `global lock` for every request so as to guarantee the order of execution for commands.

# Possible Solve
CM uses segments under the hood just like ConcurrentHashMap for parallel access.
If we can use the same hashing mechanism and just take a lock on the segment, we can guarantee ordering for same key.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.