Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.213.180 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=uqxuK7zMPVd0zfvcF6pRG0vM2gtBfCgS8cA/8Sv+7C7IcZMKXlMuQcQaQOjf8or+Ck
         1gfDgp9qQe6OO5KcsYgrPLWisHI3vpH/FfAEITFvbl5TF0vjcP+Dmi2gmKLEMlpUHJFD
         UnLwZCaccRdCSXCiaGrR5xq338/kvPsbGvAI4=
MIME-Version: 1.0
In-Reply-To: <AB864015-F91E-45C7-A7AC-A3F01ADB243F@calftrail.com>
References: <00AB9C0F-D7E0-4E76-B1AA-0A36CD47E2A7@apache.org>
 <AANLkTi===_Xiiz_GgNm=ojn4gVta-hPpEtRaaUS9yz8W@mail.gmail.com>
 <AB864015-F91E-45C7-A7AC-A3F01ADB243F@calftrail.com>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Tue, 8 Feb 2011 13:26:57 -0500
Message-ID: <AANLkTi=1yBe4Qt54UdvWkosOOQ8d=PmrH0t310pAGF0Q@mail.gmail.com>
Subject: Re: CouchOne + Membase = Couchbase
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> A few months ago, I read about BigCouch:
> =A0 =A0BigCouch =3D (CouchDB + Amazon Dynamo clustering theory)
> That sounds neat, and I was getting the impression this was done in Erlan=
g in such a way it could become part of core and was excited for it.
>

It is and there's still a general agreement that it will be. The
issues holding it back are mostly technical in that we need to
refactor our source tree which is being held up by things like waiting
for the new replicator to land.

> Now I'm trying to figure out what Couchbase is, and my reading indicates:
> =A0 =A0Couchbase =3D (Memcached + magic) + (CouchDB + ponies)
>
> Will these new dependencies make CouchDB harder to compile and use for pe=
rsonal deployments? How does merging in an in-memory cache provide the clus=
tered resiliency I was hoping would be possible by using BigCouch? I'd neve=
r heard of Membase before last night, so I guess I'm just feeling a bit lik=
e a nervous IT guy hearing the platform he relies on is about to change in =
ways he doesn't understand.
>

Couchbase is not Apache CouchDB. There are no new dependencies that
are suddenly going to be required by CouchDB.

> I'd feel more comfortable if I knew what the magic and ponies really were=
 at a code base level, so I could understand better how they will change th=
ings for me and my little Couch apps. I can tell the CouchOne guys are exci=
ted about this, though, and trust it means good things for the CouchDB comm=
unity.

For the foreseeable future, absolutely nothing is going to change for
you. Its always possible that we'll start to see some patches coming
back from Couchbase employees into Apache CouchDB, but as with all
other development they'll go through the same development processes
we've been using since CouchDB came to Apache.