My SQL hosted two excellent webinars (referenced below) on the subject of how to deploy and use memcached.
The star of the show, other than My SQL of course, is Farhan Mashraqi of Fotolog.
You may recall we did an earlier article on Fotolog in Secrets to Fotolog's Scaling Success, which was one of my personal favorites.
Fotolog, as they themselves point out, is probably the largest site nobody has ever heard of, pulling in more page views than even Flickr.
Just in case the rock you've been hiding under recently disintegrated, you may not have heard about memcached (as if). Memcached essentially creates an in-memory shard on top of a pool of servers from which an application can easily get and set up to 1MB of unstructured data.Additionally you always still have the option of throwing Memached on top of your extra partitioned system.One factor that turns this into a "it depends" scenario is when assuming the pattern of the access to your database works well with the way you partitioned the system.If you've never used memcached before there's a lot of good stuff presented.There's a little embrace and extend in the webinar as My SQL cluster is presented several times as doing much the same job as memcached, but more reliably.These are the pieces/scenarios that make each system/site different from the next. We are currently integrating memcaching in a Mysql / PHP data send between two websites.