Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of martinh@gmail.com designates
 209.85.213.52 as permitted sender)
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;
        b=RR7Z0Tl1KKn4n5NFkncVerDKs5y/w+TrycAAUbxmyQ0cdgFx8pHwXl88GpUQb3a0WC
         6aVhUWC/KOCKwmfL4qWzX0Nd2BpuowV0I8wvHXi/85hk0WLGC21dn7NfHwmER3mQiB0w
         xW76iafkACMYOWvzJ/WqyWJSkARjDTNFJt55U=
MIME-Version: 1.0
Sender: martinh@gmail.com
In-Reply-To: <AANLkTi=qiVNh37aT8ju0XOhkMpPBQSR=to9UCZBNpotT@mail.gmail.com>
References: <AANLkTinr62TrG4HGia7OX_cs88YZO+tYYhGgakjtYB+w@mail.gmail.com>
	<AANLkTi=5Hu_0B+ekbnc5sxo9t7oXdmwCrD7DQR-e5j-Z@mail.gmail.com>
	<AANLkTin3X4Gwent7Yfx++s=g181fMm6P-mKV1FJQK-b3@mail.gmail.com>
	<4CCE684E.6040600@makkiato.de>
	<12CF5A9C-0FE3-4BED-A51B-05DB34294CC7@apache.org>
	<AANLkTi=qiVNh37aT8ju0XOhkMpPBQSR=to9UCZBNpotT@mail.gmail.com>
Date: Mon, 1 Nov 2010 14:30:45 +0000
Message-ID: <AANLkTinfLAUDVoaShE1Rttaqek9UGco6s_B52T_uK63F@mail.gmail.com>
Subject: Re: Sharing design documents between DBs
From: Martin Higham <martin@ocastalabs.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=90e6ba6e8f30621be90493fea785

--90e6ba6e8f30621be90493fea785
Content-Type: text/plain; charset=ISO-8859-1

Until you have one DB per user and then you're looking at replicating the
design doc to many thousands of databases and continuous replication doesn't
make sense

Martin

On 1 November 2010 14:11, Benjamin Young <benjamin@couchone.com> wrote:

> Hey Gregor,
>
> If you setup continuous replication between your various customer db's and
> your primary application database (which would likely only contain the main
> app's design doc), then publication of the app would automatically be
> "rolled out" to the various customer db's. Because these DB's would be
> "standalone" versions of the app, they could even be on multiple hosts
> running CouchDB, so you'd remove the single point of failure problem that
> most web-apps have--as they run (often) through a single server for all
> customers.
>
> Personally, that mode of "multi-tenant" app (via replication) is pretty
> exciting, and opens up new ways of dealing with load and application
> distribution. Get's the mind reeling, or maybe that's the coffee I just
> finished... :)
>
> Later, Gregor,
> Benjamin
>
> On Mon, Nov 1, 2010 at 6:49 AM, Jan Lehnardt <jan@apache.org> wrote:
>
> > Hi Gregor,
> >
> > On 1 Nov 2010, at 08:12, Gregor Frey wrote:
> >
> > > Hi,
> > > when I followed the discussion about the setup of CouchDB in a hosted
> > environment, I wondered whether it would be possible to share the
> > application level software between multiple databases. This would enable
> a
> > real multi-tenant set-up. Otherwise you must duplicate the application
> with
> > each new tenant.
> > > Does anybody know whether and how CouchDB supports application sharing?
> >
> > CouchDB does not support application or document sharing over databases.
> > But nothing stops you from gradually replicating a new design doc (the
> > application) to every database.
> >
> > Cheers
> > Jan
> > --
> >
> >
>

--90e6ba6e8f30621be90493fea785--