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 jwall@google.com designates
 216.239.33.17 as permitted sender)
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=message-id:date:from:to:subject:in-reply-to:mime-version:
	content-type:references;
	b=YrH902DCI12lCMXE4Jylycc0Z7FhTcY+AIKF+AKIBPgqhm4/o4BzpEYcA/DowuuUA
	wGZ/ERyfyb3f4SQI91lTQ==
Message-ID: <7c40ded80809101947i673b79fcsd80f2ad95cf4be2f@mail.gmail.com>
Date: Wed, 10 Sep 2008 21:47:35 -0500
From: "Jeremy Wall" <jwall@google.com>
To: couchdb-user@incubator.apache.org
Subject: Re: Inventory on CouchDB
In-Reply-To: <888cd9180809101939g6ff59e10gf5093aec905344ef@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_22520_30489085.1221101255813"
References: <888cd9180809101939g6ff59e10gf5093aec905344ef@mail.gmail.com>

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

I may be wrong but I didn't think CouchDB was all that hard to install and
maintain. Do you have some specific concerns about deployment and
maintenance?

I definitely feel you about the self joins. If I had had something like
CouchDB availableto me about 2 years ago a number of different projects
would have been much much simpler.

On Wed, Sep 10, 2008 at 9:39 PM, Brad King <brking@gmail.com> wrote:

> This is more of a business related post than technical, so bear with
> me. I love how couchdb works: its elegant, it works how I think, it
> can accept any reasonably structured data. My decision to make is
> whether or not to take our company onto this new ground for a mission
> critical system: customer product data. Technically we call it
> "inventory" but I plan to keep all of the quantity control in
> Postgres, so its really just product data. We have some really big
> customers, with hundreds of thousands of products. It has to work, it
> can't fail. This data feeds everything else in our system.
>
> I have a vision for this great marriage of Postgres for inventory
> quantity managment and CouchDB for customer specific product data
> catalogs, but I'm struggling with what I think our Operations team can
> realistically manage for keeping these CouchDB systems up, running ,
> backed up, and easily deploying new servers for new customers.
>
> Is anyone else in the SaaS business taking the plunge here with
> CouchDB. Am I insane for even considering it? I'm just tired of
> writing self joins against unindexed fields in sql to handle
> variations in product schema per customer, it just doesn't make sense.
>

------=_Part_22520_30489085.1221101255813--