Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of rajkumar.w93@gmail.com
 designates 209.85.161.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=Vu6aRrcXjbJujptyXfJ2H2taF7VRWkg16re/O9qk7NCNpUahQuc4WylgP/zJYXpVk/
         h+zRclr5PugPNbGXspjtEPaL+b6r6m6jyhzReu4ouPy9p5D3+wkjdDJ1QUvMpF0o6+UV
         fCSexmAi8oTK4K6nrze+SqXdYutihnSkDWC78=
MIME-Version: 1.0
Sender: rajkumar.w93@gmail.com
Date: Fri, 4 Feb 2011 00:33:00 +0530
Message-ID: <AANLkTi=279fB=mDVtXfKP-sU_3o9qSuObXFSh9Z=2O6_@mail.gmail.com>
Subject: Using a synchronized counter that keeps track of no of users on the
 application & using it to allot UserIds/ keys to the new users after sign up
From: Aklin_81 <asdkl93@gmail.com>
To: user <user@cassandra.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

To generate new keys/ UserIds for new users on my application, I am
thinking of using a simple synchronized counter that can keep track of
the no. of users registered on my application and when a new user
signs up, he can be allotted the next available id.

Since Cassandra is eventually consistent, Is this advisable to
implement with Cassandra, but then I could also use stronger
consistency level like quorum or all for this purpose.


Please let me know your thoughts and suggesttions..

Regards
Asil