Re: Session and Multi Server Architecture

On 2/12/08, Nathan Nobbe <quickshiftin@gmail.com> wrote: > also, in terms of scalability, isnt facebook proof that > memcache can scale? memcached is behind facebook, livejournal (who made it), i believe dealnews, flickr, twitter, pownce, typepad, fotolog, slashdot, feedburner, 37signals, i think even myspace is trying to use it now. sun has even contributed 6? dedicated resources i believe to the project now too. here's an article about how it was key in helping twitter scale: http://highscalability.com/scaling-twitter-making-twitter-10000-percent-faster most people will agree your biggest bottleneck is always your database. throwing a caching layer in the mix (where memcached is typically the most popular) alleviates a LOT of database traffic and processing (depending on the type of load - reads vs. writes, etc.) highscalability.com is an awesome website, lots of good information and products that have proven to be successful (since the sites are obviously up and functional :)) i have read a lot of presentations and almost all of them always eventually introduce data sharding, a caching layer, batched denormalization of specific data, etc. to effectively use memcached though, you'll want to design with a caching layer in place from the beginning. it might not be -active-, but with the right hooks it will be transparent to enable it.