From user-return-15657-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Wed Apr 06 08:10:49 2011 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 67069 invoked from network); 6 Apr 2011 08:10:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Apr 2011 08:10:49 -0000 Received: (qmail 59465 invoked by uid 500); 6 Apr 2011 08:10:47 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 59442 invoked by uid 500); 6 Apr 2011 08:10:47 -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 59434 invoked by uid 99); 6 Apr 2011 08:10:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 08:10:47 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,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 bchesneau@gmail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 08:10:39 +0000 Received: by bwj24 with SMTP id 24so1737219bwj.11 for ; Wed, 06 Apr 2011 01:10:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=aG9o8dTaZXSY+Bn3+7oe6XMq/njwpRgNUFfgvrDQMhc=; b=aF2SYQ/3jmcCbKh1zB1fAh4D3Ay+fKByB4bdrkVxmDRonGCNye1Etj2QowER/08JC6 ZsTZjBA2Tmqs8CQmgRwC8nwld3HAubS3Qx1s6rSEuclUJ6m4Ffg4+S1FtWb19DFP1T8R CA5FoSKnXq21CySjoKnGCi/pcjYPe7Zc4ZERs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Obf+h1NXNp6Af6uRm4o9mlxfUytRB0ibjKx18UdoAZgRmWIRygmEOec9Dy5lcCTXgh 5e7f2nLCQRfRsQR1uasyEZpeK2oDj44U9q63Uw6BhgCvz1YeZ009vHaoIYnBWQRxvwqp p2EHdybdulF9bn1R5QA2ElbxwwpUOtwRxqBpk= MIME-Version: 1.0 Received: by 10.204.74.68 with SMTP id t4mr555535bkj.22.1302077419560; Wed, 06 Apr 2011 01:10:19 -0700 (PDT) Received: by 10.204.130.81 with HTTP; Wed, 6 Apr 2011 01:10:19 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 Apr 2011 10:10:19 +0200 Message-ID: Subject: Re: tools to move to mongodb if necessary From: Benoit Chesneau To: user@couchdb.apache.org Cc: bryan rasmussen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Apr 6, 2011 at 10:03 AM, bryan rasmussen wrote: > Hi, > > I'm worried that in the future I might need to move to MongoDB, and if > it becomes necessary to make that move I should do so fairly quickly > (this is very much a 'be prepared for eventualities 6 months from now > sort of thing'), so I'm wondering if there are any tools out there to > make such a migration easier, and if there is anything I should > consider when making my couchdb databases in light of a need to > eventually migrate. > > My main worry is having data that expands very rapidly > > thanks, > Bryan Rasmussen > . > I would only think about it when the problem come. Also you have different alternatives to mongo if you're worry about elasticity: couchdb-lounge (? status) bigcouch/cloudant and some other that could come. - beno=EEt