Yes, with such requirement as "put key if not exists already" you must implement some locker or do it with single writer. Both of this cancel "availability" property (but you could spread "single writers" or "lockers" with same mechanism as riak do, with help of riak_core and custom code).
-- View this message in context: http://riak-users.197444.n3.nabble.com/Is-Riak-suitable-for-s-small-record-write-intensive-billion-records-application-tp4025684p4025700.html Sent from the Riak Users mailing list archive at Nabble.com. _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
