On Wed, Jan 11, 2012 at 10:56 AM, Vishal Shah <gold...@gmail.com> wrote:
> To add to Ian's comment, for me personally, this specific characteristic is
> in fact a very important distinguishing feature of Riak vs other scalable KV
> systems. To me, this is what separates
Yes, but it makes it unusable for anything that requires atomic
operations. A group here just went with elasticsearch - partly
because of the full lucene indexer and range queries, but mostly
because they wanted redundant data feeds and an atomic operation to
reject duplicates. And as a nice side effect, you can run a
client-only node that doesn't store data on the same box with the
application so you don't need to go through a separate load balancer
to deal with failures of the node the app is configured to use.
--
Les Mikesell
lesmikes...@gmail.com
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
