Distributed state management for ASP.NET


 

The more I delve into distributed architectures, the more I’m feeling like Microsoft just isn’t providing much of a path forward to scalable distributed systems. Case in point: state management.
By default, session state in ASP.NET is stored in the web server’s memory. To share state across servers – which you would want to do in a server farm – you need to store it in SQL Server or in the .NET state service. This is fine for small solutions, but once you bump up against the need to partition state across many servers or multiple hosting locations, things start to get complex and expensive.

Solutions:

ASP.NET SessionStateStoreProviderBase

Using JavaSpaces from .NET

3rd Parties: ScaleOut, NCache, GigaSpaces

 

Via using Enterprise.Architecture;: Distributed state management for ASP.NET

Advertisements

One thought on “Distributed state management for ASP.NET

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s