Differences between IIs Web site applications and virtual directories and advanced application notes (file distributed storage scenarios)

For IIS Web site, we use more, it is not verbose.

  today and talk about the difference between the "IIS Application" and the virtual directory and the advanced application scenario, the file distributed storage scheme.

1:iis website:

A website, basically is a site, binding n domain names, binding n IP, and then set up an application pool, basically ran up, a website can create countless applications and virtual directories.
One line has been brought, everyone knows, not much to say.

2: Application (Independent development of program under same domain name, best application Strategy for standalone deployment):

We found that under the IIS Web site, you can create a new "application" such as:

The click is the following interface:

  The next example is the application scenario:

Example One: Compare the usual one site to the foreground and background (System Management site backstage)

1: Distribution of domain names:And for the background, typically, after we deploy the domain name:
Basically not used: Admin888.cyqdata.com most are adopted: www.cyqdata.com/admin888

The latter reason, mostly because of the same domain name, the cookie is good, or the tradition is almost such a reason.

2:iis the corresponding deployment:

A: The traditional way of deployment:

To take the second approach, if you don't know the application scenario, you might want to deploy the site to the root of the www.cyqdata.com primary domain name, the folder named: admin888, along the path.
This deployment, is equal to the development is independent, the final run is a site in the run, of course, modify the daemon, will also affect the foreground application.

B: Deploy using Application Mode:

If you see the second picture, you can see three points: 1: Alias: (equivalent to the directory name, then the access path becomes: http://www.xx.com/alias)
2: Application pool: Can run independently of an application domain, the background of the program modification, will no longer affect the foreground.

3: Physical path: You can place the background in any path without having to place it in the root directory of the master station.

From these three points, it can be seen that the deployment of application mode is the recommended choice.

PS: In fact, the default entire site is a default application.

Example two: Common site channels:

For example: Http://www.cyqdata.com/news represents a news channel Http://www.cyqdata.com/sport represents a sports channel

There may be multiple channels on-line, and they are developed independently of each other, and the power of application deployment is out of the way when it is finally deployed.

3: Virtual directory (one of the distributed file storage scenarios)

Brief description:

A virtual directory is a directory that can be mapped to any shared directory on the network.
Virtual directories, in IIS6, appear to be similar to applications, as if they were virtual paths.

In fact, the effectiveness of virtual directory in the late Distributed file storage:

Example one: Separate a large amount of static HTML into a system drive letter:

If you need to generate a lot of Html in the program, and in our program, the usual path is the root directory: "/html/..."
By setting the HTML to a virtual directory, you can move the storage file to another disk.

Even if you want to delete it, the direct formatting is OK.

Suppose that if your file is directly present in the HTML folder under the root of the website, you will have a big head if you want to delete it.

Network node distribution, improve HDD IO performance:

In addition to this mapping, you can also map to different hard disks of the network, to know the bottleneck of Io, is the limit of a single hard drive, by mapping to different hard drives, the performance of the lifting point is: The limit of a single hard drive *n block hard disk.
And all this expansion, just simple virtual directory mapping, and then move the corresponding files, and the program, do not need to move the knife, simple to complete the distributed storage of files.

This way, can be scaled horizontally, can be continuously added to the independent hard disk, convenient to improve performance.

OK, this article: the difference between IIs Web application and virtual directory and advanced application notes, the basic introduction is here, thank you for watching ...

Differences between IIs Web site applications and virtual directories and advanced application notes (file distributed storage scenarios)