Explanation of the componentized architecture of the key attributes of the IIS server

I often hear people inside and outside Microsoft call the new IIS Server 7.0 Web one of Microsoft's most important development efforts over the past few years. Considering Microsoft's recent release of a series of notable technologies, including Windows Vista ?, This comment is of great significance!

The launch date of IIS Server 7.0 is the tenth anniversary of the first IIS server version in Windows NT 4.0. In 2001, after four versions, IIS 5.0 became the most popular Web server on the Internet, although it became the notorious Code Red and nimhei worm attack object in a few months.

IIS Server 6.0 was released in Windows Server 2003. It significantly revised the Server and focuses on improving security, reliability, and performance. Since then, IIS 6.0 has proved to be a rock-solid Web server. Since its release, it has gained high reliability and security records, and has only one key Security Bulletin (not remotely available ).

In this article, I will take this opportunity to introduce to developers and administrators the main reason why the next generation of IIS Server 7.0 Web server is so different, it also gives you a good start when using many of its new features.

Componentized architecture is a key attribute of IIS Server 7.0. It can reduce security risks and minimize the need to install patches. It also supports specialized server deployment. This deployment can combine the IIS server function and custom components to optimize specific server roles in the application topology. For example, reverse proxy and cache server, HTTP Server Load balancer, or SSL and secure sentinel server.

All server functions attached to IIS Server 7.0 are based on the new public extensible API. As a developer, you can use your own functions to replace any existing server functions, or you can build new modules to add them to the IIS server 7.0 feature set. Do you want to replace the built-in authentication mechanism with a custom authentication module or provide a new form of response compression?

The new extensible API is a fundamental improvement to the previous ISAPI extensible model, allowing you to more flexibly and easily enhance servers. Almost every aspect of the server (from the core server to configuration, management, and diagnosis) provides scalability, allowing you to expand and cut servers as needed. This article will provide more information about scalability later. For more information about IIS servers, see here.