ASP.NET SqlMembership 提供程序可扩展性
我即将开展一个项目，该项目将涉及 70,000 多名用户（教育）。 我想知道 ASP.NET SqlMembership Provider 是否已用于如此大的容量？ 假设硬件已经有了，是否需要做一些特殊的事情才能使其顺利工作？ 我们正在做所有显而易见的事情，例如将数据库和应用程序分开，但是有什么代码方面我需要注意的吗？
I've got an upcoming project that is going to be dealing with 70,000+ users (education). I was wondering if the ASP.NET SqlMembership Provider has been used at such large capacities? Assuming the hardware is there, is there anything special that needs to be done to make it work smoothly? We're doing all the obvious things like separating boxes for databases and applications, but is there anything code wise that I need to watch out for?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我知道一个网站，该网站的所有者写了一篇关于 ASP.NET 性能的精彩文章( http://www.codeproject.com/KB/aspnet/10ASPNetPerformance.aspx）
在这篇文章中，有一个主题，作者描述了一个有关配置文件提供程序的补丁，以提高性能。 请阅读该部分。
I know one site that, owner of this site wrote a brilliant article about asp.net performance(http://www.codeproject.com/KB/aspnet/10ASPNetPerformance.aspx)
On this article there is one subject that author describes a patch about profile provider for higher performance. Please read that section.
内置的 SqlMembershipProvider 非常可靠且可行。 它们与 FormsAuthentication 和登录控件紧密集成。 因此身份验证是可靠的并且实施起来也很快。
我看到的唯一问题是数据库表结构的复杂性，它们非常整洁，一开始并不那么直接。 因此，您基本上可以编写自己的 MembershipProvider，它将通过更简单的设计和实现与您自己的用户表进行对话。 此外，由于表设计的原因，在 admin 上管理成员也很痛苦，但在某种程度上，这样做是相当可能的。 由于这些原因，我们基于 Sql 编写了自己的 MembershipProvider。 它的效果非常好，我们也有过很好的经验。
Inbuilt SqlMembershipProvider is very reliable and workable. They tightly integrate with FormsAuthentication and Login Controls. So authentication is reliable and it is also quick to implement.
Only problem I see is the complexity of the Database table structure, they are quite tidy and not so straight at first. So you can basically write your own MembershipProvider that will talk to your own users table with more simplistic design and implementation. Also Managing Members on admin is also painful due to table design but in a way it is fairly possible to do so. For these reasons we wrote our own MembershipProvider based on Sql. It's working amazingly and we've had good experience of the same.