Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C0DE49F48 for ; Mon, 19 Sep 2011 12:30:50 +0000 (UTC) Received: (qmail 88612 invoked by uid 500); 19 Sep 2011 12:30:49 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 88553 invoked by uid 500); 19 Sep 2011 12:30:48 -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 88543 invoked by uid 99); 19 Sep 2011 12:30:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2011 12:30:48 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shoefish@gmail.com designates 209.85.161.180 as permitted sender) Received: from [209.85.161.180] (HELO mail-gx0-f180.google.com) (209.85.161.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2011 12:30:42 +0000 Received: by gxk5 with SMTP id 5so1918134gxk.11 for ; Mon, 19 Sep 2011 05:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=O3FaorVfdt2A2wdlBoakC/84rRSm0Bhjh4oLoqVc6Hg=; b=lxmG3ly3G1+SxcisOJYMqPYXo5lPfFTzH5vOxZ3Ux7h0nZLsualjOeujK1JPpaZyRb mxI3DBk/7g1Qnx9jwLssrObvD81HAqno+9OuWdVBuqmO510f/f9QXbPhOQLOknWoBisj CVrxEmzAQU3LUCZUGPQh8BfGNQA3q15B7iTcw= MIME-Version: 1.0 Received: by 10.150.219.17 with SMTP id r17mr2287429ybg.240.1316435421899; Mon, 19 Sep 2011 05:30:21 -0700 (PDT) Received: by 10.150.212.2 with HTTP; Mon, 19 Sep 2011 05:30:21 -0700 (PDT) Date: Mon, 19 Sep 2011 15:30:21 +0300 Message-ID: Subject: does CouchDB fit my project? From: daniel davis To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=000e0cd47e72b12c1004ad4a81d2 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd47e72b12c1004ad4a81d2 Content-Type: text/plain; charset=ISO-8859-1 Hello, I think that CouchDB is a good fit for the project i'm working on but I'm not sure. I would appreciate advice. what I have is a central server in charge of tracking items, their bar-codes and whether those bar-codes were scanned and several devices doing the scanning. performance is important. data has no relations. due to customer requirements I need the data on the items locally on the devices and as current as possible. the network connection is expected to be patchy at times. when a device scans an item it must be notified if it was already scanned. what I thought I can do was: 1) run a local couchDB server on each of the devices and have them continually replicate the server's database, this way I have a good syncing implementation that I don't need to build from scratch. 2) to keep things simple at this point I will only make actual changes to the documents on the server and have those changes replicated onto the clients, trusting couchDB to send me an error HTTP response if two devices try to mark the same item as scanned (the first will update the document, then the second's command revision won't be appropriate anymore) since for now I'd rather avoid conflicts than deal with them. I have come across criticism that this will leave me very susceptible to network errors, is the incremental replication process give me reasonable protection? does this sound workable? has this issue been resolved yet? => http://www.mail-archive.com/user@couchdb.apache.org/msg02711.html --000e0cd47e72b12c1004ad4a81d2--