Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of papersmith@gmail.com
 designates 209.85.132.248 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=nplHMsUs1U1PDBvuk42vb7pz8Q3uFCOzW2rmp0FXWF8XiRxkl8nTxZuYxKM3PfrsTJLJXNMilPHAaU3nkFcXgX1ZHfTcSEVJZH8YseMgHzSEyqT50cpcZhDiLHyAjPLvZg5aMv+JxAXRVwDoKGhFHI9Zgw4aOUoI83OEi28gvwo=
Message-ID: <99849f280803101629v6438e9f8r32038c201f72f81a@mail.gmail.com>
Date: Mon, 10 Mar 2008 16:29:11 -0700
From: "B W" <papersmith@gmail.com>
To: couchdb-user@incubator.apache.org
Subject: Re: Questions regarding readiness for production environment
In-Reply-To: <37815532-9007-43C8-AB4D-8380892CF3DD@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_54922_29847812.1205191751450"
References: <99849f280803101451w696a5e4dud397d23b1c7b32f@mail.gmail.com>
	 <37815532-9007-43C8-AB4D-8380892CF3DD@gmail.com>

------=_Part_54922_29847812.1205191751450
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Jan,

Thanks for the prompt reply.

On Mon, Mar 10, 2008 at 3:56 PM, Jan Lehnardt <janlehnardt@googlemail.com>
wrote:

> Hi,
> On Mar 10, 2008, at 14:51 , B W wrote:
> > I am currently working on a public-facing web app and I would love
> > to use
> > couchdb.  I apologize if these question have been asked before, but
> > seeing
> > couchdb is in active development, it'd be nice to have some updated
> > info.
>
> What's you web app about? (if you want to share :)
>

The general idea right now is a site for organizing events.  The idea is
still not polished, so I'll be adding more features as I go, that's why I
find couchdb's flexible schema attractive. :)

>
>
> > The web site says the interface is stable enough for application
> > development, but what about implementation-wise as of 0.7?  I don't
> > have an
> > urgent need for the features on the wiki road map right now since
> > it's a new
> > project, but I was wondering if there are any performance caveats or
> > major
> > bugs I need to be aware of?
>
> The API, particularly dealing with attachments is still in flux now. I
> don't
> know of any show-stopping bugs, though. CouchDB is not yet optimised for
> speed. While fast enough for tests, it could be a lot faster. One
> thing you will
> encounter pretty quickly is that database size grows fast at the
> moment when
> you add or delete documents. The process to deal with that
> (compaction) is
> just being implemented. If you don't want to wait for that, you can
> still manually
> compact your databases by bulk copying their contents to new temporary
> dbs and then switch over regularly. Sounds like a bit of a chore and
> it is,
> but it works.
>
> With us, "alpha" means that we do not have all the features in we want
> for
> a first major release, but the things that are in are pretty stable.
> We still
> don't recommend using  CouchDB for anything mission-critical, as we
> can't
> vouch for the safety of your data. That said, the current code-base
> didn't
> show any critical bugs as of yet. But don't quote me on that if you lose
> your data :-)
>

>
>
> > I'm also wondering what kind of time frame should I expect for the
> > next
> > major releases?
>
> I can't make any commitments here, but we try to get the compaction out
> to you as quickly as possible.


That would be great! :D  One question though, once compaction is added, will
it have compatibility problem with my existing un-compacted data?


Thanks!

Bob

------=_Part_54922_29847812.1205191751450--