Discussion Locked

2-tier VS n-tier databases

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Here's a slightly more challenging question for you:

Can you explain to me the impact on the Total Cost of Ownership between 2-Tier and n-Tier (more than 2) databases in a distributed database architecture?

Please reference thin-client models versus thick-client models and where business rules would reside in these architectures.

If you can help me with this one, I would greatly appreciate it.....

arongirl@home.com

7 replies

by donq

I'm not sure from the "terms" you use what ODBC database product you are familiar with but here goes.

Each ODBC database product comes with its own "engine" (and a few cone with 2 engines).
When more than one ODBC product exists in a multi-database environment each MUST load its own engine(sometimes as much as 15 Meg).
VERY INEFFICIENT!

2-Tier = LAN
n-Tier = WAN and/or multi-Domain

The largest of businesses or organizations can use a single database product AND data warehouse to provide almost unlimited software development IF THE DATA (warehouse, or back-end)IS MODELED PROPERLY!

by donq

Some developers and/or development articles reference their connection path between GUI's to the Data as n-Tier.

Direct Table to Form connection = 1 Tier
Table to Query to Form = 2 Tier
Table to Query to Query to GUI = 3 Tier

Again I can't tell from your wording which "definition" you are after.

by donq

Business Rules reside in PC database "query constraints" or Mainframe "database "procedures and/or triggers"

by fofa

Typically the DATABASE makes up the last tier in an environment. In a 2 tier you have a program level and a database level (typically). The client level could be an application that runs on a server (thin client/fat network) or on the actual client (thin network/fat client). In our company the cost of distribution of the client software (fat client) started to get prohibative so we converted to thin client. Now as to the tier, we have found more than 3 tiers gets more costly because of the maintanence factors involved. We have found to keep costs down we have expanded our network bandwidth (many advantages not counting besides thin client) and run our applications on Citrix servers. The applications maybe 2 or 3 tier, not counting the citrix client layer. The buisness rules reside on the application layer/s either client (citrix side) or in between the client and the database. Or for those applications that do not really require reports, we use the web servers using ASP and a databse.

This discussion is closed to new replies.