From dev-return-21433-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Tue Mar 13 19:53:11 2012 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 12543968F for ; Tue, 13 Mar 2012 19:53:11 +0000 (UTC) Received: (qmail 10297 invoked by uid 500); 13 Mar 2012 19:53:10 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 10264 invoked by uid 500); 13 Mar 2012 19:53:10 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 10256 invoked by uid 99); 13 Mar 2012 19:53:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Mar 2012 19:53:10 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mfidelman@meetinghouse.net designates 207.154.13.48 as permitted sender) Received: from [207.154.13.48] (HELO server1.neighborhoods.net) (207.154.13.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Mar 2012 19:53:03 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id AD08FCC184; Tue, 13 Mar 2012 15:52:41 -0400 (EDT) X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1v+q5arwmEwn; Tue, 13 Mar 2012 15:52:35 -0400 (EDT) Received: from new-host-3.home (pool-173-76-134-212.bstnma.fios.verizon.net [173.76.134.212]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A6CDDCC171; Tue, 13 Mar 2012 15:52:34 -0400 (EDT) Message-ID: <4F5FA582.1010900@meetinghouse.net> Date: Tue, 13 Mar 2012 15:52:34 -0400 From: Miles Fidelman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Firefox/10.0.2 SeaMonkey/2.7.2 MIME-Version: 1.0 To: dev@couchdb.apache.org CC: Jan Lehnardt Subject: Re: Couchbase trademark issues References: <4F5EC423.2070101@shanecurcuru.org> <4F5EC691.3000602@shanecurcuru.org> <8BEA9BDA-F10A-4DB5-897B-5CE5D1DB2C0B@apache.org> In-Reply-To: <8BEA9BDA-F10A-4DB5-897B-5CE5D1DB2C0B@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Jan Lehnardt wrote: > > I'd be interested to hear what other measures you think Couchbase could > take? Feel free to take this to private@apache.couchdb.org to discuss > with the PMC as well. > One that that might help a lot is a really serious definition of what Couchbase is - particularly in visible locations like the front page of couchbase.com. While the name implies a close relationship to CouchDB, I really can't, for the life of me, find a clear description of what it does. I mean, CouchDB is very clearly: - "a document-oriented database that can be queried and indexed using JavaScript in a MapReduce fashion" - "A document database server, accessible via a RESTful JSON API." with http://couchdb.apache.org/docs/intro.html and http://couchdb.apache.org/docs/overview.html elaborating quite nicely. (Less visible is that CouchDB is a great application development platform. I refer to couchapps, of course). On the other hand, all I can figure out from couchbase.com is: - "Couchbase is open source NoSQL for mission-critical systems." and that one can - "spread your data across a cluster of machines and randomly access it with sub-millisecond latency" - and it's pretty quickly obvious that the most salient features of CouchDB (RESTful interface, application platform) are missing from Couchbase - by and large, it's completely useless for the kinds of things I'm working on (except maybe as a backend to add some scalability down the line) What CouchDB is, and why one might use it is very clearly defined. On the other hand, Couchbase materials (website, white paper, ...) make a generic case for NoSQL databases - but one that could equally apply to Hadoop, Riak, graph databases, and the whole range of NoSQL technologies and products. Seems to me that not only would a very clear use case and functional description for Couchbase help distinguish the two, but would also help Couchbase position itself in the space of available technologies and in the marketplace. If anything, the "Couch" in Couchbase implies that it's something like CouchDB - which it really isn't. At best, it's not very helpful, at worst it's rather misleading. Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra