Simple Twitter clone using only the Redis key-value store as db and PHP

Re:Simple Twitter clone using only the Redis key-value store... by pipagiorgos on Thursday May 21, 2009 @10:28AM (#620485)

Question: (newbie here) if we assume that with 350 million keys for the 64GB ram server we have reached the peak of it's capacity, if we double the number of keys, do we have to get new hardware, like a second server or double the ram?

Or is it something simpler? Like storing the current keys on disk (somehow) and keep going with the server as it is.

To rephrase my question: keeping all in ram... is "all" like ALL ??? Would this solution work for the "real" twitter, with the billion twits, if 350 million keys were created every hour?

[ Parent | on HN ]

Re:Simple Twitter clone using only the Redis key-value store... by antirez on Thursday May 21, 2009 @12:35PM (#620699)

If you have more data than a single server can hold the best thing to do is hashing. For instance the Redis-rb client supports consistent hashing.

yes "ALL" in Ram :) this will work for twitter, facebook, everything: what they are doing is to use only the RAM even if they have MySQL, with tons of memcached around. With Redis of course the memcached layer goes away.

[ Parent | on HN ]

Re:Simple Twitter clone using only the Redis key-value store... by jjs on Thursday May 21, 2009 @04:51PM (#621113)

> If you have more data than a single server can hold the best thing to do is hashing. For instance the Redis-rb client supports consistent hashing.

Hopefully with a secret salt! It would be interesting if someone nasty managed to take down a node by e.g. predictively registering certain usernames.

[ Parent | on HN ]