2-tier - also called client/server applications which consist of two separate applications, one server application (typically a database server like Oracle, MSSQL or any other standalone database) and a client application. suppose you want to have many different clients for front- end would be unwise to copy all the business logic (all the rules of your application) to each client app.,. so its better to create a middle layer containing the business logic, and then let the clients talk with this middle layer. Thus the clients can relatively easily be changed for other types of clients, without need for remembering how was the business logic put together. 3-tier architeture where one tier is the backend database engine, one is the front end client and one is just in between them, also named the application server or business logic node. its uses mainly Load balancing and Fault tolerance.
Asked In: Many Interviews |