From user-return-7968-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Thu Dec 10 17:27:05 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 77043 invoked from network); 10 Dec 2009 17:27:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Dec 2009 17:27:05 -0000 Received: (qmail 99111 invoked by uid 500); 10 Dec 2009 17:27:03 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 99022 invoked by uid 500); 10 Dec 2009 17:27:03 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 99012 invoked by uid 99); 10 Dec 2009 17:27:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2009 17:27:03 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 209.85.160.56 as permitted sender) Received: from [209.85.160.56] (HELO mail-pw0-f56.google.com) (209.85.160.56) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2009 17:26:53 +0000 Received: by pwi19 with SMTP id 19so40045pwi.35 for ; Thu, 10 Dec 2009 09:26:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Q/CazMSdTYp+UN/nAEQWQniGkPpvkvXxel3KbDjAjno=; b=MhMl0M+6WoxHRv6U+Kq8Adr9vtdr7t5V1VaRAllG5Zsa+MweVE1SzNqX9cnIhWHTqg kyHnSsJR1yGs8wwCuujYtTht++CtfHNHoW04WWOI4rZfNftycMwioEjTvQZlkL2uWYvk 71xyQx5kvtvZewvM4N0glr09qLz3g3/S6aN/A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=Cma5nKF5gi015e3pDplUKLR5FGvEZmwYj3QgLOdl/4QDqcmiekJXCcffNFgvgLULLW ljqPE/yCF9WsQcdsuL1EDCyUTGgagjK2IiFOQ2vtYXs0DWdRDD2wy2J2cVFhJJV0TqOP +b9GzSk0BVL4ZAjbfwvjX4H5YhO8aJH5NCWzw= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.143.25.19 with SMTP id c19mr126183wfj.87.1260465992482; Thu, 10 Dec 2009 09:26:32 -0800 (PST) In-Reply-To: <1260460317.3169.18.camel@leonardo-laptop> References: <1260460317.3169.18.camel@leonardo-laptop> Date: Thu, 10 Dec 2009 09:26:31 -0800 X-Google-Sender-Auth: 9f7d7a19283f904e Message-ID: Subject: Re: Should I use CouchDb? From: Chris Anderson To: user@couchdb.apache.org, l.rame@griensu.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 2009/12/10 Leonardo M. : > Hi, yesterday a friend sent me an email about CouchDb, and I kept > reading about it until late night, it sounds like it could solve a > problem I'll have this next year. > > Let me briefly explain what my company does, and the problem I'm facing. > The company let health organizations's (hospitals, clinics and > pharmacies) patients to pay by a local credit card, using our system, in > charge of credit validation. > > Currently the software runs on a server supported by Firebird 2.1, and > health organizations ask for authorization by phone or internet (not all > organizations have internet access in this side of the world), that's > because at this time, all organizations are not too far from our > building, they are located in the same town. > > In the near future, we are making arrangements with a couple of clinics > in other cities, and we want to let them to make authorizations online. > The problem here is we can't be sure the Internet access will be 100% > up, so I'm thinking of a multiple master redundancy schema, and after > reading about CouchDb, I think I found the solution to my problem. > > Should I choose CouchDb? CouchDB is specifically designed for occasionally-connected use cases. If you can fit your data model into CouchDB, then you should be able to run it in multiple locations, and reconcile/update data with replication when a network connection is available. > > -- > Leonardo M. Ram=E9 > http://leonardorame.blogspot.com > > --=20 Chris Anderson http://jchrisa.net http://couch.io