Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4E03CCD6.5020404@dude.podzone.net>
Date: Thu, 23 Jun 2011 17:31:34 -0600
From: AJ <aj@dude.podzone.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: No Transactions: An Example
References: <BANLkTi=MVU68oFDskXrkwDjDqj47QLxBfg@mail.gmail.com>
	<BANLkTinY2JK382Rog3VXJtvv560qakR1jw@mail.gmail.com>
	<BANLkTin_GLwVqArU36Q7xFOrF_EKWiRjmQ@mail.gmail.com>
	<BANLkTi=BBDDGbSO+YT8s6tGfsqT1HPUMYA@mail.gmail.com>
	<4E026E09.30306@dude.podzone.net>
 <BANLkTimEKRymd78EOgqQ4s+5qLYXU8wQgg@mail.gmail.com>
In-Reply-To: <BANLkTimEKRymd78EOgqQ4s+5qLYXU8wQgg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 6/23/2011 7:37 AM, Trevor Smith wrote:
> AJ,
>
> Thanks for your input. I don't fully follow though how this would work 
> with a bank scenario. Could you explain in more detail?
>
> Thanks.
>
> Trevor

I don't know yet.  I'll be researching that.  My working procedure is to 
figure out a way to handle each class of problem that ACID addresses and 
see if there is an acceptable way to compensate or manage it on the 
client or business side; following the ideas in the article.  I bet 
solutions exist somewhere.  In short, the developer needs to be fully 
versed in the potential problems that could arise and have ways to deal 
with it.  It's added responsibility for the developer, but if it keeps 
the infrastructure simple with reduced maintenance costs by not having 
to integrate another service such as ZK/Cages (as useful as they indeed 
are) then it may be worth it.  I'll let you know what I conclude.