Client/Server architecture is mainly a software concept that includes a set of service providers and service requesters. The set of computers acts as service providers and is called as server. The sets of software component, which act as service requester, are called as client.
In the client/server architecture, the database acts like a library clerk retrieving books from the shelf. The user programs have to request database for the data instead of searching for the data themselves. This way there is no risk of the users putting the data out of order. If the desired data is in use, the database makes the user wait until it is free.
The major advantage of the client/server architecture is that the server is available for a number of clients and there is distribution of work between the clients and the server. The user directs the request to the client; the client in turn understands the user’s request and redirects the request to the server. The server retrieves the data, gives it to client.
You can have client and server on the same machine or on different machines. Each client has a corresponding process inside the server.
One of the most used client/server configurations with the R/3 system is the 3 tiered architecture, which separates a system’s computer into 3 functional groups:
No comments:
Post a Comment