Cache breakdown prevention method and annotation component thereof

Abstract

The invention relates to a cache breakdown prevention method which comprises the following steps: an analysis step: analyzing a query request to obtain a key; a judgment step: judging whether data corresponding to the Key exists in the cache or not; a reading step: if the corresponding data of the Key exists in the cache, returning the corresponding data; and if not, locking the Key, executing a group of database read-write operations after successful locking, writing the results of the group of database read-write operations into the cache, removing the lock, and returning the results in thecache. Furthermore, the invention also relates to an annotation component for preventing cache breakdown, which comprises an analysis unit for analyzing the query request to obtain a key; a judging unit used for judging whether data corresponding to the Key exists in the cache or not; and a reading unit used for returning the corresponding data if the corresponding data of the Key exists in the cache; and if not, locking the Key, executing a group of database read-write operations after successful locking, writing the results of the group of database read-write operations into the cache, removing the lock, and returning the results in the cache.

Description

technical field [0001] The present application belongs to the technical field of anti-cache breakdown design, and in particular relates to an anti-cache breakdown method and an annotation component thereof. Background technique [0002] The cache annotation component annotates the business methods that require cache services in an aspect-oriented way to realize cache read and write, so that developers can use cache services transparently without paying attention to cache-related development, so that they can focus on business development. [0003] Spring 3.x provides caching-related annotations, which can implement aspect-oriented caching services. It has the following disadvantages: [0004] 1) It does not prevent cache breakdown. When the cache fails, a large number of concurrent requests are directly dropped into the database, causing the database to go down; [0005] 2) For all needs, there are many required functions, and the development and configuration are cumbersom...

AI Technical Summary

Problems solved by technology

[0004] 1) It does not prevent cache breakdown. When the cache fails, a large number of concurrent requests are directly dropped into the database, causing the database to go down;

[0005] 2) For all needs, there are many required functions, and the development and configuration are cumbersome;

Images