Scaling

http://3.rdrail.net/blog/memcached-based-message-queues/ Blog pots shows and explains how to implement simple queue system on top of memcached

http://highscalability.com/blog/2009/10/26/facebooks-memcached-multiget-hole-more-machines-more-capacit.html also see http://dormando.livejournal.com/521163.html Describing some problems with performance/scalability you may have if you partition/shard your data by hash. ( that’s what memcached does.) You may hit the cpu bound limit from the amount of requests that few very popular keys receive. Currently, there is now common way around this (perhaps because very very few sites scale to the point when this becomes an issue )

http://highscalability.com/yahoo-s-pnuts-database-too-hot-too-cold-or-just-right writeup on yahoo PTUNS (distributed database ). Also, see the original paper if you are interested.

http://www.scribd.com/doc/2569319/Real-World-Web-Performance-Scalability 193 pages of realy good summaries on the topic

http://www.scribd.com/doc/2569362/Exploring-Amazon-EC2-for-Scaleout-Applications very interesting post from people who have done benchmarking and testing amazon EC2 platform

http://venublog.com/2008/04/17/notes-on-scaling-heavy-concurrent-writes-in-real-time/ notes about how to scale innodb writes. to summ it up: shard, use int as PKEY (convert hash to int using base-convert, batch lots of write into one trx. / nothing special

http://www.danga.com/gearman/ something like MapReduce in Perl – from Brad!!

http://krow.livejournal.com/590912.html interesting thoughts and notes about DBs and scalable systems

http://highscalability.com/friends-sale-architecture-300-million-page-view-month-facebook-ror-app

http://www.slideshare.net/acme/scaling-with-memcached nice presentation on memcached