This approach of application development makes a separation of data.
The advantage with this architecture is that because of two separation data can be stored on a single host and can be shared by many applications.
However the limitation with this architecture is that because the user interface and application layer are stored on the PC. So, it is confined to limited resources of that PC.
This architecture overcomes the limitation of two tire system, where a middle layer is build.
The first layer contains the user interface, the third layer contains the data in the form of database or document base,i.e, XML. The middle layer contain the application/business logic.
1> A clear separation of application layer from user interface.
2> Support data retrieval from a web compatible data source in XML.
N-tire architecture is an architecture where logic and processing is distributed among logical and physical tires.
These tires can be conceptually separate or physically located on different servers and even in different geographical locations.
The n-tire architecture contains each modules resides in different node, which are as follows,
1.Presentation GUI(HTML,Window forms, etc.)
2.Presentation Logical Tire
Proxy tire(SOAP, COM, DCOM, etc.)
3.Business Tire(Business objects and rules)
4.Data Access Tire(Interface that handles all the data)
5.Data Tire(Storage and query)
You must Sign In To post reply
|Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here|