C/S architecture and B/S architecture, s Architecture

C/S architecture and B/S architecture, s Architecture

The content of this article is organized from http://blog.csdn.net/tennysonsky/article/details/45062079

The C/S architecture and B/S architecture are two influential software architectures. C/S is a long-established and sophisticated architecture. B/S is a new generation of architecture derived from C/S. There are many innovations in the web Information Age.

I. C/S architecture

What has always been popular and classic is the two-layer C/S architecture we want to study.

The C/S architecture consists of two layers: client and server. The first layer is the user presentation layer and the second layer is the database layer.

The client and server are directly connected, and both components assume important roles. The client at the first layer is not only capable of input, output, and operation. It can process business logic transactions in computing and data storage. The server at the second layer is mainly responsible for transaction logic processing, the transaction is heavy, but the client can share some logical transactions, thus reducing the burden on the server.

II. B/S architecture

With the popularity of Internet and WWW, the previous host/terminal and C/S cannot meet the new requirements of global network openness, interconnection, ubiquitous information and information sharing, the B/S mode is displayed, that is, the Browser/Server structure. It is an improvement of the C/S architecture. It can be said that it belongs to a three-layer C/S architecture.

Client Presentation Layer: used for interface guidance and user input, And sends a service request to the application server to display the processing result.

Application Server Business logic layer: executes the business logic and sends requests to the database.

Database Server Data storage layer: executes data logic and runs SQL statements or stored procedures.

The first layer isBrowserThat is, the client only has simple input and output functions to process a very small part of the transaction logic. Because the customer does not need to install the client, as long as there is a browser to browse the Internet, so it is oriented to a wide range of users, so the interface design is relatively simple, universal.

The second layer isWEB ServerAnd play the role of information transmission. When a user wants to access the database, the user will first send a request to the WEB server. After the WEB server agrees to the request, the user will send a request to access the database to the database server.SQL statement.

The third layer isDatabase ServerIt plays an important role because it stores a large amount of data. When the database server receives a request from the WEB server, it processes the SQL statement and sends the returned result to the WEB server. Next, the WEB server converts the received data into HTML text and sends it to the browser, that is, the interface we see in the browser.

Iii. Comparison between the C/S architecture and the B/S architecture

Compare items	C/S architecture	B/S architecture
Network Environment	Lan	Wan
Security requirements	For relatively fixed user groups, Strong Information Security Control Capabilities	Target unknown user groups, Relatively weak security control capabilities
Logical Transaction Processing	The client and server each handle part of the Logical transactions.	The client can only share simple input, output, and information. The main logic transaction processing still depends on the server.
Response Speed	Fast, especially when users increase	Slow
Software reuse	Difference	Good
System Maintenance	Difficult to upgrade	Easy to upgrade
User Interface	Close relationship with the operating system	Cross-platform, browser-related
Database Connection Type	ODBC connection, as long as the user connects to the database, the connection will remain intact Limit the number of users	JDBC connection, users do not maintain the connection to the database, so users are almost unlimited
Function	Complex to implement a single complex function. Currently, most large ERP systems are still in the C/S architecture.	Relatively weak, with fewer transaction logic to be processed, but the interface is more common
Technical personnel requirements	Relatively high	Relatively low