In typical client-server systems the server machine is much more pow- erful than the clients; that is, its processor is faster, it may have multiple processors, and it has more memory and disk capacity. Consider in- stead a scenario where client and server machines have exactly the same power. Would it make sense to build a client-server system in such a scenario? Why? Which scenario would be better suited to a data-server architecture?

In typical client-server systems the server machine is much more pow- erful than the clients; that is, its processor is faster, it may have multiple processors, and it has more memory and disk capacity. Consider in- stead a scenario where client and server machines have exactly the same power. Would it make sense to build a client-server system in such a scenario? Why? Which scenario would be better suited to a data-server architecture?

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

Defend the link between availability and dependability in the context of a computer network. Because of these issues, it is currently regarded to be obsolete. A deep dive into the subject is required.
How do dependability and availability relate to one another in the setting of a computer network? It's no longer relevant due to the aforementioned drawbacks. Is this long conversation really required?
However, according to the OSI model, the majority of computer systems only employ the minimum number of layers required. Wouldn't it be preferable to cut down on the number of layers? I was curious as to whether or if there are any possible downsides associated with having fewer layers.
How do dependability and availability interact in the context of a computer network? It is currently regarded as outdated due to the aforementioned reasons. Should we spend a lot of time deliberating about it?
Consider the following case study: A renowned restaurant chain wants to automate their business. The branches of restaurant are spread over different parts of the country. Currently each branch was being managed by a desktop based POS system, and the sales records were presented to the CEO at the end of month in a meeting. Now the CEO of the company requires a system which can provide him daily sales reports of all branches through a centralized system. The each branch manager needs help to manage employees work shifts, inventory and stock maintenance, order placement and sales record etc. The system will be installed on each branch and will be operated by the sales team. In order to keep their business running, the owners want to implement the system gradually. The software development company has agreed to provide the solution as per terms. Software development team consists of 6 members and time to completion is 6 to 8 months. Which Process lifecycle model would you suggest and why?