Re: Multi tenancy : schema vs databases - Mailing list pgsql-general

From Venkata B Nagothi
Subject Re: Multi tenancy : schema vs databases
Date
Msg-id CAEyp7J95j-_dNz2MYtByGOfYT7kACZFO7-EJe-XrSgTO+1rxEA@mail.gmail.com
Whole thread Raw
In response to Re: Multi tenancy : schema vs databases  (Rakesh Kumar <rakeshkumar464@outlook.com>)
Responses Re: Multi tenancy : schema vs databases
List pgsql-general
 

On Fri, Sep 30, 2016 at 10:16 AM, Rakesh Kumar <rakeshkumar464@outlook.com> wrote:


________________________________________
From: Venkata B Nagothi <nag1010@gmail.com>
Sent: Thursday, September 29, 2016 17:25
To: Rakesh Kumar
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Multi tenancy : schema vs databases

On Fri, Sep 30, 2016 at 5:18 AM, Rakesh Kumar <rakeshkumar464@outlook.com<mailto:rakeshkumar464@outlook.com>> wrote:

Hi

I would like to know which technique is better for supporting multi-tenancy=
 applications, going upto hundreds or even thousands of tenants.

1 - One database with difference schemas (one schema per tenant)
or
2 - One database per tenant.

Did you mean one database with-in a postgresql cluster ?

Yes.  Say something like this within a PG cluster

db4978
db6234
...
100s of such databases.

That would make things worst if you are going for one database per tenant. As said by John just now, it would end up in an very complex and bad design contributing to very poor performance and high maintenance overhead.
A schema per tenant would be a good idea and its hard to say without knowing the data isolation levels you require for each tenant.

Regards,
Venkata B N

Database consultant / Architect


pgsql-general by date:

Previous
From: David Rowley
Date:
Subject: Re: Parallel query only when EXPLAIN ANALYZEd
Next
From: Rakesh Kumar
Date:
Subject: Re: Multi tenancy : schema vs databases