cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Les Hazlewood <>
Subject Re: 99.999% uptime - Operations Best Practices?
Date Thu, 23 Jun 2011 18:14:41 GMT
> In the spirit of your re-formulated questions:
>>  - Read-before-write is a Cassandra anti-pattern, avoid it if at all
>> possible.
> This leads me to believe that Cassandra may not be a good idea for a
> primary OLTP data store.  For example "only create a user object if email
> foo is not already in use" or, more generally, "you can't create object X
> because one with an existing constraint already exists".
> Is that a fair assumption?

Actually, this may not be true, at least using Digg and Twitter as examples.
 I'd assume those apps are far more read-heavy than they are write-heavy,
but I wouldn't know for sure.

View raw message