hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Kellerman <...@powerset.com>
Subject RE: Why is scaling HBase much simpler then scaling a relational db?
Date Wed, 20 Aug 2008 21:16:31 GMT

In general you will get a quicker response to HBase questions by posting them to the HBase
mailing list (hbase-user@hadoop.apache.org) see http://hadoop.apache.org/hbase/mailing_lists.html
for how to subscribe.

Perhaps the best document on scaling HBase is actually the Bigtable paper:

Jim Kellerman, Senior Engineer; Powerset (a Microsoft Company)

> -----Original Message-----
> From: the.stuart.sierra@gmail.com [mailto:the.stuart.sierra@gmail.com] On
> Behalf Of Stuart Sierra
> Sent: Wednesday, August 20, 2008 1:03 PM
> To: core-user@hadoop.apache.org
> Subject: Re: Why is scaling HBase much simpler then scaling a relational db?
> On Tue, Aug 19, 2008 at 9:44 AM, Mork0075 <mork0075@googlemail.com> wrote:
> > Can you please explain, why someone should use HBase for horizontal
> > scaling instead of a relational database? One reason for me would be,
> > that i don't have to implement the sharding logic myself. Are there other?
> A slight tangent -- there are various tools that implement sharding
> over relational databases like MySQL.  Two that I know of are
> DBSlayer,
> http://code.nytimes.com/projects/dbslayer
> and MySQL Proxy,
> http://forge.mysql.com/wiki/MySQL_Proxy
> I don't know of any formal comparisons between sharding traditional
> database servers and distributed databases like HBase.
> -Stuart
View raw message