Is Riak suitable for s small-record write-intensive billion-records application?

Reid Draper reiddraper at gmail.com
Thu Oct 18 10:53:22 EDT 2012


On Oct 18, 2012, at 7:42 AM, Yassen Damyanov <yassen.tis at gmail.com> wrote:

> Hi everyone,
> 
> Absolutely new (and ignorant) to NoSQL solutions and to Riak (my
> apologies; but extensive experience with SQL RDBMS).

--snip--

> 
> The application should be able to write several hundreds of new
> records per second, but first check if the unique key already exists.
> Writing is to be done only if it is not there. If it is, the app needs
> to retrieve the whole record and return it to the client and no
> writing is done in this case.

Since Riak is an eventually consistent database, you will not be able to tell
with 100% certainty that a key or does not exist. If this is a _firm requirement_,
you'll need to either use another db or some external service to provide this
guarantee.

Reid

> 
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com





More information about the riak-users mailing list