Re: high scalability possible with heavy use of Session state ?

Tech-Archive recommends: Fix windows errors by optimizing your registry



A lot of this depends on how much you need to store in session
and whether you are storing only value types.

If you are concerned about session state for an app that large,
I can only assume you are running in a web farm. Another
issue that has become more and more prominent is
users having their outgoing traffic run through network
proxy server farms. If so, even if you use session affinity,
you'll still have all sorts of users with problems regarding
losing session.

A nice new product from ScaleOut Software addressing
this issue. I'd check it out prior to making your final
decision on how you manage state in your farm.

We use it at the company I work for and it is a great
product.

Read more about the problem, the product solution,
and some code samples on how to use it as a global
application cache across applications and across
servers in the farm. Very cool.

http://www.eggheadcafe.com/articles/scaleout_server.asp

--
2004 and 2005 Microsoft MVP C#
Robbe Morris
http://www.masterado.net

Earn $$$ money answering .NET Framework
messageboard posts at EggHeadCafe.com.
http://www.eggheadcafe.com/forums/merit.asp



"John A Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:ecynQYMkFHA.2904@xxxxxxxxxxxxxxxxxxxxxxx
> Has anyone been part of team that built a highly-scalable ASP.NET web-app
> that relied heavily on use of Session state ?
>
> By highly-scalable, I do not mean Amazon.com sized ... but, nonetheless,
> quite large. Just for example, a worldwide site to produce an insurance
> quote.
>
> I have heard from experts in building large-scale ASP.NET apps that if you
> wish to avoid scalability worries, stay completely away from Session state
> and instead concentrate on your energies speed of database access, and
> page and page-fragment caching.
>
> I've heard that when travelling down the scalability road, a heavy
> reliance on Session state will lead to ruin
>
> However, a state-machine tracking the user's "footprints" would be quite
> nice to have for the app I am building.
>
> Does anyone have any insight ?
>
>
>


.



Relevant Pages

  • Re: ASP.NET Application - Defined???
    ... > gateway to the app). ... > business object into session state. ... > - Then Main.aspx did the bus obj user validation and filled out the rest ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP.NET Application - Defined???
    ... A user is linked to the Default.aspx from our intranet app ... business object into session state. ... This is all working nicely today, but I want to move the user validation ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Trouble with huge amount of State Server Sessions Timed out
    ... "Unable to serialize the session state. ... > State Service or SQL Server can be memory intensive depending on the types ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: IHttpAsyncHandler problem
    ... My guess is that it's not the page you're waiting for, but the lock on the session state. ... It seems the Asp.Net ThreadPool thread used by the first tab is ... AsyncRequestState reqState = result; ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Session Variables - why arent novice developers warned?
    ... very dangerous outcome which may result when the session variables are used ... Developers want the session to be preserved when a new browser ... You can research session state very thoroughly without finding any ...
    (microsoft.public.dotnet.framework.aspnet)