CN105574158A - Refreshing method and system of database caching data - Google Patents

Abstract

The invention provides a refreshing method and system of database caching data. The refreshing method comprises the following steps: receiving a primary library update message which contains primary library update time which is updated at the time and an updated data object, obtaining the auxiliary library update time of a corresponding data object in an auxiliary library, then, comparing the primary library update time and the auxiliary library update time, and executing a caching data refreshing operation if the auxiliary library update time is longer than the primary library update time. Therefore, the refreshing of the caching data can be realized without a situation that development personnel increase development codes of timing task inspection so as to lower the development cost of the refreshing of the database caching data.

Description

Method and system for refreshing database cache data

technical field

The invention relates to the field of databases, in particular to a method and system for refreshing cached data in a database.

Background technique

In the scenario where the database reads and writes are separated, there will be a certain delay in replicating data from the database, and the source of the cached data is from the database. When the data is modified and the cache needs to be refreshed, it takes a long time to wait.

In the current existing solutions, the modified information is usually recorded in the main library, and then the data in the slave library is checked by a scheduled task check. If there is an update, the cache is refreshed, otherwise continue to wait for the task check. Therefore, developers need to spend a lot of energy to increase the development code of scheduled task checking to realize the refreshing of cached data, thereby increasing the development cost of refreshing the database cached data.

Contents of the invention

In view of the high development cost of database cache data refresh in the above prior art, the purpose of the present invention is to provide a database cache data refresh method and system thereof, which can reduce the development cost of database cache data refresh.

Refresh method of database cache data, including:

Receive the message of main library data update, the message includes the time of this update and the updated data object, record the time as the update time of the main library;

Obtain the latest update time of the corresponding data object in the slave library, record it as the update time of the slave library, and compare the update time of the slave library with the update time of the master library;

If the update time of the slave library is greater than or equal to the update time of the master library, a cache data refresh operation is performed according to the message.

Refresh system for database cache data, including:

The message receiving module is used to receive the message of master database data update, and said message includes the time of this update and the updated data object, and records said time as master database update time;

The message comparison module is used to obtain the latest update time of the corresponding data object in the slave library, which is recorded as the update time of the slave library, and compares the update time of the slave library with the update time of the main library;

A data refresh module, configured to perform a cache data refresh operation according to the message if the update time of the slave library is greater than or equal to the update time of the master library.

The method and system for refreshing database cached data of the present invention obtains the update time of the corresponding data object in the slave library by receiving the update time of the master library including the update time of the master library and the updated data object of the master library, and then Comparing the update time of the slave library with the update time of the master library, if the update time of the slave library is greater than or equal to the update time of the master library, perform a refresh operation of cached data according to the message. Therefore, the refresh of cached data can be realized without developers adding development codes for timing task checking, thereby reducing the development cost of refreshing database cached data.

Description of drawings

Fig. 1 is a schematic flow chart of a method for refreshing database cached data of an embodiment;

Fig. 2 is an example diagram of the refreshing method of database cache data;

Fig. 3 is a schematic structural diagram of a system for refreshing database cache data according to an embodiment.

detailed description

In order to make the purpose, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings.

Please refer to FIG. 1 for a schematic flowchart of a method for refreshing database cache data in an embodiment.

A method for refreshing database cache data, comprising:

S102. Receive a data update message of the master database, the message includes the time of this update and the updated data object, and record the time as the update time of the master database.

By receiving the data update message of the master database, determine the update time of the master database and the updated data objects, and provide a benchmark for the comparison of subsequent update times.

S104. Obtain the latest update time of the corresponding data object in the slave library, record it as the update time of the slave library, and compare the update time of the slave library with the update time of the master library.

By obtaining the latest update time of the corresponding data object in the slave library, determine the update time of the slave library, and compare the update time of the slave library with the update time of the master library to judge the update status of the corresponding data object in the slave library, thereby improving the judgment of the slave library The convenience of data update.

S106. If the update time of the slave library is greater than or equal to the update time of the master library, perform a cache data refresh operation according to the message.

If the update time of the slave library is greater than or equal to the update time of the main library, it means that the corresponding data object in the slave library has been updated in this update, and the refresh operation of the cached data is performed. Therefore, by actively performing the refresh of the cached data operation, thereby shortening the waiting refresh time of cached data and improving the refresh efficiency of cached data.

In this embodiment, by receiving the main library data update message containing the updated main library update time and the updated data object, the slave library update time of the corresponding data object in the slave library is obtained, and then the slave library update time is compared with the Master database update time, if the slave database update time is greater than or equal to the master database update time, perform a cache data refresh operation according to the message. Therefore, the refresh of cached data can be realized without developers adding development codes for timing task checking, thereby reducing the development cost of refreshing database cached data.

In one of the embodiments, the comparison of the update time of the slave library and the update time of the master library includes:

If the update time of the slave library is less than the update time of the master library, store the identifier of the message in a preset service queue.

Wherein, the identification of the message is the label of the message of the main library data update this time, and only the identification of the message needs to be stored, thereby saving system resources; the service queue is used to store the identification of the message, and The identification of the message to monitor.

In one of the embodiments, the step of storing the identifier of the message into a preset service queue includes:

Detect whether the time for storing the identifier of the message in the service queue reaches a set duration, and if so, return a response that the message fails to be received, so as to receive the message again.

Through detection, if the time for the identifier of the message to be stored in the service queue reaches the set duration, return a response that the message fails to be received, to re-receive the message, and after re-receiving the message, again Judgment is made on the data update status of the slave database to improve the judgment efficiency of the slave database data update.

In one of the embodiments, the receiving the message of master database data update includes:

Receiving the message of the main library data update sent by the preset message queue, the message queue obtains the message of the main library data update in real time, thereby improving the efficiency of obtaining the message of the data update;

The executing the refresh operation of cached data according to the message further includes,

Returning a response that the message is received successfully to the message queue, releasing the occupied resources of the corresponding message in the message queue, thereby improving the operating efficiency of the message queue;

The returning a response of failure to receive the message to re-receive the message includes,

Returning a response of failure to receive the message to the message queue, and receiving the message resent by the message queue, so as to continue to judge the data update situation of the slave database, and improve the judgment efficiency of the data update of the slave database.

FIG. 2 is an example diagram of a method for refreshing database cached data. In combination with FIG. 2 , the embodiment of the method for refreshing database cached data of the present invention will be further described below with a specific example.

Specifically, a message queue 204 is set between the updating component 202 and the processing component 203 . When the main library 200 data was updated, the update component 202 sent a notification message of updating the cache to the message queue 204, and the message included the update time of the main library and the updated data object; the processing component 203 received the update message forwarded by the message queue 204, Obtain the latest update time (recorded as the update time from the library) of the corresponding data object in the library 201, and compare the update time from the library with the update time of the main library, if the update time from the library is greater than or equal to the main library update time, then the processing component 203 performs the refresh operation of cached data according to the message, and returns a response that the message is received successfully to the message queue 204; otherwise, the message identifier is stored in the preset service queue 205 ; detect whether the time for the identification of the message to be stored in the service queue 205 reaches 120 seconds, if so, return the response of the message reception failure to the message queue 204, and put the message back in the message queue 204, The processing component 203 will re-receive the message, making full use of the delayed confirmation mechanism of the message queue, making cache refreshing simple and efficient, and facilitating the realization of scenarios requiring asynchronous cache refreshing.

In one of the embodiments, the message queue is a RabbitMQ queue, and the set duration is 120 seconds.

The RabbitMQ queue has powerful performance and is easy to use, and it is used in this embodiment to improve the operability of the message queue; while the setting time of 120 seconds improves the judgment efficiency of slave database data update, the frequency of judgment is not too high. Dense, so as not to take up too many system resources.

The present invention also provides a refresh system for database cache data, as shown in Figure 3, comprising:

The message receiving module 300 is configured to receive a message of data update of the master database, the message includes the time of this update and the updated data object, and the time is recorded as the update time of the master database.

The message receiving module 300 determines the update time of the main library and the updated data objects by receiving the message of the main library data update, so as to provide a benchmark for the comparison of subsequent update times.

The message comparison module 301 is configured to obtain the latest update time of the corresponding data object in the slave library, which is recorded as the update time of the slave library, and compare the update time of the slave library with the update time of the master library.

The message comparison module 301 determines the update time of the slave library by obtaining the latest update time of the corresponding data object in the library, and compares the update time of the slave library with the update time of the master library to determine the update situation of the corresponding data object in the slave library , so as to improve the convenience of judging the data update of the slave library.

The data refresh module 302 is configured to perform a cache data refresh operation according to the message if the update time of the slave library is greater than or equal to the update time of the master library.

If the update time of the slave library is greater than or equal to the update time of the main library, it means that the corresponding data object in the slave library has been updated in this update, and the refresh operation of the cached data is performed. Therefore, by actively performing the refresh of the cached data operation, thereby shortening the waiting refresh time of cached data and improving the refresh efficiency of cached data.

In this embodiment, the message receiving module 300 receives the master library data update message containing the updated master library update time and the updated data object this time, and the message comparison module 301 obtains the slave library update time of the corresponding data object in the slave library, and then compares From the update time of the database and the update time of the master database, the data refresh module 302 judges that if the update time of the slave database is greater than or equal to the update time of the master database, then perform a cache data refresh operation according to the message. Therefore, the refresh of cached data can be realized without developers adding development codes for timing task checking, thereby reducing the development cost of refreshing database cached data.

In one of the embodiments, the data refresh module is further configured to store the identifier of the message in a preset service queue if the update time of the slave library is shorter than the update time of the master library.

In one of the embodiments, the data refresh module is also used to detect whether the time for storing the identifier of the message in the service queue reaches the set duration, and if so, return a response that the message fails to be received to receive it again said message.

Wherein, the identification of the message is the label of the message of the main library data update this time, and only the identification of the message needs to be stored, thereby saving system resources; the service queue is used to store the identification of the message, and The identification of the message is monitored, and if the time for storing the identification of the message in the service queue reaches the set duration, a response that the message fails to be received is returned to receive the message again, thereby continuing to process the slave library. The data update status is judged to improve the judgment efficiency of slave database data update.

In one of the embodiments, the system for refreshing the database cache data further includes:

The message transfer module is used to obtain the data update message of the main database in real time through the preset message queue, thereby improving the efficiency of obtaining the message of data update;

The message receiving module includes:

The receiving sub-module is used to receive the message of master database data update sent by the message transfer module;

The first response sub-module is configured to return a response to the message transfer module that the message is received successfully after performing the cache data refresh operation according to the message, so as to release the occupied resources of the corresponding message in the message queue, thereby improving the message The operating efficiency of the queue;

The second response sub-module is used to return a response that the message fails to be received to the message transfer module if the time for the message identifier to be stored in the service queue reaches the set duration, and receive the message transfer module again The message is sent, so as to continue to judge the data update situation of the slave database, and improve the judgment efficiency of the data update of the slave database.

In one of the embodiments, the message queue is a RabbitMQ queue, and the set duration is 120 seconds.

The RabbitMQ queue has powerful performance and is easy to use, and it is used in this embodiment to improve the operability of the message queue; while the setting time of 120 seconds improves the judgment efficiency of slave database data update, the frequency of judgment is not too high. Dense, so as not to take up too many system resources.

The various technical features of the above-mentioned embodiments can be combined arbitrarily. For the sake of concise description, all possible combinations of the various technical features in the above-mentioned embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, should be considered as within the scope of this specification.

The above-mentioned embodiments only express several implementation modes of the present invention, and the descriptions thereof are relatively specific and detailed, but should not be construed as limiting the patent scope of the present invention. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present invention, and these all belong to the protection scope of the present invention. Therefore, the protection scope of the patent for the present invention should be based on the appended claims.

Claims (10)

1. The refresh method of database cache data is characterized in that, comprising: Receive the message of main library data update, the message includes the time of this update and the updated data object, record the time as the update time of the main library; Obtain the latest update time of the corresponding data object in the slave library, record it as the update time of the slave library, and compare the update time of the slave library with the update time of the master library; If the update time of the slave library is greater than or equal to the update time of the master library, a cache data refresh operation is performed according to the message. 2. the refresh method of database cache data according to claim 1, is characterized in that, described comparing described from library update time and described master library update time, comprising afterwards: If the update time of the slave library is less than the update time of the master library, store the identifier of the message in a preset service queue. 3. The refresh method of the database cache data according to claim 2, characterized in that, storing the identifier of the message into a preset service queue, and then comprising: Detect whether the time for storing the identifier of the message in the service queue reaches a set duration, and if so, return a response that the message fails to be received, so as to receive the message again. 4. the refresh method of database cache data according to claim 3, is characterized in that, the message that described receiving master library data update comprises: Receive the message that the preset message queue sends the main library data update, and the message queue obtains the message of the main library data update in real time; The executing the refresh operation of cached data according to the message further includes, Returning a response that the message is received successfully to the message queue; The returning a response of failure to receive the message to re-receive the message includes, Returning a response that the message fails to be received to the message queue, and receiving the message resent by the message queue. 5. The method for refreshing database cache data according to claim 4, wherein the message queue is a RabbitMQ queue, and the set duration is 120 seconds. 6. The refreshing system of database cache data is characterized in that, comprising: The message receiving module is used to receive the message of master database data update, and said message includes the time of this update and the updated data object, and records said time as master database update time; The message comparison module is used to obtain the latest update time of the corresponding data object in the slave library, which is recorded as the update time of the slave library, and compares the update time of the slave library with the update time of the main library; A data refresh module, configured to perform a cache data refresh operation according to the message if the update time of the slave library is greater than or equal to the update time of the master library. 7. The refreshing system of database cache data according to claim 6, is characterized in that, The data refreshing module is further configured to store the identifier of the message into a preset service queue if the update time of the slave database is less than the update time of the master database. 8. The refreshing system of database cache data according to claim 7, is characterized in that, The message receiving module is further configured to detect whether the time for storing the identifier of the message in the service queue reaches a set duration, and if so, return a response that the message fails to be received, so as to receive the message again. 9. The system for refreshing database cache data according to claim 8, further comprising: The message transfer module is used to obtain real-time data update messages of the main database through the preset message queue; The message receiving module includes: The receiving sub-module is used to receive the message of master database data update sent by the message transfer module; The first response sub-module is configured to return a response that the message is received successfully to the message transfer module after the cache data refresh operation is performed according to the message; The second response sub-module is used to return a response that the message fails to be received to the message transfer module if the time for the message identifier to be stored in the service queue reaches the set duration, and receive the message transfer module again The message sent. 10. The system for refreshing database cached data according to claim 9, wherein the message queue is a RabbitMQ queue, and the set duration is 120 seconds.