November 29th, 2012, 11:43 PM
Multitenant: Best Practices?
We are going to use PG as our database for an online, multitenant SaaS application. We want to place each subscriber in his/her own database. I am wondering whether there are any best practices for using PG in a multiuser, SaaS situation, where performance is crucial. For example, I have found references that each tenant should have their own tablespace (directory), but I have found other references where the tablespace should be assigned on a per application basis.
We will most likely use the EnterpriseDB Amazon Web Services: "Postgres Plus Cloud Database". Has anyone used it for a scalable, SaaS application? The only unfortunate thing that I can find is that all of the users are assigned to the database instance rather than to each database...
Anyway, I hope that we can get a good conversation going because I am sure that others will be asking for this information, too.
Thank you for your time and suggestions,
December 10th, 2012, 07:51 AM
is your development completed?