Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 2648 invoked from network); 15 Sep 2009 09:39:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Sep 2009 09:39:53 -0000 Received: (qmail 21660 invoked by uid 500); 15 Sep 2009 09:39:52 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 21617 invoked by uid 500); 15 Sep 2009 09:39:52 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 21606 invoked by uid 99); 15 Sep 2009 09:39:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 09:39:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aklimets@day.com designates 207.126.148.182 as permitted sender) Received: from [207.126.148.182] (HELO eu3sys201aog002.obsmtp.com) (207.126.148.182) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 15 Sep 2009 09:39:41 +0000 Received: from source ([209.85.218.213]) by eu3sys201aob002.postini.com ([207.126.154.11]) with SMTP ID DSNKSq9gyDldu4KKSvqh1jrth4HC+SsW7LU+@postini.com; Tue, 15 Sep 2009 09:39:21 UTC Received: by bwz9 with SMTP id 9so2843789bwz.41 for ; Tue, 15 Sep 2009 02:39:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.53.149 with SMTP id m21mr2448721fag.101.1253007560045; Tue, 15 Sep 2009 02:39:20 -0700 (PDT) In-Reply-To: <1253006078.8027.12.camel@frax> References: <1253006078.8027.12.camel@frax> Date: Tue, 15 Sep 2009 11:39:20 +0200 Message-ID: Subject: Re: Multi-tenant Content Repository From: Alexander Klimetschek To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, have a look at those two previous discussions: http://markmail.org/message/eso35utn3k3572nv http://markmail.org/message/s66ho2dfskteep53 Regards, Alex On Tue, Sep 15, 2009 at 11:14, Ben Francis wrote: > Hi List, > > How would members of the list recommend going about implementing a > multi-tenant content repository? We would like to host multiple tenants > on one relational database server for a service where customers can sign > up to store their content via a web front end. > > I can see several options: > > REPOSITORY-PER-CUSTOMER > > This would involve (I think) automatically creating a database (or at > least a set of tables) for each tenant that signs up. Each tenant would > have their own version storage and search index. > > WORKSPACE-PER-CUSTOMER > > This would involve automatically creating a new workspace for each > customer that signs up. All customers would share a common version > storage and search index and the permissions system would be relied upon > to isolate tenants' data from each other. > > SUB-TREE-PER-CUSTOMER > > A "tenant" node would act as the root for a sub-tree in the repository > under which the tenant's content would be stored. Again, each tenant > would share a common version store and search index and the permissions > system would be relied upon to isolate tenants from each other. > > I think the last option would be the easiest to implement, but the first > option would be the most secure, what do you think? > > Any suggestions welcome. > > Regards > > Ben > > -- > Ben Francis > http://tola.me.uk > > -- Alexander Klimetschek alexander.klimetschek@day.com