Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 8287 invoked from network); 11 Sep 2008 08:14:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Sep 2008 08:14:09 -0000 Received: (qmail 92030 invoked by uid 500); 11 Sep 2008 08:14:04 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 92005 invoked by uid 500); 11 Sep 2008 08:14:04 -0000 Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-user@incubator.apache.org Delivered-To: mailing list couchdb-user@incubator.apache.org Received: (qmail 91994 invoked by uid 99); 11 Sep 2008 08:14:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Sep 2008 01:14:04 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jrhuggins@gmail.com designates 209.85.146.180 as permitted sender) Received: from [209.85.146.180] (HELO wa-out-1112.google.com) (209.85.146.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Sep 2008 08:13:05 +0000 Received: by wa-out-1112.google.com with SMTP id m16so210272waf.6 for ; Thu, 11 Sep 2008 01:13:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=HmCiNIgLUW6c+8dDlu8YnLO8+54Q9gJU/a+5NbtPKM0=; b=Wq2X3jT8eCeKAhPUeuNA6fANKSqsYDXI8gWTGUnUCX++I3sjaxjPW2cC8kf+vA6f5H ZrIu+ab0KE3QHvkFeE+5nyDHHEsCYJKeSsigW0lkhTlQ35MI14HkXACOOYG4TXOl1Aqs bU78uXDwaDl93wms/ijpFi2yHpresvNhVmY3Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=Uf2h2uYrWlOky60ynDlbws97urmdX/qKublJi/paDiVyUtutTVkXHpCiGdlvqpNUbP GUPhW1ctA+lS8ChJMYnkYyXGnC3IpgQ1TrA6WuDDdJbqVyFZy9XFJv61mPfYL+t5nXRx Ecy8+rQvj0R0JnyyPI24StHu0NxWSGPR5dV0A= Received: by 10.114.170.1 with SMTP id s1mr1721986wae.17.1221120807878; Thu, 11 Sep 2008 01:13:27 -0700 (PDT) Received: by 10.114.134.14 with HTTP; Thu, 11 Sep 2008 01:13:27 -0700 (PDT) Message-ID: <53b9568a0809110113j5957cc25te825e24797e48092@mail.gmail.com> Date: Thu, 11 Sep 2008 01:13:27 -0700 From: "Jason Huggins" Sender: jrhuggins@gmail.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: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <888cd9180809101939g6ff59e10gf5093aec905344ef@mail.gmail.com> X-Google-Sender-Auth: 2a50d989f9a41436 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Sep 10, 2008 at 7:39 PM, Brad King wrote: > 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. I suspect you might be making things more complicated for yourself by trying to use a Postgres *and* CouchDB solution. I think you'll have less stress in your life if you can just pick one and run with it. With that said, however, if you use a debian-based system like ubuntu... I found these instructions remarkable easy and clear for installing CouchDB: http://barkingiguana.com/2008/06/28/installing-couchdb-080-on-ubuntu-804 And installing CouchDB on future versions of ubuntu will be as simple as: "apt-get install couchdb" Regarding data backups, I fell in love with CouchDB's simple replication story after trying to figure out how to "architect" a real-time-replication and backup/restore strategy for MySQL for my Amazon EC2-based startup. Real-time replication (what MySQL people would call a Multiple Master-Multiple Slave setup) and backup/restore for CouchDB is child's play compared to the work involved for the other databases. (I used to be an Oracle DBA.) Since my data storage needs matched CouchDB's "document-centric" view of the world... CouchDB was a better fit for me -- but my "conversion experience" to CouchDB is mostly because of it's database backup and replication. Long story short --- if you pick CouchDB -- your operations team will probably love you for the work you just saved them. :-) > Is anyone else in the SaaS business taking the plunge here with > CouchDB. Yes! But alas, I'm in "stealth mode" with my startup -- so I can't go into any more detail, but I can say I'm betting on CouchDB in a big way. > Am I insane for even considering it? It depends... :-) Classic advice applies -- use the right tool for the job... If your data is "document-y" -- invoices, purchase orders, status reports, meeting notes -- a non-relational db like CouchDB might make more sense... If you feel like you're struggling to fit your data into CouchDB's world view... then it might be the wrong tool for you... Other great advice -- "your company's project isn't the school science fair" -- using relatively new technology - no matter how promising it is -- comes with higher risk for your project -- be prepared to find bugs and deal with API changes as CouchDB is still "pre 1.0". If "failure is not an option" for you -- don't treat your project as a grand science experiment of new technologies. Try doing a few proof-of-concepts with your idea and build-up technical experience with the tools and your proposed design before going "all in". Cheers, Jason Huggins, happy CouchDB user