views:

79

answers:

2

Any recommendations for transition from single server to load balancing environment of 3 servers?

I considered using Sql Server session management, but I am storing linq2sql objects in session which has serialization issues. With a quick search I found a workaround .But I am skeptical to use this approach considering code-change/readability/performance issues. Any suggestions are welcome.

+2  A: 

Just a suggestion : Can't you use sticky sessions in your load balancer?

LightX
I am using inproc until now. I don't know how to use sticky sessions in asp.net. Is there a way to access and modify the sessions in load balancer?
Syam
@Syam, This has to be configured at the loadbalancer. We are using this in production with three servers. Most hardware and s/w load balancers are able to do this. see.. http://en.wikipedia.org/wiki/Load_balancing_(computing)#Persistence
LightX
@LightX, I just confirmed with network team about the sticky sessions. This solves my issue. Thank a lot
Syam
+2  A: 

We use memcached but it sounds like you want something to be a more critical portion of your app than just caching if you're placing LINQ to SQL objects up there (and I btw agree with RPM that you should consider getting out of that business...)

Anyway, this is a nice blog post that gives you a few options. Velocity is definitely one to look at since it's what Microsoft is offering (this is an asp.net app) and it seems to be gaining steam these days.

Tahbaza
@Tahbaza, I like this solution but my problem seems to be much simpler than that. @LightX suggested I use sticky sessions for this issue. Thanks a lot any way. As I mentioned, I am using colletion<T> objects to store in the session. The relation between those tables are the once causing serialization pains
Syam