And I was thinking of using JTA for transaction processing. I have no
experience with it but on the surface it looks like it should work.
On 6/21/2011 3:31 PM, AJ wrote:
What's the best accepted way to handle that 100% in the client? Retries?
On 6/21/2011 3:14 PM, Anand Somani wrote:
Not sure if it is that simple, a quorum can fail with writes
happening on some nodes (there is no rollback). Also there is no
concept of atomic compare-and-swap.
On Tue, Jun 21, 2011 at 2:03 PM, AJ <a...@dude.podzone.net
<mailto:a...@dude.podzone.net>> wrote:
On 6/21/2011 2:50 PM, Stephen Connolly wrote:
how important are things like transactional consistency for you?
would you have issues if only one side of a transfer was recorded?
Right. Both of those questions are about consistency. Isn't the
simple solution is to use QUORUM read/writes?
cassandra, out of the box, on it's own, would not be ideal if
the above two things are important for you.
you can add components to a system to help address these things,
eg zookeeper, etc. a reason why you moght do this is if you
already use cassandra in your app and are trying to limit the
number of databases
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random
nonsense words and other nonsense are a direct result of using
swype to type on the screen
On 21 Jun 2011 18:30, "AJ" <a...@dude.podzone.net
<mailto:a...@dude.podzone.net>> wrote:
