We are using cluster setup of redis and sending commands to store scores, ranks, etc in-parallel to all the shards. That way we are scaling writes and reads. That being said, storing a large leaderboard (i.e sorted set) is challenging since a single LB will reside on a single node. So, this is a nice engineering problem that we have solved differently.
Good talk. Good description of design problem.
i f**kin ❤️ redis.
Basically you just used redis to solve all the problem. Redis already supports your usecase.
How is redis being single threaded lets you distribute the work? Some of the claims are not making sense to me😊
We are using cluster setup of redis and sending commands to store scores, ranks, etc in-parallel to all the shards. That way we are scaling writes and reads. That being said, storing a large leaderboard (i.e sorted set) is challenging since a single LB will reside on a single node. So, this is a nice engineering problem that we have solved differently.
Wooow