Cool, maybe we can help each other out. I'm using multiple web-apps, all running in Resin containers. Have you thought about schema or how to generate sessionIds for cookies?
-Kal On Tue, Feb 1, 2011 at 12:22 PM, Sasha Dolgy <sdo...@gmail.com> wrote: > I am working on this tonight with jetty as front end and cassandra as > backend session store. Hopefully. > > On 1 Feb 2011 18:19, "Kallin Nagelberg" <kallin.nagelb...@gmail.com> wrote: >> Hey, >> I am currently investigating Cassandra for storing what are >> effectively web sessions. Our production environment has about 10 high >> end servers behind a load balancer, and we'd like to add distributed >> session support. My main concerns are performance, consistency, and >> the ability to create unique session keys. The last thing we would >> want is users picking up each others sessions. After spending a few >> days investigating Cassandra I'm thinking of creating a single >> keyspace with a single super-column-family. The scf would store a few >> standard columns, and a supercolumn of arbitrary session attributes, >> like: >> >> 0s809sdf8s908sf90s: { >> prop1: x, >> created : timestamp, >> lastAccessed: timestamp, >> prop2: y, >> arbirtraryProperties : { >> someRandomProperty1:xxyyzz, >> someRandomProperty2:xxyyzz, >> someRandomProperty3:xxyyzz >> } >> >> Does this sound like a reasonable use case? We are on a tight timeline >> and I'm currently on the fence about getting something up and running >> like this on a tight timeline. >> >> Thanks, >> -Kal >