Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 11620 invoked from network); 1 Feb 2011 20:49:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Feb 2011 20:49:12 -0000 Received: (qmail 32150 invoked by uid 500); 1 Feb 2011 20:49:09 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 31822 invoked by uid 500); 1 Feb 2011 20:49:08 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 31805 invoked by uid 99); 1 Feb 2011 20:49:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 20:49:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Janne.Jalkanen@ecyrd.com designates 193.64.5.122 as permitted sender) Received: from [193.64.5.122] (HELO mail.ecyrd.com) (193.64.5.122) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 20:48:58 +0000 Received: from [192.168.0.10] (cs181095019.pp.htv.fi [82.181.95.19]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.ecyrd.com (Postfix) with ESMTPSA id 265B297C1BE for ; Tue, 1 Feb 2011 22:48:22 +0200 (EET) From: Janne Jalkanen Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: multipart/alternative; boundary=Apple-Mail-2-458522124 Subject: Re: cassandra as session store Date: Tue, 1 Feb 2011 22:48:21 +0200 In-Reply-To: To: user@cassandra.apache.org References: <1296582141589-5981961.post@n2.nabble.com> <1296583033554-5982024.post@n2.nabble.com> Message-Id: X-Mailer: Apple Mail (2.1082) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-2-458522124 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii If your sessions are fairly long-lived (more like hours instead of = minutes) and you crank up a suitable row cache and make sure your db is = consistent (via quorum read/writes or write:all, read:1) - sure, why = not? Especially if you're already familiar with Cassandra; possibly = even have a deployed instance already for your web app. Adding new = components to the mix is always a sure way to get some headscratching = going. For a small team who does not want to spend too much time on = configuring yet another database, Cassandra would probably work well as = a session store. And you would get cross-datacenter reliability too. However, you might want to use 0.7 and expiring columns; otherwise = cleaning up is going to be boring. /Janne On Feb 1, 2011, at 22:24 , Sasha Dolgy wrote: >=20 > What I'm still unclear about, and where I think this is suitable, is = Cassandra being used as a data warehouse for current and past sessions = tied to a user. Yes, other things are great for session management, but = I want to provide near real time session information to my users ... = quick and simple and i want to use cassandra ... surely i can't be that = bad for thinking this is a good idea? > =20 > -sd >=20 > On Tue, Feb 1, 2011 at 9:20 PM, Kallin Nagelberg = wrote: > nvm on the persistence, it seems like it does support it: >=20 > 'Since version 1.1 the safer alternative is an append-only file (a > journal) that is written as operations modifying the dataset in memory > are processed. Redis is able to rewrite the append-only file in the > background in order to avoid an indefinite growth of the journal.' >=20 > This thread probably shouldn't digress too much from Cassandra's > suitability for session management though.. --Apple-Mail-2-458522124 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

What I'm still unclear about, and where I = think this is suitable, is Cassandra being used as a data warehouse for = current and past sessions tied to a user.  Yes, other things are = great for session management, but I want to provide near real time = session information to my users ... quick and simple and i want to use = cassandra ... surely i can't be that bad for thinking this is a good = idea?
  
-sd

On Tue, Feb = 1, 2011 at 9:20 PM, Kallin Nagelberg <kallin.nagelberg@gmail.com&= gt; wrote:
nvm on the persistence, it seems like it does support it:

'Since version 1.1 the safer alternative is an append-only file (a
journal) that is written as operations modifying the dataset in = memory
are processed. Redis is able to rewrite the append-only file in the
background in order to avoid an indefinite growth of the journal.'

This thread probably shouldn't digress too much from Cassandra's
suitability for session management though..

= --Apple-Mail-2-458522124--