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?
My first three decisions:
.
, , .
ASP.Net Do Do not Do -:
, .
, / . , , .
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.
Source: https://habr.com/ru/post/1699709/More articles:Built-in list that can be accessed by index and key - dictionaryHow to link one table with many different tables? - databaseInclude ib_logfiles in backup? - mysqlASP.NET MVC Beta 1 - Does It Support Strongly Typed Data? - c #Changing java lookandfeel without changing application - javaHow can I reliably determine the window handle for a given Outlook inspector window with WordMail enabled from COM-Addin (Outlook <= 2003)? - winapiiPhone SDK: welcome video - objective-cPlace the MySQL JAR connector in the WEB-INF / lib of my WAR, and not in $ CATALINA_HOME / common / lib? - javaDispose C # DLL tagged for COM interoperability - c #Is there a change event for the list control? - cAll Articles