what is the advantage of using the three tier architecture in dot net?

Question

The task can be implemented with the normal use of a dot net as well as using the three tier architecture.But in todays world mostly are preferring the three tier thing.why?can you please explain me clearly?

Answer 1

Well, first, you get a seperation of the User Interface from the "meat and potatoes" code. Then you have seperation of the meat from the database access layer.

The code is easier to maintain since it's not all jumbled into one, and say for instance you are trying to connect to two different database systems, all you would have to do is replace the database layer, and the application would "automagically" be updated, without having to recompile the app.

Answer 2

Two-Tier Architecture:- A two-tier architecture is where a client talks directly to a server, with no intervening server. It is typically used in small environments (less than 50 users). A common error in client/server development is to prototype an application in a small, two-tier environment, and then scale up by simply adding more users to the server. This approach will usually result in an ineffective system, as the server becomes overwhelmed. To properly scale to hundreds or thousands of users, it is usually necessary to move to a three-tier architecture. Three-Tier Architecture:- A three-tier architecture introduces a server (or an "agent") between the client and the server. The role of the agent is manyfold. It can provide translation services (as in adapting a legacy application on a mainframe to a client/server environment), metering services (as in acting as a transaction monitor to limit the number of simultaneous requests to a given server), or intellegent agent services (as in mapping a request to a number of different servers, collating the results, and returning a single response to the client.