Home/ Questions/Q 8013607
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T19:40:35+00:00

I am building an MVC 3 Application and have a question about one example

  • 0

I am building an MVC 3 Application and have a question about one example scenario.

I have two entities – Order and OrderDetails.
Order data is filled on one page, detail is added, edited, deleted on other three pages.
Once order and details are filled I save this bunch of data to database.

As you can see, during user work and before data is saved to the DB, I need to store the order and details data into some kind of in-memory or similar object.

Now, if I store this object in Session then I am breaking scalability – application cannot be spanned across multiple machines.

Is there a Pattern or Approach which allows scalability and do scenarios like described?

Note: Solution other than Sql-Server Session State

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    have a look at the State Server Session

    StateServer mode, which stores session state in a separate process called the ASP.NET state service. This ensures that session state is preserved if the Web application is restarted and also makes session state available to multiple Web servers in a Web farm.

    http://msdn.microsoft.com/en-us/library/ms178586.aspx

    • 0