When writing a large number of small entries into a bucket is easy and efficient when writing, the penalty you pay is that instead it becomes expensive when you try to read the values, since you most likely will not know these keys. If you need to look at these keys up the secondary index, key filter, or, even worse, go through all the keys in the bucket (which is a very difficult operation and is never recommended for a production environment), it will be significantly less efficient than extracting data by key, and also not scaling.
Riak , , , , . , , , .
, , , . , , , , - -. , . , , , ( ), , . . , , . 3, 14:15 14:20 2013/03/07, "server3_20130307_1415". , 5- "server3_20130307_1420". , .
, , , , . , , , , , Riak 1-2 . , , .
, . , , "server3_20130307_14", 14: 00-15: 00. , .
, , . , , ( "allow_mult" true "last_write_wins" false [1]). , Riak , , , . , , .
, , , ( ), .
[1] http://docs.basho.com/riak/latest/references/apis/http/HTTP-Set-Bucket-Properties/