Regardless of Traackr or whatever mud/fud the Hypertable folks want to
sling, let's not lose focus on what we're doing: building the most
scalable, solid, data storage system out there.
It's nice to learn lessons from folks who have moved off of HBase or
those who want to try to compete. But also keep in mind that though we
might have lost one user, we've gained so many other much larger
installs in the last year or two - I won't sweat the loss of a few
people over to MongoDB. They'll always crush us on feature set, but
we'll always crush them on so many other dimensions. We can't be all
things to all people, so let's keep with what we're good at.
One nice anecdote: I recently gave a talk comparing HBase and Accumulo
in which I tried to use one slide to show a comparison of community
size and number of production deploys. I quickly ran out of space on
the slide for all the logos of HBase users (while the other half of
the slide had one nice big one).
On Wed, Feb 8, 2012 at 10:31 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
> I read the report from traackr where the author mentioned that the size of
> data may out grow MongoDB approach.
> I think we do need to make HBase more user friendly. This involves making
> setup easier, parameter tuning more dynamic (HBASE-5349, etc) and
> ultimately, adding secondary index support.
> On Wed, Feb 8, 2012 at 8:54 AM, Stack <[EMAIL PROTECTED]> wrote:
>> The Hypertable crew are throwing stones again. See
>> if you haven't already. ("Shock! Horror! Java App GCs when
>> misconfigured!"). J-D did a bit of a response. We should do a
>> comparison some day (Volunteers?). It seems like hypertable has some
>> nice ergonomics that we could pickup where it changes allocations
>> based on the incoming loading. Its probably time too to look at
>> default tunings again so out of the box we run smooth when suites like
>> performance evaluation are set running.
>> This article by George and the lads over at Traackr is more
>> interesting in my opinion:
>> There are reminders for us therein: e.g. some more attention to ease
>> of operation. This is not news I know -- and our letting go of the
>> (unsatisfactory) built-in secondary indexing contrib left them a high
>> and dry (we could have done better messaging around these contribs it
>> seems) -- but nonetheless a timely reminder from the lads over at
>> Traackr (sorry to see you go George and crew).
Software Engineer, Cloudera