We need to persist the sessions and associated shopping baskets / activity summaries somewhere and Cass seems like a good fit, without the restrictions imposed by SQL there would be less necessity to purge old sessions.
I take the point on though and have made a note to do some sanity checking on a session before persisting it. MK 2009/9/15 Joe Stump <[email protected]>: > I'd recommend still using Memcached for sessions. The reason is because > Memcached has built in garbage collection of zombie sessions (via LRU) and > Cassandra does not. > > --Joe > > On Sep 14, 2009, at 5:09 PM, Matt Kydd wrote: > >> I'm looking at a similar use for Cass - storing sessions and some >> denormalised data for fast frontend use. >> >> The app will be Rails and was planned to be using Memcache for >> partials, but I'm looking at ways I can get those in to Cass too - >> eliminating Memcached altogether from the architecture. >> >> MK > >
