Web Application Architecture

Sharing information on the Internet is a simple process of a client using a Web browser to request a file from a Web server. The Web server sends a response that contains the file and the Web browser uses the HTML tags to properly format and display the data in that file. Improvements to that model usually include some way of generating HTML dynamically, either on the side of the Web client (using client-side scripting, DHTML, XML, or accessing client applications) or on the side of the Web server (using ASP, COM+, ISAPI, or other server interfaces).

A Web browser displaying HTML has the capacity to mimic any user interface. Cross-platform support for scripting languages and Java applets, as well as support for embedded COM components, makes it possible to use Web technologies for not only Web applications, but for distributed computing. Web applications have been adapted for use by businesses to:

• Allows developers to write component-based applications that run on the Web.
• Enable distribution of applications throughout an enterprise.
• Create and customize new applications quickly.
• Update databases remotely by using an ordinary Web browser on any machine.
• Add transaction processing to Web applications.
• Provide business-to-business information sharing.
• Manage resources and enable remote system administration.

This section outlines general concepts that will assist you in building Web applications, such as the following:

• Building on the Client/Server Architecture: Briefly outlines the traditional client/server design model.
• Microsoft Windows Distributed interNet Application Architecture: Outlines Microsoft Windows DNA, the Microsoft architecture for building Web applications.
• Internet Information Services Architecture: Reviews the IIS components and programming model.
• The New System Architecture: Introduces n-tier and distributed systems design, as an enhancement to the client/server model.