The most interesting piece of information is really how you expect to access the data. That should be the starting point for designing the data layout.
Also, ... What are the kinds of lookups typically needed? How many different "messages/" buckets do you expect? Order of magnitude numbers .... What kind of read/write performance do you expect? How big are the messages? Is the message/_meta object likely to be contended for writes? Kresten On Aug 16, 2012, at 1:05 PM, ZhouJianhua <jh.z...@outlook.com<mailto:jh.z...@outlook.com>> wrote: Hi, I want to store a list and append item to it later. Is it suitable to do this in riak? My scheme is like this: message: bucket of all messages; message/_meta: an object to store the first index and last index of list; message/n: key of message, such as message/1, message/2, ... I have never used key-value DB, and had no idea how to model. Any suggestion would be appreciated! _______________________________________________ riak-users mailing list riak-users@lists.basho.com<mailto:riak-users@lists.basho.com> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com Mobile: + 45 2343 4626 | Skype: krestenkrabthorup | Twitter: @drkrab Trifork A/S | Margrethepladsen 4 | DK- 8000 Aarhus C | Phone : +45 8732 8787 | www.trifork.com<http://www.trifork.com> _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
