2-tier system has its own connections to both db and
--> Network utilization increases linearly when adding
clients and this works only in LANS with a lot of
bandwidth because everything is processed in the client
side. It is not possible to hide application files.
3-tier FAT client takes the application via AOS but uses
database connection of it's own.
--> Application files are hided behind the AOS, and there
is no locking problems when opening shared files. Some
code is processed in the AOS and some in the client. This
works only in LAN with a lot of bandwidth. We use this
configuration when conneting batch server to other servers
in the internal 1GB network .
3-tier Thin client uses everything via AOS and uses AOSes
capability to cache a lot of data and objects.
--> Both application and DB is hided behind one port and
there is minimumum amount of tarffic in the network. This
works fine in the LAN and remote connections if you have
latency under 50 ms. We install AOSes with two NICs, the
1Gbps one connected with DB and the 100 Mbps to the clients
client). I have
client) installed on
difference between 2-tier