3 ms·
Any time you have per user data you have an a clear shard key. i.e. instead of one Redis instance you have 100 where each serves a subset of users. In practice
by mbell 12y ago
Any time you have per user data you have an a clear shard key. i.e. instead of one Redis instance you have 100 where each serves a subset of users. In practice sharding isn't quite so simple but having a clear boundary makes it fairly easy to manage.
- bozoUser 12y agowow that makes sense...thanks!
- js2 12y agoYou can shard client-side, but another option is twemproxy, which can shard the keyspace for you. If you're using Python and want to shard in the client, check out nydus - https://github.com/disqus/nydus https://github.com/disqus/nydus
- mbell 12y agoI don't think that solution is viable within the constraints the parent post is talking about. There are many problems that come up with millions of users. Proper load balancing in that case is not simple and mostly dependent on the business logic.
- eurleif 12y agoWhat about Redis Cluster?