对于DAL和配置多租户最佳实践隔离DB [英] best practice for DAL and configuration on Multi-Tenant isolated DB
问题描述
我公司拥有十几个网站和孤立的DB（相同的架构）。
每一个客户都有自己的网站（不同的应用程序池）和DB。
My company holds a dozen websites and isolated DBs (identical schemas). every customer has its own website (different app pool) and DB.
每一个网站都有自己的配置，几个连接字符串，但它们都具有相同的配置模式。
every website has its own configuration, several connection strings, but they all have same schema for configuration.
cust1.domain.com
cust1.domain.com
cust2.domain.com
cust2.domain.com
cust3.domain.com
cust3.domain.com
我们希望所有的网站合并为一（单独的应用程序池），并留在隔离区议会对数据安全性的原因，并大量。
We would like to merge all websites to one (single app pool) and stay with isolated DBs for security and large amount of data reasons.
什么是设计它的DAL和配置的最佳实践？
什么是它的含义，如果大量的租户将在同一时间？没有一个应用程序池可以管理这种情况下，也可以以某种方式进行管理？
what is the best practice for designing a DAL and configuration of it? what are the implications of it, if large amount of tenant will be on the same time? does one application pool can manage this situation or it can be managed somehow?
顺便说一句，我们使用ASP-会员用户身份验证。
BTW, we are using asp-membership for users authentication.
在此先感谢，
埃迪
Thanks in advance, Eddie
推荐答案
您可以从多租户数据架构尝试'共用一个数据库，不同的模式。在你的DAL您可以选择perticular当前用户特定的模式。简单而安全的这样
You can try 'Shared DataBase With Different Schema' from multi tenant data architecture . In your DAL you can choose specific schema which perticular to current user. Simple and secure in this way
继续阅读 http://msdn.microsoft.com/en-us/库/ aa479086.aspx
这篇关于对于DAL和配置多租户最佳实践隔离DB的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
