In fact, don't say more, everyone knows that the software system on the network can be roughly divided into B / S and C / S structures. For the C / S structure small understanding, just contact the actual C / S system architecture actually used in the project.
General Small Systems: Use the C / S system, individuals feel that there are no problems with architectural aspects. It is just a simple reading database and is displayed to the front desk. Generally, it is divided into two layers: server side, client, and is also a fat client. The server is also the RUN database.
And when the system is large enough, I don't want to talk about the architecture. The architecture of personal contact B / S also has some small knowledge, so it feels that the large C / S architecture is also referring to the architecture of B / S, and the truth does not leave the "ancestral".
A large C / S architecture I want to roughly divide: physical layer / business logic layer / user control layer / front interface layer.
The role between one layer is analyzed one by one:
Entity: It is used to communicate directly with the database, which is generally used to code generator. Map the table names and fields directly to the entity layer directly. The physical layer is generally used in bulk increase, and the timing is better because it is not necessary to deal with the database directly. And when just a simple SQL SELECT, I think it is still good to avoid the entity, and I will not get the opposite result.
Logical Control: If you really want to carefully consider the problem of architecture, I think business logic of this software system should not be easy. The designers and developers must have a headache. The best way is to put the business logic layer. As an undertaking, a good interface is defined for external calls. I think this is very similar to the Struts of the B / S structure J2EE.
User Control: This layer is mainly used to reduce the development, abstract the controls used by multiple places. Reuse. For example, pack DataGrid into its own system, and add some other controls such as Combo, Button to drag and drop to developers, greatly reduce the development. Of course, this part needs to complete the design work well in the previous period. Which part is needed, you can use more users to use users, you must make it in advance.
The front desk layer (User facade): This layer does not say more, I believe everyone can understand, that is, Form.
Lastly said: Limited the dependency between the levels, such as Entity can't call business logic layers ............
Warmly welcome you to shoot bricks! If you say something, please advise! Thank you. Next, some B / S architectures will be written, as well as the Data Warehouse's ETL articles!
