Quantcast
Channel: dBforums – Everything on Databases, Design, Developers and Administrators
Viewing all articles
Browse latest Browse all 13329

Multi-tenant DB Design, a Salesforce scenario

$
0
0
I was doing some research into the optimal DB setup for a Salesforce like application (webapp with sensitive data for multiple 10.000's of customers, each customer can have multiple USER accounts).

My idea is, is that the split database setup (different DB for each customer) is the best since its the only way to make sure data is really isolated in terms of security, and because its not just multi customer, but each customer can have multiple users that login to work on the data. However...is having a DB instance with 10.000 'small' DB's really gonna work?

I dont really feel much for the shared schema setup since you will end up with 10's of thousands of tables, which doesn't seem very manageable.

The 1 big DB setup with just using a customerID column per table seems the easiest to implement, but not really secure...and joining tables will be quite a task as I presume.

What are your thoughts on this scenario? The seperate DB's-scenario seems best to me from a scalability and security perspective...but what do I know :D

Thanks!

Viewing all articles
Browse latest Browse all 13329

Trending Articles