Thank you so much, looks nice, I'll be looking into it.
On 2/22/2012 3:08 PM, Rob Coli wrote:
On Wed, Feb 22, 2012 at 10:37 AM, Maxim Potekhin <potek...@bnl.gov
<mailto:potek...@bnl.gov>> wrote:
The idea was to provide redundancy, resilience, automatic load
balancing
and automatic repairs. Going the way of the file system does not
achieve any of that.
(Apologies for continuing slightly OT thread, but if people google and
find this thread, I'd like to to contain the below relevant
suggestion.. :D)
With the caveat that you would have to ensure that your client code
streams instead of buffering the entire object, you probably want
something like MogileFS :
http://danga.com/mogilefs/
I have operated a sizable MogileFS cluster for Digg, and it was one of
the simplest, most comprehensible and least error prone parts of our
infrastructure. A++ would run again.
--
=Robert Coli
rc...@palominodb.com <mailto:rc...@palominodb.com>
