> So, pretty general question: > > Seems against the recommendation of this list, Memcached is often used as a > session store. I'm working with a client now that uses two clusters of > memcached servers and every write is saved on two > clusters and on failed reads the backup is read. Poor mans HA -- kind of. > From what I hear the session data is updated very often -- that is almost > every read is followed by an update. And I believe the sessions are large, > too. Memcached has been reliable and easy to scale. > Still, it's a cache. > > I'm just curious what people here would recommend now for a durable and > highly available, yet fast and scalable session store for a high traffic site. > > Combine the two clusters into a single cluster and use Mysql and replication? > Memcachedb?
http://dormando.livejournal.com/495593.html - I wrote this old post on the topic. Need to rewrite that post to be a lot more succinct :/
