cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Les Hazlewood <...@katasoft.com>
Subject Re: 99.999% uptime - Operations Best Practices?
Date Thu, 23 Jun 2011 18:00:52 GMT
On Thu, Jun 23, 2011 at 10:41 AM, Chris Burroughs <chris.burroughs@gmail.com
> wrote:
>
>
> 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?

Thanks,

Les

Mime
View raw message