Menu
I have searched Google to find the main difference between 3-tier and n-tier architecture in .net but I have failed to find it out. Several sites said both are the same in nature and some of the sites said there are differences between them.
I want to know the major differences, and which one is better in performance optimization?
810
A two-tier DB architecture either buries the application logic within the server database, on the client (inside the UI), or both of them. A three-tier DB architecture buries the process or application logic in the middle-tier. Thus, it acts as a separate entity from the Client/ User Interface and the data Interface.
In simple term 3 layer architecture can implement in single machine then we can say that its is 1 tier architecture. If we implement each layer on separate machine then its called 3 tier architecture.
The chief benefit of three-tier architecture is that because each tier runs on its own infrastructure, each tier can be developed simultaneously by a separate development team, and can be updated or scaled as needed without impacting the other tiers.
A 3-tier application architecture is a modular client-server architecture that consists of a presentation tier, an application tier and a data tier.
Presentation layer (client browser)
Application or Business logic layer
Data Layer
The main difference is that n-tier arch got 2 extra layers. Example on data layers one part of developers are SQL developers whose work on DB server (making DB structure, writing Stored procedures and so forth), and .Net developers whose work on consuming that stored procedures and making abstraction ( implementing repository pattern)...
Hope this help you.
160
I know this question is old, but the really simple and ultimately correct answer is:
3-tier is N-tier where N=3.
32
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
