he business can handle a rare
> incomplete transaction, then this might be acceptable.
>
>
>
> On 6/22/2011 9:14 AM, Sasha Dolgy wrote:
>
>> I would still maintain a record of the transaction ... so that I can
>> do analysis post to determine if/when problems occurred ...
oes, ZooKeeper can be scaled by having several clusters
> and hashing lock paths to them. Alternatively, Lamport's bakery algorithm
> could be investigated as this shows you can have locking without a central
> coordinator service.
>
> Best, Dominic
>
>
> On 22
ms occurred ...
>
> On Wed, Jun 22, 2011 at 4:31 PM, Trevor Smith wrote:
> > Sasha,
> > How would you deal with a transfer between accounts in which only one
> half
> > of the operation was successfully completed?
> > Thank you.
> > Trevor
>
lumn family. one row per account ... each column for
> transaction data and one column for the actual balance.
> just so long as you use whole numbers ... no one needs pennies anymore.
> -sd
>
> On Wed, Jun 22, 2011 at 4:18 PM, Trevor Smith wrote:
> > Hello,
> > I was wonderi
-transactional datastores in general).
Consider the simple system that has accounts, and users can transfer money
between the accounts.
There are these interesting papers as background (links below).
Thank you.
Trevor Smith
http://www.ics.uci.edu/~cs223/papers/cidr07p15.pdf
http://blogs.msdn.com/cfs
