What are the key factors for successful scalability of ASP.NET applications?

When you launch a new ASP.NET application that knows that at some point in the future it needs to scale, what are the most important design decisions that will allow scalability in the future without wholsesale refactoring?

+3
source share
4 answers

My first three decisions:

  • Disabling or saving session state in the database.
  • Saving as little as possible in session state.
  • N-. - Web- DLL , -, . , , , , , , , .

.

, , .

+3

ASP.Net Do Do not Do -:

  • - SessionState = Off
  • ViewState - EnableViewState = False
  • - ASP.NET ASP.NET, (DataGrid )
  • ( sqlreaders on )

  • . System.Web.Cache .
  • - ( S3?)
  • , , , .
  • , , , .
  • - , .
  • , , , , , "-".

, .

+3

, / . , , .

+1

There are so many reasons that you can write a book on this subject. Actually, there is a great book and it is free .; -)

Microsoft has released Improving the Performance and Scalability of .NET Applications as a PDF Book.

You should read the cover for the cover if you do not mind writing style. It not only identifies key performance scenarios, but also sets benchmarks by measuring performance and how to apply what you are learning.

+1
source

Source: https://habr.com/ru/post/1699709/


All Articles