What is 3 Tier Architechture?

Prashant More

18y6.5k.NET

Hello All,

I want to know what is 3 tier architechture.Please anybody explain me in brief with example.

My email ids are

[email protected]

Thanks & Regards

Prashant S. More

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Raj Kumar18y ago
Tier 1: the client contains the presentation logic, including simple control and user input validation. This application is also known as a thin client.

Tier 2: the middle tier is also known as the application server, which provides the business processes logic and the data access.

Tier 3: the data server provides the business data.
These are some of the advantages of a three-tier architecture:
It is easier to modify or replace any tier without affecting the other tiers.

Separating the application and database functionality means better load balancing.

Adequate security policies can be enforced within the server tiers without hindering the clients.
0
Niradhip Chakraborty18y ago
Check out all the parts(i.e. part1,part2 and part3) in the follwing article

http://aspguy.wordpress.com/2008/07/12/implementing-a-3-tier-architecture-with-c-part-1/
0
Prashant More18y ago
Hello All,

Please anybody explain me implementation of the 3 tier architechture.

Thanks & Regards

Prashant S. More
0
Sivangari Vytheswaran18y ago
Three-tier (layer) is a client-server architecture in which the user interface, business process (business rules) and data storage and data access are developed and maintained as independent modules or most often on separate platforms. Basically, there are 3 layers, tier 1 (presentation tier, GUI tier), tier 2 (business objects, business logic tier) and tier 3 (data access tier). These tiers can be developed and tested separately.

What is the need for dividing the code in 3-tiers? Separation of the user interface from business logic and database access has many advantages. Some of the advantages are as follows:
- Reusability of the business logic component results in quick development. Let's say we have a module that handles adding, updating, deleting and finding customers in the system. As this component is developed and tested, we can use it in any other project that might involve maintaining customers.
- Transformation of the system is easy. Since the business logic is separate from the data access layer, changing the data access layer won’t affect the business logic module much. Let's say if we are moving from SQL Server data storage to Oracle there shouldn’t be any changes required in the business layer component and in the GUI component.
- Change management of the system is easy. Let's say if there is a minor change in the business logic, we don’t have to install the entire system in individual user’s PCs. E.g. if GST (TAX) is changed from 10% to 15% we only need to update the business logic component without affecting the users and without any downtime.
- Having separate functionality servers allows for parallel development of individual tiers by application specialists.
- Provides more flexible resource allocation. Can reduce the network traffic by having the functionality servers strip data to the precise structure needed before sending it to the clients.
0