title: ASP.NET - Alternatives to Session Variables in C#
body: <p>So I've always used session variables when needed (e.g. saving user form data from one registry step to another).</p>
  
  <p>I've been told that a web application should always be stateless and that the problem with the session variables is the more users that access the web application the more memory of the web server is going to be used, which will eventually break the application in terms of scalability.</p>
  
  <p>What I wanted to know is what alternatives are being used today to couple a User to it's data. In my case i have an application that has a registry form with 4 separate steps and i want to allow the users to continue the registry process where they left. </p>
  
  <p>Thanks in advance to all who answer.</p>