title: What is the best practise design for a scalable web application involving session state
body: <p>The reason I ask this is recentlydesigned an application , initially wanted to use no session state to keep things simple, but eventually succumbed to the ease of the session state idea for storing state. I was aware that moving to a web farm solution would involve configuring session state to run in sql. However I had never run across any information explaining serialization would be neccessary.
  So no I need to refactor code to achieve this.</p>
  
  <p>Additionally, I use linq to sql to give me data objects. Ideally this would be easy to serialise, but it seems not straight forward. </p>
  
  <p>I have googled and doing this should be ok. The question isn't how to serialise the linq data class but rather:</p>
  
  <p>Is session state the way forward, in particular when designing scalable applications on a web farm,  should we use other methods, what's recommended when using linq for data access, should we use query string etc.</p>
  
  <p>Thanks  </p>