Hi Georgio, There are many possible ways to do something like this. Riak CS in particular chunks large files into immutable data blocks, and has manifests pointing to those blocks to track versions of files. Manifests and blocks are each stored in their own riak object. There are some tricks around manifest merging that take into account the eventually consistent nature of Riak CS, and there are quite a few other gotchas around building a system like this on top of Riak, including undocumented performance hacks.
Riak CS additionally provides S3 API compatibility and is a commercially supported product, built by people that also work on Riak and strive to make the product as fast and reliable as possible on a daily basis. And crazier than that, it's free and open source! It doesn't sound like your goal is to build an object store, but to build a good product on top of an object store. In this case, I'd say just use Riak CS and develop your application. If CS doesn't meet your measured needs for latency than build your own store, or better yet help fix Riak CS :) Best of luck, Andrew On Tue, Dec 10, 2013 at 5:29 AM, Georgio Pandarez <georgiopanda...@gmail.com > wrote: > Hi, > > I have noticed that Riak-CS can shard (that is split) large keys > automatically across nodes. I would like to achieve a similar outcome with > Riak itself. Is there any best practice to achieve this? Could a portion of > Riak-CS be used or should I just bite the bullet and use Riak-CS? > > Latency is key for my application and I wanted to avoid the additional > layer Riak-CS provides. > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
