An optimized java Web three-tier system

Abstract

The invention discloses an optimized Java Web three-layer system, the optimized Java Web three-layer system includes a presentation layer, a business layer and a persistence layer, the presentation layer is used for interacting with users on the Web side, and the business layer For implementing business logic, the persistence layer is used to encapsulate database interaction, and also includes a memory data pool, a modified data cache pool and a persistent processing layer, and the memory data pool is used to store frequently accessed and operated data in the database; The changed data cache pool is used to store the data changed by the business layer; the persistent processing layer is used to acquire data from the changed data cache pool and synchronize to the database. The invention introduces the concepts of memory data pool and persistent processing layer into the three-layer system, so as to improve the operating efficiency of the framework and enhance the scalability of the system.

Description

technical field [0001] The invention relates to the field of electronic technology, in particular to an optimized Java Web three-tier system. 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 database. On the one hand, frequen...

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