Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
From: Ying Bian <ybian@me.com>
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable
Subject: Create many couchdb instances on demand?
Message-id: <4FA798CE-7B51-45FF-9D29-357434D6D2F1@me.com>
Date: Fri, 09 Oct 2015 22:36:05 +0800
To: user@couchdb.apache.org
MIME-version: 1.0 (Mac OS X Mail 8.2 \(2104\))

Hi all,

I=E2=80=99m building a platform where users (platform users) can create =
their own customize =E2=80=9Capp=E2=80=9Ds.=20

In my original architecture I was thinking to assign each =E2=80=9Capp=E2=80=
=9D a dedicated database in a=20
shared couchdb instance. With that app database, the app owner can store =
whatever=20
he needs to store, including the app=E2=80=99s own users (app users). =
Note that "app users" are=20
different from "platform users=E2=80=9D: platform users are just app =
owners who create apps, while
app users are the consumers of a specific app, which should be isolated =
from app to app.

As in couchdb there is only one _users table per couchdb instance, I am =
wondering whether it
is a better architecture if I assign each app one couchdb instance =
instead of a database? Then
I can leverage the authentication & authorization logic provided by =
couchdb. Otherwise I would
have to have another authentication & authorization system and need to =
keep it consistent with
that in couchdb.

What do you think of this? Is it a normal setup to have many couchdb =
instances? I assume I=20
would need to consult with some technology like docker to do this. How =
complex is it and=20
what kind of additional issues do I need to address?

Your opinion is very much appreciated.

-Ying=