Method and device for reading and writing cache memory on basis of Spring expression language

Abstract

The invention discloses a method for reading and writing a cache memory on the basis of a Spring expression language. The method comprises the following steps of: generating a cache secret key by utilizing the Spring expression language on the basis of an attribute of a user; and outputting data, corresponding to a cache secret key, stored in the cache memory when the fact that the cache secret key matched with the generated cache secret key exists in the cache memory is determined.

Description

technical field [0001] The present disclosure relates generally to cache memory reading and writing, and more particularly, to methods and apparatus for reading and writing cache memory based on the Spring Expression Language. Background technique [0002] A cache is a fast temporary storage built to avoid frequently fetching data from a database or disk file. The use of cache can effectively improve the load capacity of the website and reduce the service response time. Spring cache is not a specific cache implementation (such as EHCache or OSCache) in essence, but an abstraction for cache use. By adding a small amount of various annotations defined by it to the existing code, the return object of the cache method can be achieved Effect. However, the existing technology has the following disadvantages: it is based on the dynamically generated proxy mechanism to aspect the method call, if the method of the object is an internal call (that is, this reference), or if the non-...

AI Technical Summary

Problems solved by technology

However, the existing technology has the following disadvantages: it is based on the dynamically generated proxy mechanism to aspect the method call, if the method of the object is an internal call (that is, this reference), or if the non-public method wants to implement annotation-based caching It will cause the proxy mechanism to fail, and the aspect will also fail; when writing data, there will be operations to insert cache during the execution of business logic, which will lengthen the response time of the entire service; it cannot be started and stopped at any time, as long as it does not throw If an exception occurs, the method data will be cached, not according to the return result of the method, and the applicable scenarios have strong restrictions; if the data expiration time of different methods is different, multiple cache instance objects must be defined, the maintenance cost is high, and If you need to modify the cache settings, you must restart the service, which is poor in flexibility; there is no corresponding solution for preventing cache penetration and instantaneous timeout of large batches of data in the same service.

Images