Page 1 of 1

SaaS Multi Tenant MySQL Database Architecture

Posted: Mon Feb 07, 2011 8:24 pm
by buckit
Web application that contains highly sensitive data. as a whole the data becomes more and more sensitive with the increase of tenants.

hardware is not an issue, I personal colo space with high end servers for me to do what I want with.

Separate databases for each tenant or separate tables in a single database?

I dont think a shared schema will work, even if I use views to ensure "tenant_id" relationship as not to show cross data.


I have read about 20 different articles and thought through every possibility. I just cant decide which direction to go. either way will be a versioning nightmare.

Re: SaaS Multi Tenant MySQL Database Architecture

Posted: Mon Feb 07, 2011 10:18 pm
by califdon
What kind of threats are you trying to protect against?

Re: SaaS Multi Tenant MySQL Database Architecture

Posted: Tue Feb 08, 2011 6:29 pm
by buckit
Crossed data is the primary.

We keep our servers EXTREMELY secure but also to stop a single database of all critical data... in addition to the DB architecture the critical parts of the data will be encrypted.