Describe client/server architecture, including fat and thin clients, client/server tiers, and middleware.

Question

What will be an ideal response?

Answer 1

• Client/server architecture refers to systems that divide processing between one or more networked clients and a central server. In a typical client/server system, the client handles the entire user interface, including data entry, data query, and screen presentation logic. The server stores the data and provides data access and database management functions. Application logic is divided in some manner between the server and the clients.
• A fat client design locates all or most of the application processing logic at the client. A thin client design locates all or most of the processing logic at the server. Typically, thin server designs provide better performance, because program code resides on the server, near the data. In contrast, a fat client handles more of the processing and must access and update the data more often. Fat client design is simpler and less expensive to develop, because the architecture resembles traditional file server designs where all processing is performed at the client.
• Client/server designs can be two-tier or three-tier. In a two-tier design, the user interface resides on the client, all data resides on the server, and the application logic can run either on the server, on the client, or be divided between the client and the server. In a three-tier design, a middle layer between the client and server processes the client requests and translates them into data access commands that can be understood and carried out by the server.
• Middleware is software that connects dissimilar applications and enables them to communicate and exchange data.