Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates
 209.85.215.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=Nj2LTNr7D8+qDvBm0mUQHcjUtWkMJPEoziNS9LDZXATqZuFoGHXFUNsBAjpvW4rWKN
         qnv/s2/uMmC4dVhRUsYlINFAwJpx4gwYIarRMdcbCVHj+X9URR8hKwrOmwG12R24027g
         wyBvM2TLXx3l85NaYxEaT48COnP3Hh4agtPiY=
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: <AANLkTing--2nTF9tQh08bHFKH7EVECYr7KFkyN9h0dYt@mail.gmail.com>
References: <AANLkTing--2nTF9tQh08bHFKH7EVECYr7KFkyN9h0dYt@mail.gmail.com>
Date: Wed, 8 Sep 2010 08:32:40 -0700
Message-ID: <AANLkTincR+qsOF8oQPQPCOZ9HfONauDbeqOyD7mnHXsu@mail.gmail.com>
Subject: Re: asynchbase: A new entirely asynchronous / non-blocking HBase
 client
From: Stack <stack@duboce.net>
To: user@hbase.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Just to say that I've been reviewing this code on and off for a while
now.  Its great stuff.  Not only is it non-blocking netty-based, at
its core it has a clone of the Twitsted Deferred [1] implementation
which looks like a sweet pattern for non-blocking network programming
but would look to be useful beyond this use case, for example
implementing a server core.

St.Ack

1. http://twistedmatrix.com/documents/10.1.0/api/twisted.internet.defer.Def=
erred.html

On Wed, Sep 8, 2010 at 2:22 AM, tsuna <tsunanet@gmail.com> wrote:
> Hello,
> I use Netty extensively, and for a long time I wanted to have a fully
> asynchronous / non-blocking and thread-safe HBase client. =A0So I ended
> up writing one from scratch, which I just released at:
> http://github.com/stumbleupon/asynchbase
>
> It's rather different from HBase's own client (HTable). =A0The core of
> asynchbase is made of HBaseClient (javadoc @ http://su.pr/1PJCSY), and
> you normally need only a single instance (vs. one per table with
> HTable). =A0This instance is entirely thread-safe (I think :D) and
> scales well in my limited loadtests (on a 4 core machine it scales
> linearly). =A0I wrote it originally for another project that relies
> heavily on HBase and Netty (a scalable time series database we use for
> monitoring at StumbleUpon =96 http://opentsdb.net), which is gonna be
> open sourced most likely during the last week of September. =A0In some
> write-heavy code paths I'm seeing a 3x to 4x throughput improvement
> with asynchbase.
>
> There's a heated debate ongoing at StumbleUpon about the license of
> the client. =A0Stack wants to use it in HBase itself, but the LGPLv3+ is
> unfortunately incompatible with the ASF license. =A0Others simply seem
> to dislike anything with the substring "GPL" in it (:D). =A0I haven't
> had much time to find another license yet, but I think we're going to
> switch to something like a BSD or MIT style license. =A0I'm going in
> vacation soon so I wanted to get some feedback from other HBase users
> instead of blocking on this stupid and annoying licensing issue.
>
> Your feedback or patches would be most welcome!
>
> PS: The source code
> (http://github.com/stumbleupon/asynchbase/blob/master/src/HBaseRpc.java)
> contains an unofficial documentation of the Hadoop and HBase RPC
> protocols as well as Hadoop's variable-length encoding for integer
> values. =A0I've heard that others may be interested in implementing
> native HBase clients in non-Java languages, so I thought I'd pass this
> around to save their time.
>
> --
> Benoit "tsuna" Sigoure
> Software Engineer @ www.StumbleUpon.com
>