Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 50821 invoked from network); 7 Sep 2010 06:59:48 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Sep 2010 06:59:48 -0000 Received: (qmail 56482 invoked by uid 500); 7 Sep 2010 06:59:47 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 56232 invoked by uid 500); 7 Sep 2010 06:59:43 -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 56224 invoked by uid 99); 7 Sep 2010 06:59:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Sep 2010 06:59:42 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jshook@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Sep 2010 06:59:36 +0000 Received: by qwc9 with SMTP id 9so4853800qwc.31 for ; Mon, 06 Sep 2010 23:59:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=d/HTI8bCxlbUL5zJ+u0cup4PUZ2d8LnPiIdSjzZ4tR0=; b=VUAF3snCz3sC0CW4IhEMTpM6S68zwwtUiF5CHYAL7ENULd3Tx6RzsRAbfD1djqh3IR EvOl11ikGW2Twm6X5VEzvSiZcQYt/crLuZMeXp0140TFzk8u85VDzUnfJIlZbm1aZiSh btUOAJR3aJftnW/lXM617oAuHa5ZLrMLojaDY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=qVTTBh0bwpq/7LX4AH3i8J6hvWgixRydT1B6XcBlpk0ibDfPil7aVcX73An5f8Qwaf pcI27NtsMfT87GKT/FhQh8A1SZB2Zxzku5CArEZttgsx2wHSLVVeMBJKFEFLqCYr9wxP zk+tAC6AhOs0NFKN6bTffABx+F1lo+7Y19oY0= MIME-Version: 1.0 Received: by 10.229.91.75 with SMTP id l11mr4338903qcm.24.1283842755956; Mon, 06 Sep 2010 23:59:15 -0700 (PDT) Received: by 10.229.84.142 with HTTP; Mon, 6 Sep 2010 23:59:15 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Sep 2010 01:59:15 -0500 Message-ID: Subject: Re: How to implement (generic) ACID on application level From: Jonathan Shook To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable ... some kind of what? On Mon, Sep 6, 2010 at 3:38 AM, Michal August=FDn wrote: > Thank you for the great link! > The mentioned solution is using locking but I would prefer some optimisti= c > strategy (because the conflicts are rare in my situation) but I'm afraid > that this is really the best solution... > So the solution is probably to use some kind of > 2010/9/6 Reza Lesmana >> >> I read an article about using CAGES with Cassandra to achieve locking >> and transaction... >> >> Here is the link : >> >> >> http://ria101.wordpress.com/2010/05/12/locking-and-transactions-over-cas= sandra-using-cages/ >> >> On 9/5/10, Michal August=FDn wrote: >> > Hello, >> > >> > we can read everywhere that Cassandra (and similar NoSQL solutions) >> > doesn't >> > support full ACID and (when we want to have ACID) we have to implement >> > ACID >> > in higher layers of our application. Are there some good resources on >> > how to >> > implement ACID on higher layers? I.e. how to implement repository >> > pattern/DAO with ACID support when Cassandra is the database. >> > >> > I'm sure that some pessimistic solution (locks) is absolutely unsuitab= le >> > for >> > Cassandra so the solution probably would deal with optimistic >> > concurrency... >> > >> > Thank you! >> > >> > Augi >> > > >