Hi, I'm new to riak, and have been busily reading though the wiki, watching the videos, and catching up on the mail list, so I will have lots of questions over the next few weeks - so sorry <grin>
To begin, I'm curious about the characteristics of the seven backends for riak [1] 1. riak_kv_bitcask_backend - stores data to bitcask 2. riak_kv_fs_backend - stores data directly to files in a nested directory structure on disk 3. riak_kv_ets_backend - stores data in ETS tables (which makes it volatile storage, but great for debugging) 4. riak_kv_dets_backend - stores data on-disk in DETS tables 5. riak_kv_gb_trees_backend - stores data using Erlang gb_trees 6. riak_kv_cache_backend - turns a bucket into a memcached-type memory cache, and ejects the least recently used objects either when the cache becomes full or the object's lease expires 7. riak_kv_multi_backend - configure per-bucket backends Unfortunately this amount of choice means I need to do my homework to make an informed decision ;-) so I'd love any pointers or to hear any advice on performance comparisons, best practices, backends for development vs deployment etc Kind Regards Neville [1] http://wiki.basho.com/display/RIAK/How+Things+Work#HowThingsWork-Backends
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
