On Tue, Jun 30, 2009 at 1:27 PM, Tzury Bar Yochay <[email protected]>wrote:
> > > If persistence is important, that is the right approach. We use > > memcache for sessions at dealnews, but they are not ecommerce related or > > mission critical information. It's not worth the DB write for us. > > High availability is the most important thing for us. Not persistence. > If memcached is not the solution can anyone point out about other > possible solutions? > What would be the best way to have a session saved in more than one > server? > That is not a good solution in my opinion. Session data is typically temporal. Do you really want to bog down your entire site in order to replicate all the session data? When you state "High Availability" what exactly does that mean to you? What are the use cases? Again, we don't know what language you're talking about, so it's hard to give you specifics without that information. One solution that hasn't been mentioned is to have the session data live on a robust NFS store -- Netapps are particularly well known in this area. Netapps basically implement RAID 6, and will provide you great reliability, depending on what you want to pay. You can iscsi or san connect them and get blazing performance. Depending on the size of your session data set, you could also use a cluster database like the mysql NDB.
