4 ms·
You mean something like "store all keys with an even hash value on server X, and all keys with an odd hash value on server Y"? You can do this yourself in your
by cx01 17y ago
You mean something like "store all keys with an even hash value on server X, and all keys with an odd hash value on server Y"? You can do this yourself in your application: Just hash the value and then send the request to the corresponding server.
- wanderr 17y agoHow is that any different than how you would do it with MySQL? If both products have the same solution to the same problem (handle it in your application) then why aren't they on the same edge?
- cx01 17y agoRead the comment by "strlen". Partitioning and network partitions are two totally different things.
- wanderr 17y agoI did, but I still don't see how redis and MySQL differ in how they handle either type.
- cx01 17y agoIf you want to partition (shard) your data, then this will work roughly the same in MySQL and Redis. But this article is only about partition tolerance. Neither MySQL nor Redis are inherently distributed, so it's not possible to generally state that either is partition-tolerant or not. The article is misleading here. You could use a replication strategy that is partition-tolerant or you could use a strategy that's not partition-tolerant.
- wanderr 17y agoThanks, that's what I thought. I was hoping I was wrong. :P