Asp. NET upgrade capability discussion (i)

Scalability is always entangled with my last topic performance, but in fact, they are two completely different issues. In the performance section, I've talked about caching, which is one of the biggest improvements in scalability, so I was thinking that I had to find something else to discuss in this section.

First, the system is built to improve performance in multiprocessor and cascade environments with certain characteristics. For example, session state can be maintained by a separate processor, on a separate machine, and even allow cross server sessions in the database. By doing this, you can add more Web servers relatively easily, even if you don't think about the rapid increase in traffic during the development process.

There are also some things called "Web gardens" that I don't quite understand. However, they can help multiprocessor machines to help them do more work than a single processor. I think it's a very novel idea, but there are those who think they won't use this feature.

So you already have the tools to build a perfect Web farm, but how do you keep them running? Of course, ASP. NET Runtime monitors and manages processes. When there is a vulnerability or deadlock, the runtime will automatically close, but just wait and it will recover. Before the old version is closed, a new version will be launched in the old version to overwrite the old version. Runtime then directs the new instructions to the new work process and rejects the old instructions and closes them. Because of the substitution, the end user will not find any changes.

After introducing the high performance of so many asp.net, here are a few examples.