As I see it, there are a few advantages - You get Riak's built-in redundancy. The various chunks of your file will be written in multiple locations across your cluster. Even in the event of a single server failure, you'll still be able to read data out of your luwak cluster.
Performance - I would think that there's a performance boost since you can, in theory, serve more files through the same luwak cluster than you could serve through a single file server (unless that file server itself were also clustered and attached to a SAN). If you're storing text (or some other easily understood format) you can use MapReduce to perform queries across your files instead of having to write some kind of file system crawler. Jeremiah Peschka Microsoft SQL Server MVP MCITP: Database Developer, DBA On Tue, Jan 25, 2011 at 8:56 AM, Joshua Partogi <[email protected]>wrote: > From the wiki: > "Luwak works by breaking large files into blocks and storing each block as > a separate Riak object" > > But what does not get mentioned is the advantage of it. Does it make > serving files faster? Or does it save more space in HD? > > Thanks heaps for your assistance. > > -- > http://twitter.com/jpartogi <http://twitter.com/scrum8> > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
