cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Prescod <>
Subject Re: Memcached protocol?
Date Mon, 05 Apr 2010 16:20:06 GMT
On Mon, Apr 5, 2010 at 1:02 AM, David Strauss <> wrote:
> ...
> But your "write then read" model lacks the atomicity of the memcached
> API. It's possible for two clients to read the same value.

Do you have an example application where this particular side effect
of eventual consistency is problematic? Obviously memcached and
Cassandra are different because of eventual consistency. The question
is whether they are different enough to break an inconvenient number
of real applications. Do you depend on add returning a unique number
to each client in an application you've deployed? I have always
imagined it as being primarily for simple counters.

 Paul Prescod

View raw message