Comments on: To Redis or Not To Redis? (Key-Value Stores Part 4) http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/ Wed, 08 Feb 2012 12:12:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Researching Redis on Rails « High Tech Sorcery http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/comment-page-1/#comment-59306 Researching Redis on Rails « High Tech Sorcery Sun, 08 Jan 2012 09:34:46 +0000 http://www.engineyard.com/blog/?p=2148#comment-59306 [...] To Redis or Not To Redis? (Key-Value Stores Part 4) | Engine Yard Blog [...] [...] To Redis or Not To Redis? (Key-Value Stores Part 4) | Engine Yard Blog [...]

]]> By: Dave http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/comment-page-1/#comment-47830 Dave Wed, 27 Oct 2010 19:01:36 +0000 http://www.engineyard.com/blog/?p=2148#comment-47830 Great link!! Great link!!

]]> By: Leah Silber http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/comment-page-1/#comment-19190 Leah Silber Thu, 24 Sep 2009 18:51:32 +0000 http://www.engineyard.com/blog/?p=2148#comment-19190 Awesome -- thanks for the link! Awesome — thanks for the link!

]]> By: JEG2 http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/comment-page-1/#comment-19189 JEG2 Thu, 24 Sep 2009 18:47:23 +0000 http://www.engineyard.com/blog/?p=2148#comment-19189 I've done a more in-depth series of articles about Redis on my blog: <a href="http://blog.grayproductions.net/articles/using_keyvalue_stores_from_ruby" target="_blank">http://blog.grayproductions.net/articles/using_ke...</a> I've done a more in-depth series of articles about Redis on my blog: http://blog.grayproductions.net/articles/using_ke…

]]> By: antirez http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/comment-page-1/#comment-18651 antirez Mon, 14 Sep 2009 19:40:21 +0000 http://www.engineyard.com/blog/?p=2148#comment-18651 @dubek: there is a trick, the Ruby library is designed in order to put the keys in the same server as long as this keys all have a {soemthing_equal} string, so for instance: key1{this_are_about_userid_1} and key2{this_are_about_userid_1} are guaranteed to hash the same. You can find more info about this idea here: <a href="http://antirez.com/post/Sorting-in-key-value-data-model.html" target="_blank">http://antirez.com/post/Sorting-in-key-value-data...</a> Hope this helps. Cheers, Salvatore @dubek: there is a trick, the Ruby library is designed in order to put the keys in the same server as long as this keys all have a {soemthing_equal} string, so for instance:

key1{this_are_about_userid_1} and key2{this_are_about_userid_1} are guaranteed to hash the same.

You can find more info about this idea here: http://antirez.com/post/Sorting-in-key-value-data…

Hope this helps.

Cheers,
Salvatore

]]> By: dubek http://www.engineyard.com/blog/2009/key-value-stores-for-ruby-part-4-to-redis-or-not-to-redis/comment-page-1/#comment-18623 dubek Sun, 13 Sep 2009 13:42:57 +0000 http://www.engineyard.com/blog/?p=2148#comment-18623 Note that set operations (for example, intersection) only work if the two sets are on the same Redis server. If you have multiple servers (with consistent hashing), how can you be sure that keywords_gal and keywords_guy are stored on the same server? Note that set operations (for example, intersection) only work if the two sets are on the same Redis server. If you have multiple servers (with consistent hashing), how can you be sure that keywords_gal and keywords_guy are stored on the same server?

]]>