Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 74.125.82.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=fOOkXPc5+nCq0NOMC6ASf1ZlfVcDiU0Li3aYmk8uxc1uzB8Vh8wE1ZMFj2DdqKgABj
         +7wPivHYf7f+vAQ2aL11SB6ASzL3Lkjp83EfYg8JCOCMDuMKwanHvX/xkiQERd5V9wQ8
         bAoXlnSYHEiWTXSfwCK7S4LV2qxrOY3cnlYio=
MIME-Version: 1.0
In-Reply-To: <4BE097C1.5080902@darose.net>
References: <4BE097C1.5080902@darose.net>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Tue, 4 May 2010 23:13:26 -0500
Message-ID: <p2ze06563881005042113v2d179205h9ff892b93bdb1025@mail.gmail.com>
Subject: Re: Building on top of Cassandra's core layer
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, May 4, 2010 at 4:55 PM, David Rosenstrauch <darose@darose.net> wrot=
e:
> I've had some neat ideas that I'd like to tinker with for a distributed D=
B
> that implements a very different data model than Cassandra. =A0However, I
> obviously don't want to reinvent the wheel - particularly because in the
> case of distributed systems, the wheel is quite complicated and hard to g=
et
> right.
>
> What I'm thinking would make more sense then is to build on top of the
> Cassandra core (since it's obviously been implemented well and has been
> proven to scale quite nicely) and then implement my own middle/top layer(=
s).
>
> So I'm wondering:
>
> * Anyone know if such a thing has been attempted before? =A0(And, if so, =
links
> to any stories about success / failure / tips.)

I believe Jun Rao and Sandeep Tata built a kind of chain replication
starting from Cassandra 0.4-ish.  I don't think the code is available.

> * Would there happen to be any docs/blogs/emails providing useful tech in=
fo
> for such an effort?

I don't know of any, short of the articles about Cassandra's code
itself.  Ran Tavory wrote an excellent survey piece:
http://prettyprint.me/2010/05/02/understanding-cassandra-code-base/

> * What I should include/exclude from the Cassandra source code to start
> building on? =A0Or, in other words, which package(s) from the source woul=
d be
> considered to constitute the core layer?

I don't see any shortcuts here.  You need to understand the code
enough to answer that question yourself.

--=20
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com