The membership *does not* read or write to the SQL database on each request. You only call to the Membership system when a user logs-in. Everything else is then handled via the FormsAuthentication system - which does not access a database on any request (instead it uses a cookie to authenticate the user). As such, you could have a thousand active users on the site, and never hit the database on any request other than when they login. This scales incredibly well, and works on both single-system and web-farm configurations.
The membership API also doesn't serialize any objects to the database. I think you might be thinking of the Profile system instead. Thanks, Scott -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Paul Cowan Sent: Friday, February 09, 2007 7:29 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] AOP and security Hi, The membership reads and writes to SqlServer by default, it also puts impositions as such things as all objects should be serializable. THere obviously is an overhead involved in reading and writing to SqlServer on every page request. >> (and in use on systems with 2M+ active users). I am sure they have top of the range hardware which is not always the case for my end of the market. We are running a reasonably busy website and the client has not even given us a dedicated web server. We are also running ASP.NET 2.0 on windows 2000 and IIS 5.0. We are trying to talk them into upgrading but we they are being very stubborn. [EMAIL PROTECTED] > Date: Fri, 9 Feb 2007 07:05:27 -0800> From: [EMAIL PROTECTED]> Subject: Re: > [ADVANCED-DOTNET] AOP and security> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM> > > The default providers in ASP.NET 2.0 are extremely fast and scalable (and > in use on systems with 2M+ active users).> > If you want to override the > providers and role your own (using whatever storage schema you want), then > you can also build and plug-in your own providers. This blog post points to a > few simple providers that are useful to get started: > http://weblogs.asp.net/scottgu/archive/2006/10/13/Tip_2F00_Trick_3A00_-Source_2F00_Documentation-for-Simple-ASP.NET-2.0-SQL-Providers-Published.aspx> > > Thanks,> > Scott> > -----Original Message-----> From: Discussion of > advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Paul Cowan> > Sent: Friday, February 09, 2007 1:43 AM> To: > ADVANCED-DOTNET@DISCUSS.DEVELOP.COM> Subject: Re: [ADVANCED-DOTNET] AOP and > security> > I am not for one minute suggesting you can serve web.config > files. you are aware connection strings have been hacked from the > web.config?> > I just do not like the overhead of the members/roles stuff > that comes with .NET 2.0. I had a look at membership and found it very slow.> > > > > [EMAIL PROTECTED]> > > > > Date: Thu, 8 Feb 2007 11:17:58 -0500> From: > [EMAIL PROTECTED]> Subject: Re: [ =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
