Default N-Tier Nature of Web Applications
When working with web applications, a very important concept to grasp is that by its very own nature each web application is distributed and is inherently 2-tier by default (or 3-tier if we include the database as a separate tier). Therefore, it is not possible to have a single-tier (or 1-tier) architecture at all, when dealing with web applications. And as we saw in the last chapter, if we include a database and client browser in our system, then we already have a basic 3-tier application structure.
Let's understand this concept in detail with a sample configuration for a simple ASP.NET web application:
Web Server: A machine running a web server such as IIS, handling all HTTP requests and passing them onto the ASP.NET runtime process. The deployed project files (ASPX,
ASCX, DLLsetc) are published on this server.Database Server: This will be the physical database such as SQL Server, Oracle and so on. It can be on the same machine as the web server...
