CN114327603A - Data caching method and device thereof, and computer-readable storage medium - Google Patents

Abstract

The invention discloses a data caching method and device and a computer readable storage medium. Wherein, the method comprises the following steps: monitoring the main version number of the target data storage medium to obtain a monitoring result; when the monitoring result shows that the major version number changes, comparing the major version number with the current version number of the target data cache center to obtain a version number comparison result; when the comparison result of the version numbers is determined to show that the major version number is larger than the current version number, obtaining updated data in the target data storage medium based on the major version number; and caching the updated data to a target data caching center. The invention solves the technical problems of low data updating automation degree and large workload of operation and maintenance personnel caused by poor compatibility of the cache data updating component in the related technology.

Description

Data caching method and device thereof, and computer-readable storage medium

technical field

The present invention relates to the field of data processing, and in particular, to a data caching method and device thereof, and a computer-readable storage medium.

Background technique

In the current local cache solutions, commonly used cache components such as spring cache, google gauva, and ehance are used to manage cached data. The data cache of these solutions requires developers to write additional code to manage them, which is more intrusive to the application.

Although the application itself can realize the local cache, it can also meet the needs of fast data access, but because the cache data management logic is not universal, and the data needs to be refreshed manually when updating, etc., additional workload is required to complete the cache requirements.

In addition, by adopting the centralized cache management of the middleware, the introduction of the cache middleware system will increase the cost of system maintenance and operation and maintenance, and increase the burden on the development and operation and maintenance personnel.

For the above problems, no effective solution has been proposed yet.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a data caching method and device, and a computer-readable storage medium, so as to at least solve the problem that the poor compatibility of cached data update components in the related art leads to a low degree of data update automation and a large workload of operation and maintenance personnel technical issues.

According to an aspect of the embodiments of the present invention, a data caching method is provided, comprising: monitoring the major version number of a target data storage medium to obtain a monitoring result; when the monitoring result indicates that the major version number has changed, Compare the main version number with the current version number of the target data cache center to obtain a version number comparison result; when it is determined that the version number comparison result indicates that the main version number is greater than the current version number, based on The major version number acquires the update data in the target data storage medium; and caches the update data in the target data cache center.

Optionally, the target data storage medium includes a plurality of data tables, and each data table in the plurality of data tables is provided with a slave version number, wherein, when the data in the each data table changes, The corresponding secondary version number is automatically updated; when the secondary version number is updated, the primary version number is automatically updated, and the update information of the secondary version number is recorded in the primary version number.

Optionally, comparing the main version number with the current version number of the target data cache center to obtain a version number comparison result, including: obtaining the main version number and the current version number; The information is compared with the current version number to obtain the version number comparison result.

Optionally, acquiring the update data in the target data storage medium based on the master version number includes: determining a target slave version number based on the master version number; determining in a target data table corresponding to the target slave version number When there is data update, the update data is obtained from the target data table.

Optionally, the method further includes: when it is determined that there is no data update in the target data table corresponding to the target slave version number, replacing the cache slave version number in the data cache center with the target slave version number. .

Optionally, the method further includes: updating the cache main version number of the data cache center.

Optionally, caching the update data to the data cache center includes: determining the cache slave version number based on the target slave version number; searching a cache data table corresponding to the cache slave version number, wherein the The cache data table is a data table included in the data cache center; the update data is cached to the cache data table.

Optionally, after the update data is cached in the target data cache center, the method further includes: deleting historical cache data in the cache data table.

According to another aspect of the embodiments of the present invention, there is also provided a data caching device, including: a monitoring module for monitoring the main version number of a target data storage medium to obtain a monitoring result; a comparison module for The monitoring result indicates that when the main version number changes, the main version number is compared with the current version number of the target data cache center to obtain a version number comparison result; an acquisition module is used to determine the version number When the comparison result indicates that the major version number is greater than the current version number, the update data in the target data storage medium is obtained based on the major version number; the cache module is configured to cache the update data to the target Data cache center.

Optionally, the target data storage medium includes a plurality of data tables, and each data table in the plurality of data tables is provided with a slave version number, wherein, when the data in the each data table changes, The corresponding secondary version number is automatically updated; when the secondary version number is updated, the primary version number is automatically updated, and the update information of the secondary version number is recorded in the primary version number.

Optionally, the comparison module includes: a first acquisition unit for acquiring the main version number and the current version number; a comparison unit for comparing the main version number with the current version number Perform information comparison to obtain the version number comparison result.

Optionally, the obtaining module includes: a first determining unit for determining a target slave version number based on the master version number; a second obtaining unit for determining a target data table corresponding to the target slave version number When there is data update in the target data table, the update data is obtained from the target data table.

Optionally, the device further includes: a replacement module, configured to replace the data cache center with the target slave version number when it is determined that there is no data update in the target data table corresponding to the target slave version number. The cache from the version number.

Optionally, the apparatus further includes: an update module configured to update the cache main version number of the data cache center.

Optionally, the cache module includes: a second determination unit for determining the cache slave version number based on the target slave version number; a search unit for searching a cache data table corresponding to the cache slave version number , wherein the cache data table is a data table included in the data cache center; a cache unit is configured to cache the update data to the cache data table.

Optionally, the apparatus further includes: a deletion unit, configured to delete the historical cached data in the cached data table after the updated data is cached in the target data cache center.

According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, the computer-readable storage medium comprising a stored computer program, wherein the computer is controlled when the computer program is run by a processor The device where the readable storage medium is located executes the data caching method described in any one of the above.

According to another aspect of the embodiments of the present invention, a processor is also provided, and the processor is configured to run a computer program, wherein the computer program executes any one of the data caching methods described above when the computer program runs.

In the embodiment of the present invention, the main version number of the target data storage medium is monitored to obtain a monitoring result; when the monitoring result indicates that the main version number has changed, the main version number is compared with the current version number of the target data cache center , obtain the version number comparison result; when it is determined that the version number comparison result indicates that the main version number is greater than the current version number, obtain the update data in the target data storage medium based on the main version number; cache the update data in the target data cache center. The data caching method provided by the embodiment of the present invention achieves the purpose of updating and caching data by monitoring the main version number of the target data storage medium, thereby achieving the technical effect of improving the system throughput rate, and further solving the problems in the related art. The poor compatibility of cached data update components leads to technical problems that the automation of data update is low and the workload of operation and maintenance personnel is large.

Description of drawings

The accompanying drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the attached image:

1 is a flowchart of a data caching method according to an embodiment of the present invention;

FIG. 2 is a flowchart of a request query cache response according to an embodiment of the present invention;

Fig. 3 is the flow chart of cache SDK parameter version update according to an embodiment of the present invention;

4 is a schematic diagram of cache component cooperation according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a data caching apparatus according to an embodiment of the present invention.

Detailed ways

In order to make those skilled in the art better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only Embodiments are part of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

It should be noted that the terms "first", "second" and the like in the description and claims of the present invention and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the invention described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

Example 1

According to an embodiment of the present invention, a method embodiment of a data caching method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings may be executed in a computer system such as a set of computer-executable instructions, and, Although a logical order is shown in the flowcharts, in some cases steps shown or described may be performed in an order different from that herein.

FIG. 1 is a flowchart of a data caching method according to an embodiment of the present invention. As shown in FIG. 1 , the method includes the following steps:

Step S102, monitor the major version number of the target data storage medium to obtain a monitoring result.

Optionally, in the above steps, the target data storage medium includes but is not limited to: a local cache and a server cache.

Step S104, when the monitoring result indicates that the main version number has changed, compare the main version number with the current version number of the target data cache center to obtain a version number comparison result.

Optionally, in the above steps, during the monitoring process, when the major version number changes, the current major version number is compared with the current version number of the target data cache center, and a comparison result is obtained.

Step S106, when it is determined that the version number comparison result indicates that the major version number is greater than the current version number, acquire the update data in the target data storage medium based on the major version number.

Step S108, cache the updated data to the target data cache center.

As can be seen from the above, in the embodiment of the present invention, firstly, the main version number of the target data storage medium can be monitored to obtain the monitoring result; then, when the monitoring result indicates that the main version number has changed, the main version number and the target data can be cached. The current version number of the center is compared to obtain the version number comparison result; then, when it is determined that the version number comparison result indicates that the main version number is greater than the current version number, the update data in the target data storage medium can be obtained based on the main version number; finally Update data can be cached to the target data cache center. The data caching method provided by the embodiment of the present invention achieves the purpose of updating and caching data by monitoring the main version number of the target data storage medium, thereby achieving the technical effect of improving the system throughput rate, and further solving the problems in the related art. The poor compatibility of cached data update components leads to technical problems that the automation of data update is low and the workload of operation and maintenance personnel is large.

As an optional embodiment, the target data storage medium includes a plurality of data tables, and each data table in the plurality of data tables is set with a slave version number, wherein when the data in each data table changes, its The corresponding slave version number is automatically updated; when there is an update in the slave version number, the master version number is automatically updated, and the update information of the slave version number is recorded in the master version number.

In the above optional embodiment, in order to record the data update history of the database parameter table and manage the cached parameter data, the parameter table version zipper method is designed and implemented with the parameter update version as the data dimension. The parameter table version zipper method records every change of data in the parameter table by updating the major version number change table A and the minor version change table B. This design is the basis for the management parameters of the cache component. The specific steps of this method are as follows:

Step 1), assuming that there is a parameter table T ₁ , each record in T ₁ has a version number V _t , when there is data change, a new record is added in the A table, and the content is: (AV ₁ , AV ₀ , VFlag, UpdateTime), wherein, AV ₁ represents the current version number of the A table; AV ₀ represents the previous version number of the A table; VFlag represents the version synchronization state of the A table; The specific table update information is recorded in the B table, and the content is: (T ₁ , PV _t , AV ₁ , C, UpdateTime) Among them, T ₁ represents the parameter table name; PV _t represents the parameter table record version number; AV ₁ represents the current A Table version number; C represents the maximum value of the A table record version number; UpdateTime represents the update time.

Step ₂ ), when the T1 table has data update again, the version number written in the record in the T1 table is Vt _{+1, and} the newly added record in the _A table is as follows: (AV2, AV1, _VFlag , UpdateTime); The newly added records in table B are as follows: (T ₁ , PV _t+1 , AV ₂ , C, UpdateTime), and at the same time modify the records in table B (T ₁ , PV _t , AV ₁ , C, UpdateTime) to (T ₁ , PV _t , AV ₁ , AV ₂ , UpdateTime).

Step ₃ ), when T1 table data is updated again, upgrade the corresponding version number, repeat the steps of step 1) and step 2), and cache the parameter table data cached in the SDK (that is, the target data storage medium) according to the A table version. Number cache, the initial value is (AV, Cache), AV is the current version number of the A table, and Cache is the cache data object of the version parameter table; in order to ensure that the cache data is available, cache data with two version numbers is stored in the cache SDK for A version of cached data is guaranteed to be available when replacing a new version. When a new version of table A is added, trigger the cache SDK module to go to the configuration center to pull the latest version number of table A, and upload the version number to the parameter query service module to pull the corresponding version data.

As an optional embodiment, the main version number is compared with the current version number of the target data cache center to obtain the version number comparison result, including: obtaining the main version number and the current version number; comparing the main version number with the current version number The version number is compared for information, and the version number comparison result is obtained.

In the above-mentioned optional embodiment, the main version number and the current version number are obtained first, and then they are compared to obtain a comparison result of whether the main version number and the current version number are consistent.

As an optional embodiment, acquiring the update data in the target data storage medium based on the master version number includes: determining the target slave version number based on the master version number; determining that there is a data update in the target data table corresponding to the target slave version number , get updated data from the target data table.

In the above-mentioned optional embodiment, the cached SDK loading parameter table is divided into two modes: active loading and lazy loading. The active loading mode is to load the data in the configured parameter table into the memory when the application starts (that is, in the embodiment of the present invention, the main version number and the current version number are actively obtained and compared to obtain the comparison result); lazy loading mode When the application starts, the parameter table data is not loaded first, and when there is a query request to query the parameter table data, the data is cached (that is, when there is a data update in the target data table corresponding to the version number of the determined target in the embodiment of the present invention, the data from the target data is updated. table gets updated data). The data has hot data and cold data, and the table, as a collection of data, also has the difference between hot and cold. The advantage of the two cache modes is that the cache mode can be determined according to the hot and cold of the table dimension, and the active loading mode can cope with the rapidity of the full amount of hot data. The lazy loading mode can filter out the hot data in the cold table for caching, which not only saves memory space, but also accelerates data access in a targeted manner.

As an optional embodiment, the data caching method further includes: when it is determined that there is no data update in the target data table corresponding to the target slave version number, replacing the cache slave version number in the data cache center with the target slave version number .

As an optional embodiment, the data cache method further includes: updating the cache main version number of the data cache center.

The specific steps of the data caching method are described in detail below:

Step a. Parameter table loading mode. The cache SDK loading parameter table is divided into two modes: active loading and lazy loading. Active loading mode is to load the data in the configured parameter table into memory when the application starts. In the lazy loading mode, the parameter table data is not loaded first when the application starts, and the parameter table data is cached when there is a query request to query the parameter table data. The data has hot data and cold data, and the table, as a collection of data, also has the difference between hot and cold. The advantage of the two cache modes is that the cache mode can be determined according to the hot and cold of the table dimension, and the active loading mode can cope with the rapidity of the full amount of hot data. The lazy loading mode can filter out the hot data in the cold table for caching, which not only saves memory space, but also accelerates data access in a targeted manner.

Step b. Cache initialization. The cache SDK determines how to load data and create memory index objects according to the table load mode, index field, primary key field, cache enable flag, etc. specified in the configuration file, and supports the creation of cache data indexes based on the primary key and configuration fields. Through the provided SPI interface, the combination of cached data can also be extended.

Step c. Parameter table data access. Fig. 2 is a flow chart of requesting a query cache response according to an embodiment of the present invention. As shown in Fig. 2, for parameter table data access in active loading mode, when querying parameter table data, the sql statement operation mapping interface aspect in DaoSupport is set , for all query requests that need to access parameter table data, by weaving the access cache Advice(@Around(doPointSelectList()) into Pointcut(@Pointcut(“execution(public*DaoSupport.selectList(..))&&args(java. lang.String,..)”)) specified Joinpoint to achieve the purpose of obtaining data from the cache. Parse the query statement conditions, compare the index field set, if the index field is hit, go to the cache index to return the data, if not hit , the data is returned after creating an index based on this field.

In addition, for the parameter table data access in the lazy loading mode, by intercepting the query method in the Executor of MyBatis, parsing the sql statement and sql identifier in the query method, calling the parameter query service, realizing the lazy loading parameter table data query, and performing the data return after the data is returned. cache.

It should be noted that Mybatis is a data access layer framework that provides an extensible interceptor; SQL is a structured query language used to operate relational databases; Intercept method parameters before method invocation, perform operations such as verification and assignment; parameter table is the database table managed by the parameter cache component that the application needs to access; parameter table version is used to record the update history of parameter table data; Jointpoint (connection point) indicates A clearly defined point in a program typically includes method calls, access to class members, and execution of exception handler blocks, etc. It can also nest other joint points; Pointcut (pointcut) represents a group of joint points, These joint points are either combined through logical relationships, or concentrated through wildcards, regular expressions, etc., which define where the corresponding advice will occur; Advice (enhancement) defines the specific program points defined in Pointcut. The operation to do, it uses before, after and around to distinguish whether the code is executed before, after, or instead of each joint point.

As an optional embodiment, caching the update data to the data cache center includes: determining the cache slave version number based on the target slave version number; searching for a cache data table corresponding to the cache slave version number, wherein the cache data table is a data cache The data table contained in the center; caches updated data to the cache data table.

FIG. 3 is a flowchart of updating the parameter version of the cached SDK according to an embodiment of the present invention. As shown in FIG. 3 , after the cached SDK node detects that there is a change of the main version number, the data of the latest parameter table version is pulled. The steps for updating the cached SDK parameter version are described in detail.

Step 1), obtain the main version number, compare with the version number in the current cache, if the latest version number is greater than the version number in the memory, perform step 2), otherwise end.

Step 2), obtain the version number of the parameter table updated this time according to the main version number.

Step 3), determine whether the table is updated, if there is an update, pull the version number data, and delete the previous version data. If there is no update, replace the cached version number.

As an optional embodiment, after the update data is cached in the target data cache center, the data cache method further includes: deleting historical cache data in the cache data table.

FIG. 4 is a schematic diagram of the cooperation of cache components according to an embodiment of the present invention. As shown in FIG. 4 , the cache component consists of three parts: a cache SDK, a cache query service module and a data synchronization module. The caching SDK provides a caching service for common application parameters. By configuring the name of the parameter table to be cached, the component loads the cached data when the application starts. The cache query service module solves the problem of sudden increase in the number of connections caused by concurrent access to the database by multiple nodes, and is used for cache data acquisition. The data synchronization module is used to synchronize the data of the database parameter table and realize the consistency of the node cache and the database data. The following describes the specific steps of the cooperation of the cache components.

Step a. When there is data update in the parameter table, the data synchronization module synchronizes the version information to the master library and the version number queue, and performs data synchronization between the master and slave libraries.

Step b. The timing task of the data synchronization module monitors whether the queue version is updated or changed. If there is a new record, the information is pushed to the configuration center.

Step c. The cache SDK module monitors the data update changes in the configuration center, and after the data changes, obtains the latest version number and calls the cache query service to query the latest data.

As can be seen from the above, in the embodiment of the present invention, although there are many cache middlewares for data cache that can accelerate data access, the business logic code and the cache data code are often coupled together. Developers should pay attention to the data cache logic. If there is a problem with the logic, it is necessary to understand the principle of the cache middleware. The management of cached data needs to be maintained by developers, including data consistency, cache expiration replacement strategy, etc. Therefore, the embodiment of the present invention can introduce the management and management of cached data based on simple configuration. Synchronization, less intrusive to the application, no need to pay attention to the details of the cache implementation logic, and the access based on the cache index improves the access response speed.

Example 2

According to another aspect of the embodiment of the present invention, a data cache device is also provided. FIG. 5 is a schematic diagram of the data cache device according to an embodiment of the present invention. As shown in FIG. 5 , the device includes: a monitoring module 51 and a comparison module 53 , an acquisition module 55 and a cache module 57 . The data cache device will be described below.

The monitoring module 51 is used to monitor the main version number of the target data storage medium to obtain the monitoring result;

The comparison module 53 is used to compare the main version number with the current version number of the target data cache center when the monitoring result indicates that the main version number changes, and obtain the version number comparison result;

The obtaining module 55 is used to obtain the updated data in the target data storage medium based on the major version number when it is determined that the version number comparison result indicates that the major version number is greater than the current version number;

The cache module 57 is configured to cache the updated data to the target data cache center.

It should be noted here that the above-mentioned monitoring module 51, comparison module 53, acquisition module 55, and cache module 57 correspond to steps S102 to S108 in Embodiment 1, and the above-mentioned modules have the same examples and application scenarios as the corresponding steps. , but not limited to the content disclosed in Example 1 above. It should be noted that the above-mentioned modules can be executed in a computer system such as a set of computer-executable instructions as part of an apparatus.

As can be seen from the above, in the embodiment of the present invention, firstly, the monitoring module 51 can be used to monitor the main version number of the target data storage medium to obtain a monitoring result; then, the monitoring result can be used to indicate that the main version number changes with the help of the comparison module 53. , compare the main version number with the current version number of the target data cache center, and obtain the version number comparison result; then the acquisition module 55 can be used to determine that the version number comparison result indicates that the main version number is greater than the current version number, based on the main version number. The version number acquires the updated data in the target data storage medium; finally, the updated data can be cached to the target data cache center by means of the cache module 57 . Through the data caching device provided by the embodiment of the present invention, the purpose of updating and caching data by monitoring the main version number of the target data storage medium is achieved, thereby achieving the technical effect of improving the system throughput rate, and further solving the problems in the related art. The poor compatibility of cached data update components leads to technical problems that the automation of data update is low and the workload of operation and maintenance personnel is large.

Optionally, the target data storage medium includes a plurality of data tables, and each data table in the plurality of data tables is provided with a slave version number, wherein, when the data in each data table changes, its corresponding slave version number. Automatic update; when there is an update of the secondary version number, the main version number is automatically updated, and the update information of the secondary version number is recorded in the primary version number.

Optionally, the comparison module includes: a first acquisition unit for acquiring a main version number and a current version number; a comparison unit for performing information comparison between the main version number and the current version number to obtain a version number comparison result.

Optionally, the acquisition module includes: a first determination unit, used for determining a target slave version number based on the master version number; a second acquisition unit, used for determining that there is a data update in the target data table corresponding to the target slave version number, Get updated data from the target data table.

Optionally, the data cache device also includes: a replacement module, configured to replace the cache slave version number in the data cache center with the target slave version number when it is determined that there is no data update in the target data table corresponding to the target slave version number. .

Optionally, the data cache device further includes: an update module for updating the cache main version number of the data cache center.

Optionally, the cache module includes: a second determination unit for determining the cache slave version number based on the target slave version number; a search unit for searching the cache slave version number corresponding to the cache data table, wherein the cache data table is data. The data table contained in the cache center; the cache unit is used to cache the updated data to the cache data table.

Optionally, the data caching apparatus further includes: a deletion unit, configured to delete the historical cached data in the cached data table after the updated data is cached in the target data cache center.

Example 3

According to another aspect of the embodiments of the present invention, a computer-readable storage medium is also provided, where the computer-readable storage medium includes a stored computer program, wherein when the computer program is executed by the processor, a device where the computer-readable storage medium is located is controlled Perform any of the data caching methods above.

Example 4

According to another aspect of the embodiments of the present invention, a processor is also provided, where the processor is configured to run a computer program, wherein when the computer program runs, any one of the above data caching methods is executed.

The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages or disadvantages of the embodiments.

In the above-mentioned embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are only illustrative, for example, the division of the units may be a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or Integration into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of units or modules, and may be in electrical or other forms.

The units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes .

The above are only the preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the principles of the present invention, several improvements and modifications can be made. It should be regarded as the protection scope of the present invention.

Claims (11)

1. A method for caching data, comprising:

monitoring the main version number of the target data storage medium to obtain a monitoring result;

when the monitoring result shows that the major version number changes, comparing the major version number with the current version number of a target data cache center to obtain a version number comparison result;

when the comparison result of the version numbers is determined to indicate that the main version number is larger than the current version number, acquiring updating data in the target data storage medium based on the main version number;

and caching the updated data to the target data caching center.

2. The method according to claim 1, wherein the target data storage medium contains a plurality of data tables, each of the plurality of data tables is provided with a slave version number, and when data in each data table changes, the corresponding slave version number is automatically updated; when the slave version number is updated, the master version number is automatically updated, and the update information of the slave version number is recorded in the master version number.

3. The method of claim 1, wherein comparing the major version number with a current version number of a target data cache center to obtain a comparison result of version numbers comprises:

acquiring the main version number and the current version number;

and comparing the information of the main version number with the information of the current version number to obtain a comparison result of the version number.

4. The method of claim 2, wherein obtaining update data in the target data storage medium based on the master version number comprises:

determining a target slave version number based on the master version number;

and when the target is determined to have data update from the target data table corresponding to the version number, acquiring the update data from the target data table.

5. The method of claim 4, further comprising:

and when it is determined that no data update exists in the target data table corresponding to the target slave version number, replacing the cache slave version number in the data cache center with the target slave version number.

6. The method of claim 5, further comprising: and updating the main cache version number of the data cache center.

7. The method of claim 5, wherein caching the updated data to the data caching center comprises:

determining the cache slave version number based on the target slave version number;

searching a cache data table corresponding to the cache slave version number, wherein the cache data table is a data table contained in the data cache center;

and caching the updated data into the cache data table.

8. The method of claim 7, wherein after caching the updated data to the target data caching center, the method further comprises:

and deleting the historical cache data in the cache data table.

9. A data caching apparatus, comprising:

the monitoring module is used for monitoring the main version number of the target data storage medium to obtain a monitoring result;

the comparison module is used for comparing the main version number with the current version number of the target data cache center when the monitoring result shows that the main version number changes, so as to obtain a version number comparison result;

an obtaining module, configured to obtain, when it is determined that the version number comparison result indicates that the major version number is greater than the current version number, update data in the target data storage medium based on the major version number;

and the cache module is used for caching the updated data to the target data cache center.

10. A computer-readable storage medium, comprising a stored computer program, wherein the computer program, when executed by a processor, controls an apparatus in which the computer-readable storage medium is located to perform the data caching method of any one of claims 1 to 8.

11. A processor for executing a computer program, wherein the computer program executes to perform the data caching method of any one of the preceding claims 1 to 8.

Images