Client side architecture vs. Server side Architecture

Introduction

Client-server architecture allows simultaneous access to data for multiple users. Database based on SQL-server, in most cases support the optimistic locking (optimistic locking) - an approach that allows multiple users at one and the same time work with the same data. Conflict resolution is postponed until the moment when users send SQL-server modification. Client-server is a computer or network architecture in which the job or the network load is distributed among the service providers (service), called servers, and customer service are called clients. Often, clients and servers communicate over a computer network and may be different physical devices and software.

Discussion

If within a client-server architecture in response to a request from the server you get a certain amount of data, you should try to formulate a query so that the volume of the resulting data would not be too large. For this purpose, it is recommended to perform filtering on the server side. When it comes to local data, it is recommended to divide a large number of records across multiple files, thanks to this you can download only the ones you need. Thus, evaluating the benefits of client-server architecture, we can move on to the study of specific techniques of programming in a client-server environment. The main goal is to properly distribute the load between the client and the server and reduce the bandwidth needed to transmit information between the client and server.

However, in addition to performance gains there are other compelling arguments in favor of client-server architecture. Client-server architecture allows customers to manage large volumes of data. Database size can reach several hundreds of megabytes or even more - files of this size is not always acceptable to store on the local client computer hard disk. The network version of 1C: Enterprise allows you to organize a large number of jobs in file-server or client-server architecture.

The popularity of multimedia and hypermedia environments, applications, in the style of the Internet, requiring large amounts of stored information, the development of sophisticated client-server architectures cause a significant increase in the cost of creating and managing distributed repositories. However, in addition to performance gains there are other compelling arguments in favor of client-server architecture. Client-server architecture allows customers to manage large volumes of data. Database size can reach several hundreds of megabytes or even more - files of this size is not always acceptable to store on the local client computer hard disk.

The cursor on the server side is controlled by the system RDBMS. In client-server architecture, based on products such as SQL Server, Oracle, or InterBase, this means that the cursor control is carried out on a remote server computer. When it comes to desktop database such as Access or Paradox, a server cursor is controlled by the software package, servicing the database. That is a logical cursor is located on the server, but database is physically with the cursor located on the client. Typically, server cursors are loaded faster than client-side cursors, because when you ...