An optimized Java Web three-tier architecture and optimization method

Abstract

The invention discloses an optimized three-layer structure of Java Web and an optimized method thereof, The optimized three-tier architecture for Java Web, includes a presentation layer, a business layer and a persistence layer, wherein the presentation layer is used for Web end interaction with users, the business layer is used for realizing business logic, and the persistence layer is used for encapsulating database interaction, and The optimized three-tier architecture further comprises a memory data pool, a modified data buffer pool and a persistence processing layer, wherein the memory data pool is used for storing data frequently accessed and operated in the database; the modified data buffer pool is used for storing the data modified by the service layer; the persistence processinglayer is used for obtaining data from the modified data buffer pool and synchronizing the data to the database. The invention introduces the concepts of the memory data pool and the persistent processing layer for the three-layer structure, so as to achieve the purposes of improving the operation efficiency of the structure and enhancing the expansibility of the system.

Description

technical field [0001] The invention relates to the field of electronic technology, in particular to an optimized Java Web three-layer architecture and an optimization method. Background technique [0002] The Java Web three-tier architecture is a popular idea based on modular programming, and it is also a standard module division method for current Web applications. The three layers in the architecture are presentation layer, business layer and persistence layer. The presentation layer is used to interact with users on the Web side, the business layer is used to implement business logic, and the persistence layer is used to encapsulate database interaction. The three-tier architecture diagram is as follows figure 1 shown. [0003] When this three-tier architecture is faced with high-concurrency web applications, since high-concurrency web applications mean a large number of accesses to data in the persistence layer, data in the persistence layer is usually stored in the ...

AI Technical Summary

Problems solved by technology

[0003] When this three-tier architecture is faced with high-concurrency web applications, since high-concurrency web applications mean a large number of accesses to data in the persistence layer, data in the persistence layer is usually stored in the database. On the one hand, frequent access to the database It will definitely affect the operating efficiency of the system, thereby affecting the user's access experience; on the other hand, in order to avoid dirty data in the database, read-write locks are often used in the read and write operations of the database, and frequent access to the database will inevitably increase the read-write lock. Lock competition further reduces the rate of data access, thereby reducing the performance of the system

At the same time, if the business layer adds or modifies the data acquisition requirements, it needs to be modified in the persistence layer code accordingly. This cascading modification reduces the scalability of the system and leads to poor system maintainability.

Images