InterviewBit Problems   Sharding a Database


About the Sharding a Database category (1)
Are Total number of shards and total number of machines are equal here? (1)
How will we insure , same user goes to same shard , when new shrds added? (1)
How many shards do we have and how do we distribute the data within the shard? (7)
Can we have a fixed number of shards? (5)
Number of machines (2)
How frequently would we need to add machines to our pool? (6)
I cant understand,what advantage we gain by maintaining the multiple copies of th (3)
Can we think of a better sharding strategy? (4)
Modified consistent hashing confusion (2)
When new shard added or one shard removed then those keys will be point to new shard. But data was stored in removed hash. Wouldn't there will be miss for all keys which are stored in removed key? (2)
Handling a request while adding a node (1)
Hint: Consistent Hashing? (1)
Found a nice article about consistent hashing with sample implementation (1)
I found the following YouTube tutorial by Curtis on Consistent Hashing interestin (3)
Logical shard ids for uniform distributionand scalability (1)
Discussion of the Estimation was irrelevant (1)
Modified consistent hashing: Multiple copies of same shard (1)
Multiple copies of the same shard distributed over the ring (3)
What happens when the hash generated for a key collides with an existing shard on the ring (2)
I think modified consistent hashing explained above is not correct. Please refer (2)
What is this obsession with 72GB RAM? Isn't is better / easier to pick powers of (2)
Modified consistent hashing (1)
How do I locate a key reliably? (3)
Https://www.toptal.com/big-data/consistent-hashing (1)
Storing data in multiple shards is same as replication factor. We can address thi (2)
How does the system remain available during the time when a node failure occurs a (1)
It looks like this is not addressing the question of how data is actually relocat (1)
Sharding a Database What is the minimum number of machines required to store the data? (2)
Great Doc. You can find more information about consistent hashing implementation (1)