Return-Path: X-Original-To: apmail-couchdb-marketing-archive@minotaur.apache.org Delivered-To: apmail-couchdb-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1359210416 for ; Thu, 7 May 2015 05:39:24 +0000 (UTC) Received: (qmail 61586 invoked by uid 500); 7 May 2015 05:39:24 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 61548 invoked by uid 500); 7 May 2015 05:39:24 -0000 Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@couchdb.apache.org Delivered-To: mailing list marketing@couchdb.apache.org Received: (qmail 61536 invoked by uid 99); 7 May 2015 05:39:23 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 May 2015 05:39:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 3136CC2E83 for ; Thu, 7 May 2015 05:39:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.001 X-Spam-Level: **** X-Spam-Status: No, score=4.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_LAZY_DOMAIN_SECURITY=1, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id p5AIe99q7FtV for ; Thu, 7 May 2015 05:39:09 +0000 (UTC) Received: from smtpcmd02111.aruba.it (smtpcmd02111.aruba.it [62.149.158.111]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id 76467201C1 for ; Thu, 7 May 2015 05:39:08 +0000 (UTC) Received: from mail-ig0-f176.google.com ([209.85.213.176]) by smtpcmd02.ad.aruba.it with bizsmtp id Qtf51q00H3ov35t01tf5wP; Thu, 07 May 2015 07:39:06 +0200 Received: by iget9 with SMTP id t9so5075895ige.1; Wed, 06 May 2015 22:39:05 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.62.148 with SMTP id y20mr12361539igr.17.1430977145392; Wed, 06 May 2015 22:39:05 -0700 (PDT) Received: by 10.107.57.193 with HTTP; Wed, 6 May 2015 22:39:05 -0700 (PDT) Received: by 10.107.57.193 with HTTP; Wed, 6 May 2015 22:39:05 -0700 (PDT) In-Reply-To: References: Date: Thu, 7 May 2015 07:39:05 +0200 Message-ID: Subject: Replication VS Couchapps story: are they opposites or can live together? From: Giovanni Lenzi To: user@couchdb.apache.org, dev@couchdb.apache.org, marketing@couchdb.apache.org Content-Type: multipart/alternative; boundary=047d7bdcab346ed59d0515775416 --047d7bdcab346ed59d0515775416 Content-Type: text/plain; charset=UTF-8 Answer to this question should be pretty straigthforward given they always have lived together. But here I would like you to reflect on their concepts, in order to draw a line on what is the real innovating feature couchdb should point on for the future. Imho couchdb replication is simply awesome, but it is a system feature. Even if couchdb may have a unique master/master one, every db, sql or nosql, have some kind of replication. Coming to couchapps.. imho they ARE unique. Giving them a proper platform-indipendent and browser-only development environment and improving their weaknesses, they could really represent a differentiating feature from competitors. So I think they can live together of course, but couchdb should definitely push its story and marketing on couchapps. Cheers, Giovanni Lenzi ------ www.smileupps.com Couchapps store and Couchdb hosting --047d7bdcab346ed59d0515775416--