CN110807040B - Method, device, equipment and storage medium for managing data - Google Patents
Method, device, equipment and storage medium for managing data Download PDFInfo
- Publication number
- CN110807040B CN110807040B CN201911046015.0A CN201911046015A CN110807040B CN 110807040 B CN110807040 B CN 110807040B CN 201911046015 A CN201911046015 A CN 201911046015A CN 110807040 B CN110807040 B CN 110807040B
- Authority
- CN
- China
- Prior art keywords
- data
- interface
- cache
- target
- managing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present disclosure relates to a method, an apparatus, a device and a storage medium for managing data, which are applied to a terminal device or a server, and the method includes: in response to the calling of a preset interface to change target data in a database, querying a dependency interface dependent on the preset interface from a pre-acquired interface dependency relationship table, wherein the interface dependency relationship table is used for recording the dependency relationship among the interfaces; and updating the content corresponding to the dependent interface in the locally stored cache expiration table based on the target data changed by the preset interface to obtain an updated cache expiration table. According to the cache overdue table updating method and device, the content corresponding to the dependent interface in the cache overdue table can be updated based on the target data changed by the preset interface, the updated cache overdue table is obtained, and then data can be provided for a user subsequently based on the cache overdue table, so that the waiting time of the user can be reduced, the user experience is improved, and the waste of network resources can be avoided.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a method, an apparatus, a device, and a storage medium for managing data.
Background
With the development of internet technology, a user may request an API (Application Programming Interface) to obtain remote data through a browser or an Application client in a terminal device.
However, in the related art, when operations such as jumping, refreshing a page, or re-opening a page are performed, the timeliness and validity of data are maintained by means of reacquiring an API. Specifically, each time the terminal device acquires the API, the terminal device needs to resend the request to the server to wait for the server to acquire data from the database, and then return the data to the terminal device. Even if the data is not changed, that is, the data acquired this time is the same as the data acquired last time, the http request has to be sent again, which not only causes the user to wait for the API interface to return the data, which affects the user experience, but also causes the waste of network resources.
Disclosure of Invention
The present disclosure provides a method, an apparatus, and a system for managing data to at least solve the technical problems in the related art.
The technical scheme of the disclosure is as follows:
according to a first aspect of embodiments of the present disclosure, there is provided a method of managing data, including:
in response to calling a preset interface to change target data in a database, querying a dependency interface dependent on the preset interface from a pre-acquired interface dependency relationship table, wherein the interface dependency relationship table is used for recording the dependency relationship among the interfaces, the preset interface comprises an interface used for adding, deleting or modifying data, and the dependency interface comprises an interface used for acquiring data and dependent on the preset interface;
and updating the content corresponding to the dependent interface in the locally stored cache expiration table based on the target data changed by the preset interface to obtain an updated cache expiration table.
In an embodiment, when the method for managing data is applied to a server, the method for managing data further includes:
and sending the updated cache expiration table to the terminal equipment so that the terminal equipment replaces the locally stored cache expiration table of the terminal equipment with the updated cache expiration table.
In an embodiment, the method for managing data further includes:
in response to receiving a first request for calling a target interface to acquire target data, searching the target interface from the interface dependency relationship table;
responding to the searched target interface, and detecting whether first cache data corresponding to the target data exists locally;
if the first cache data exists, judging whether the first cache data is valid or not based on the cache expiration table;
and if the first cache data is valid, providing the first cache data serving as target data to a sender of the first request.
In an embodiment, the method for managing data further includes:
if the first cache data does not exist or the first cache data exists but is invalid, sending a second request for acquiring the target data to target equipment, wherein the target equipment comprises a server under the condition that the method for managing the data is applied to terminal equipment; in the case that the method for managing data is applied to a server, the target device comprises a database;
and providing data returned by the target equipment in response to the second request as target data to a sender of the first request, storing the data serving as second cache data of the target data in the local, and recording the cache time of the second cache data.
In an embodiment, the step of detecting whether the first cache data corresponding to the target data exists locally in response to finding the target interface includes:
responding to the searched target interface, and judging whether the type of the target interface is the interface type of the acquired data;
and responding to the type of the target interface as the interface type of the acquired data, and detecting whether first cache data corresponding to the target data exists locally.
In an embodiment, the cache expiration table includes a modification time of the target data in the database;
the step of determining whether the first cache data is valid based on the cache expiration table includes:
obtaining the caching time of the first caching data;
if the caching time is later than the modification time, determining that the first caching data is valid;
and if the caching time is earlier than or equal to the modification time, determining that the first cache data is invalid.
In an embodiment, in a case that the method for managing data is applied to a server, the method for managing data further includes constructing the interface dependency table based on the following steps:
acquiring a code file of a server, wherein the code file comprises a first calling relation between each interface and each service layer, a second calling relation between each service layer and each data access layer and a third calling relation between each data access layer and each database table;
determining a dependency relationship between each interface and each database table based on the first call relationship, the second call relationship and the third call relationship;
and generating an interface dependency relationship table based on the dependency relationship among a plurality of interfaces associated with the same database table.
According to a second aspect of the embodiments of the present disclosure, there is provided an apparatus for managing data, which is applied to a terminal device or a server, and includes:
the system comprises a dependent interface query module, a database processing module and a data processing module, wherein the dependent interface query module is configured to execute the steps of responding to the calling of a preset interface to change target data in the database, and querying a dependent interface dependent on the preset interface from a pre-acquired interface dependent relation table, the interface dependent relation table is used for recording the dependent relation among interfaces, the preset interface comprises an interface used for adding, deleting or modifying data, and the dependent interface comprises an interface used for acquiring data and dependent on the preset interface;
and the cache expiration table updating module is configured to execute target data changed based on the preset interface, update the content corresponding to the dependent interface in the locally stored cache expiration table, and obtain an updated cache expiration table.
In an embodiment, when the apparatus for managing data is applied to a server, the apparatus for managing data further includes:
a cache expiration table sending module configured to send the updated cache expiration table to a terminal device, so that the terminal device replaces a locally stored cache expiration table of the terminal device with the updated cache expiration table.
In an embodiment, the apparatus for managing data further includes a target data providing module;
the target data providing module includes:
a target interface searching unit configured to perform searching for a target interface from the interface dependency relationship table in response to receiving a first request for calling the target interface to obtain target data;
the first data detection unit is configured to execute detection of whether first cache data corresponding to the target data exists locally or not in response to the target interface being found;
a first data judgment unit configured to perform, when the first cache data exists, judging whether the first cache data is valid based on the cache expiration table;
a first data providing unit configured to perform, when the first cache data is valid, providing the first cache data as target data to a sender of the first request.
In one embodiment, the target data providing module includes:
a second request sending unit configured to execute sending a second request for acquiring the target data to a target device when the first cache data does not exist or exists but is invalid, wherein the target device includes a server if the method for managing data is applied to a terminal device; in the case that the method for managing data is applied to a server, the target device comprises a database;
and the second data providing unit is configured to provide data returned by the target device in response to the second request as target data to a sender of the first request, store the data as second cache data of the target data in the local area, and record cache time of the second cache data.
In an embodiment, the first data detection unit is further configured to perform:
responding to the searched target interface, and judging whether the type of the target interface is the interface type of the acquired data;
and responding to the type of the target interface as the interface type of the acquired data, and detecting whether first cache data corresponding to the target data exists locally.
In an embodiment, the cache expiration table includes a modification time of the target data in the database;
the first data judging unit is further configured to perform:
obtaining the caching time of the first caching data;
if the caching time is later than the modification time, determining that the first caching data is valid;
and if the caching time is earlier than or equal to the modification time, determining that the first cache data is invalid.
In an embodiment, in a case that the apparatus for managing data is applied to a server, the apparatus for managing data further includes a dependency relationship table generating module;
the dependency relationship table generation module comprises:
the code file acquisition unit is configured to execute acquisition of a server code file, wherein the code file comprises a first calling relation between each interface and each service layer, a second calling relation between each service layer and each data access layer and a third calling relation between each data access layer and each database table;
a dependency relationship determination unit configured to perform determining a dependency relationship between the respective interface and the respective database table based on the first call relationship, the second call relationship, and the third call relationship;
and the dependency relationship table generation unit is configured to generate an interface dependency relationship table based on the dependency relationship among the plurality of interfaces associated with the same database table.
According to a third aspect of the embodiments of the present disclosure, there is provided an electronic device for managing data, including:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement a method of managing data as described in any of the above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium having instructions that, when executed by a processor of an electronic device for managing data, enable the electronic device for managing data to perform the method for managing data as set forth in any one of the above.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product, which, when executed by a processor of an electronic device for managing data, enables the electronic device for managing data to perform the method for managing data as defined in any one of the above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
the method comprises the steps of responding to target data in a preset interface change database called, inquiring a dependency interface depending on a preset interface from a pre-acquired interface dependency relationship table, wherein the interface dependency relationship table is used for recording dependency relationships among all interfaces, and updating contents corresponding to the dependency interface in a locally stored cache overdue table based on the target data changed by the preset interface to obtain an updated cache overdue table.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a flow chart illustrating a method of managing data in accordance with an exemplary embodiment.
Fig. 2 is a flowchart illustrating a method of managing data according to yet another exemplary embodiment.
Fig. 3 is a flowchart illustrating a method of managing data according to yet another exemplary embodiment.
Fig. 4 is a flowchart illustrating how to detect whether first cache data corresponding to the target data exists locally in response to finding the target interface according to an exemplary embodiment.
Fig. 5 is a flow diagram illustrating how to determine whether the first cached data is valid based on the locally stored cache expiration table, according to an example embodiment.
FIG. 6A is a flowchart illustrating how the interface dependency table is constructed in accordance with an illustrative embodiment.
FIG. 6B is a diagram illustrating various levels of calling relationships in a server code file, according to an example embodiment.
Fig. 7 is a block diagram illustrating an apparatus for managing data according to an example embodiment.
Fig. 8 is a block diagram illustrating an apparatus for managing data according to still another exemplary embodiment.
FIG. 9 is a block diagram illustrating an electronic device that manages data in accordance with an example embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
FIG. 1 is a flow chart illustrating a method of managing data in accordance with an exemplary embodiment. The method for managing data according to the embodiment may be used in a server (e.g., a server or a server cluster formed by multiple servers, etc.), or may also be used in a terminal device (e.g., a smart phone, a tablet computer, or a desktop computer, etc.). As shown in fig. 1, the method comprises the following steps S101-S102:
in step S101, in response to a preset interface being called to change target data in the database, a dependent interface dependent on the preset interface is queried from a pre-obtained interface dependency relationship table.
In this embodiment, after the server calls the preset interface to change the target data in the database, the dependent interface dependent on the preset interface may be queried from the locally stored interface dependency relationship table.
The interface dependency relationship table is used for recording the dependency relationship between the interfaces, the preset interfaces may include interfaces for adding (add), deleting (delete) or modifying (update) data, and the dependent interfaces include an interface for obtaining (get) data.
In step S102, based on the target data of the preset interface change, updating the content corresponding to the dependent interface in the locally stored cache expiration table to obtain an updated cache expiration table.
In an embodiment, after querying a dependent interface dependent on the preset interface from the interface dependency relationship table, the content corresponding to the dependent interface in the cache expiration table may be updated based on target data changed by the preset interface, for example, expiration time (e.g., modification time of corresponding data in a database) of cache data corresponding to the dependent interface in the cache expiration table may be set, and the updated cache expiration table may be further obtained.
For example, when the delete interface is invoked to modify the data in the database (i.e., after the target data in the database is deleted), the expiration time of the cache data corresponding to the get interface dependent on the delete interface in the cache expiration table may be set, for example, the time for modifying the data in the database by the delete interface is set.
As can be seen from the above description, in this embodiment, a dependency interface dependent on a preset interface is queried from an interface dependency relationship table by changing target data in a database in response to calling the preset interface, and based on the target data changed by the preset interface, content corresponding to the dependency interface in a cache expiration table is updated to obtain an updated cache expiration table, so that the cache expiration table stored locally can be timely maintained, and further, data can be subsequently provided to a user based on the cache expiration table, so that user waiting time can be reduced, user experience can be improved, and waste of network resources can be avoided.
Fig. 2 is a flowchart illustrating a method of managing data according to yet another exemplary embodiment. The method for managing data in this embodiment may be used in a server (e.g., a server or a server cluster composed of multiple servers), or may also be used in a terminal device (e.g., a smart phone, a tablet computer, or a desktop computer). As shown in fig. 2, the method comprises the following steps S201 to S203:
in step S201, in response to calling a preset interface to change target data in the database, a dependent interface dependent on the preset interface is queried from a pre-obtained interface dependency relationship table.
In step S202, based on the target data of the preset interface change, the content corresponding to the dependent interface in the locally stored cache expiration table is updated, so as to obtain an updated cache expiration table.
For the explanation and description of steps S201-S202, reference may be made to the above embodiments, which are not described herein again.
In step S203, the updated cache expiration table is sent to the terminal device, so that the terminal device replaces the locally stored cache expiration table of the terminal device with the updated cache expiration table.
In this embodiment, after obtaining the updated cache expiration table, the server may replace the locally stored cache expiration table with the updated cache expiration table, and may send the updated cache expiration table to the terminal device, so as to ensure the validity of the locally stored cache expiration table of the terminal device. On this basis, when the terminal device receives a request for acquiring data by calling a target interface (e.g., a get interface), it may determine whether valid cache data exists locally based on the cache expiration table, and may further provide the locally stored cache data to the data requester under the condition that valid cache data exists.
As can be seen from the above description, in this embodiment, a dependency interface dependent on a preset interface is queried from the interface dependency relationship table in response to calling of target data in a preset interface change database, and based on the target data of the preset interface change, content corresponding to the dependency interface in the cache expiration table is updated to obtain an updated cache expiration table, and then the locally stored cache expiration table is replaced by the updated cache expiration table, and the updated cache expiration table is sent to the terminal device, so that the locally stored cache expiration table can be timely maintained, and the updated cache expiration table can be timely pushed to an associated terminal device, thereby ensuring validity of the cache expiration table in the terminal device.
Fig. 3 is a flowchart illustrating a method of managing data according to yet another exemplary embodiment. The method for managing data according to the embodiment may be used in a server (e.g., a server or a server cluster formed by multiple servers, etc.), or may also be used in a terminal device (e.g., a smart phone, a tablet computer, or a desktop computer, etc.). As shown in fig. 3, the method comprises the following steps S301 to S308:
in step S301, in response to a preset interface being called to change target data in the database, a dependent interface dependent on the preset interface is queried from a pre-obtained interface dependency relationship table.
In step S302, based on the target data of the preset interface change, the content corresponding to the dependent interface in the locally stored cache expiration table is updated, so as to obtain an updated cache expiration table.
For the explanation and explanation of steps S301 to S302, reference may be made to the above embodiments, which are not described herein again.
In step S303, in response to receiving a first request for invoking a target interface to obtain target data, the target interface is looked up from the interface dependency relationship table.
In this embodiment, the server may obtain an interface dependency relationship table in advance, where the interface dependency relationship table is used to record a dependency relationship between interfaces, the preset interface includes an interface for adding, deleting, or modifying data, and the dependency interface includes an interface for obtaining data that depends on the preset interface; furthermore, when a first request for calling a target interface to obtain target data is received, the target interface can be searched from the interface dependency relationship table.
For example, the first request may include detecting a jump triggered by a user, refreshing a page, or re-opening a page, and the like, which is not limited in this embodiment.
The target data may include data such as user information, which is not limited in this embodiment.
In step S304, in response to finding the target interface, detecting whether first cache data corresponding to the target data exists locally: if yes, go to step S305; if not, go to step S307.
Taking a terminal device as an example, when the terminal device receives a first request for calling a target interface to obtain target data, it may detect whether first cache data corresponding to the target data exists locally, and if so, execute step S305; otherwise, step S307 is executed.
In another embodiment, the above-mentioned manner of detecting whether the first cache data corresponding to the target data exists locally may also refer to the following embodiment shown in fig. 4, which is not described in detail herein first.
In step S305, determining whether the first cache data is valid based on the cache expiration table: if yes, go to step S306; if not, go to step S307.
In this embodiment, after detecting that the first cache data corresponding to the target data locally exists, a detection result may be obtained:
if the detection result indicates that the first cache data exists, whether the first cache data is valid may be further determined, for example, whether the first cache data is valid may be determined based on the locally stored cache expiration table.
In an embodiment, the cache expiration table may include information related to locally stored cache data, such as a cache time, an expiration time (e.g., a modification time of corresponding data in the database), and the like, which is not limited in this embodiment. On the basis, when the existence of the first cache data is detected, whether the first cache data is valid can be judged based on the cache expiration table.
Further, when it is determined that the first cache data is valid, step S306 may be performed to provide the first cache data as target data to a sender of the first request (i.e., a requester of the target data).
In another embodiment, if it is detected that the first cached data does not exist locally, or the first cached data exists but the first cached data is invalidated, steps S307 to S308 may be executed.
In another embodiment, the above-mentioned manner of determining whether the first cache data is valid based on the cache expiration table may also be referred to the following embodiment shown in fig. 5, which will not be described in detail herein.
In step S306, the first cache data is provided as target data to the sender of the first request.
In step S307, a second request for acquiring the target data is sent to the target device.
In step S308, data returned by the target device in response to the second request is provided as target data to the sender of the first request, and is stored locally as second cache data of the target data, and the cache time of the second cache data is recorded.
For example, when the first cache data does not exist or the first cache data is invalid, a second request for acquiring the target data may be sent to the target device.
It should be noted that, in a case where the method for managing data of the present embodiment is applied to a terminal device, the target device may include a server. However, in the case that the method for managing data of the present embodiment is applied to a server, the target device may include a database.
On this basis, after sending a second request for acquiring the target data to the target device, the data returned by the target device in response to the second request may be provided as the target data to the sender of the first request. Specifically, data returned by the target device in response to the second request may be received, and the data may be provided to the sender of the first request.
Further, after receiving data returned by the target device in response to the second request, the local first cache data may be updated by using the data, for example, the data returned by the target device may be stored locally as second cache data of the target data, and the cache time of the second cache data is recorded.
As can be seen from the above description, in this embodiment, in response to receiving a first request for calling a target interface to obtain target data, detecting whether first cache data corresponding to the target data exists locally, and when the first cache data exists, determining whether the first cache data is valid based on a cache expiration table stored locally, and when the first cache data is valid, providing the first cache data as the target data to a sender of the first request, so that the first cache data can be provided as the target data to the sender of the first request under the condition that the first cache data of the target data exists locally and the first cache data is valid. Because the data is provided for the data requesting party based on the valid data of the local cache, the data does not need to be requested again from the server or the database, the waiting time of the user can be reduced, the user experience is improved, and the waste of network resources can be avoided.
On the other hand, when the first cache data does not exist or the first cache data is invalid, a second request for acquiring the target data is sent to the target device, and data returned by the target device in response to the second request is provided to a sender of the first request as the target data, so that the second request for acquiring the target data can be sent to the target device under the condition that the data cannot be managed to a data requester based on the locally cached data, indiscriminate re-request of the data to a server or a database can be avoided, and therefore the waiting time of a user can be reduced to a certain extent and waste of network resources can be avoided; in addition, because the data returned by the target device is stored locally as the second cache data of the target data and the cache time of the second cache data is recorded, the local cache data can be updated, and the subsequent judgment of the validity of the second cache data based on the cache time can be realized.
Fig. 4 is a flowchart illustrating how to detect whether first cache data corresponding to the target data exists locally in response to finding the target interface according to an exemplary embodiment. In this embodiment, an example of how to detect whether the first cache data corresponding to the target data exists locally in response to finding the target interface is taken as an example on the basis of the above embodiment. As shown in fig. 4, the step S304 of detecting whether the first cache data corresponding to the target data exists locally in response to finding the target interface may include the following steps S401 to S402:
in step S401, in response to finding the target interface, it is determined whether the type of the target interface is the interface type of the acquired data.
For example, when a first request for calling a target interface to obtain target data is received, the target interface may be looked up from a pre-obtained interface dependency table. It is worth noting that if the target interface exists in the interface dependency table, data can be provided to the data requestor based on the scheme of the disclosed embodiment. Specifically, if the target interface exists in the interface dependency relationship table, the validity of the cache data corresponding to the target interface can be ensured based on each interface in the table, and thus, the data can be provided to the data requester based on the scheme of the embodiment of the present disclosure. In contrast, if the target interface does not exist in the interface dependency relationship table, the validity of the cache data corresponding to the target interface cannot be ensured based on each interface in the table, and thus, the data cannot be provided to the data requester based on the scheme of the embodiment of the present disclosure.
In an embodiment, the interface dependency relationship table may be used to record dependency relationships between interfaces, such as: the interface a depends on the interface B and the interface C (that is, the validity of the cache data corresponding to the interface a is affected by data change of both the interface B and the interface C), and the like.
On this basis, after the target interface is found from the interface dependency relationship table, it can be further determined whether the type of the target interface is the interface type for obtaining data (i.e., get type).
It can be understood that, if the type of the target interface is a get type, the data providing to the data requester based on the locally stored valid cache data can be realized in response to receiving the first request for invoking the interface to obtain the target data. If the type of the target interface is not a get type (e.g., add type, delete type, etc.), it is unable to respond to the first request for invoking the interface to "get" the target data; moreover, the add type or delete type interface is used to modify data rather than to obtain data, and thus cannot pre-cache data locally, and thus cannot provide data to a data requester based on locally stored effective cache data.
In step S402, in response to that the type of the target interface is an interface type of the acquired data, detecting whether first cache data corresponding to the target data exists locally.
In an embodiment, when it is determined that the type of the target interface is the interface type of the acquired data, the step of detecting whether the first cache data corresponding to the target data exists locally may be performed. For a specific implementation manner of this step, reference may be made to the above embodiments, which are not described herein again.
As can be seen from the above description, in this embodiment, by responding to the searched target interface, determining whether the type of the target interface is the interface type for obtaining data, and detecting whether the first cache data corresponding to the target data exists locally when the type of the target interface is the interface type for obtaining data, it can be realized to accurately determine whether the target interface is suitable for the scheme of the embodiment of the present disclosure based on the interface dependency relationship table, so that smooth implementation of the scheme can be ensured, and the implementability of the scheme is improved.
Fig. 5 is a flow diagram illustrating how to determine whether the first cached data is valid based on the locally stored cache expiration table, according to an example embodiment. The present embodiment is exemplarily illustrated on the basis of the foregoing embodiment, by taking an example of how to determine whether the first cache data is valid based on the cache expiration table stored locally.
In this embodiment, the cache expiration table may include modification time of the target data in the database.
As shown in fig. 5, the step of determining whether the first cache data is valid based on the locally stored cache expiration table in step S305 may include the following steps S501 to S504:
in step S501, a buffering time of the first buffered data is obtained.
In step S502, it is determined whether the caching time is later than the modification time of the target data: if yes, go to step S503; if not, go to step S504.
In step S503, it is determined that the first cache data is valid.
In step S504, it is determined that the first cache data has expired.
In an embodiment, after detecting that there is locally first cache data corresponding to the target data, the cache time of the first cache data may be obtained, and the modification time of the target data in the database may be obtained from a locally stored cache expiration table, so that the cache time of the first cache data may be compared with the modification time of the target data:
if the caching time of the first cache data is later than the modification time of the target data, that is, the first cache data is cached after the target data in the database is modified, it can be determined that the first cache data is valid (that is, the first cache data is the same as the target data in the database);
if the caching time of the first cached data is earlier than or equal to the modification time of the target data, that is, the first cached data is cached when the target data in the database is modified or before the target data is modified, it may be determined that the first cached data is invalid (that is, the first cached data is different from the target data in the database).
As can be seen from the above description, in this embodiment, by obtaining the cache time of the first cache data, and determining that the first cache data is valid when the cache time is later than the modification time, and determining that the first cache data is invalid when the cache time is earlier than or equal to the modification time, it can be implemented to accurately determine whether the first cache data is valid, and then, it can be implemented to subsequently provide data to a data requester based on valid data cached locally when the first cache data is valid, and further, it can be avoided to re-request data from a server or a database, which can reduce user waiting time, improve user experience, and avoid waste of network resources.
FIG. 6A is a flowchart illustrating how the interface dependency table is constructed in accordance with an illustrative embodiment. On the basis of the above embodiments, the present embodiment exemplifies how to construct the interface dependency relationship table. As shown in fig. 6A, in the case that the method for managing data is applied to a server, the method for managing data of this embodiment may further include constructing the interface dependency relationship table based on the following steps S601-S603:
in step S601, a server code file is acquired.
In an embodiment, in order to construct the interface dependency relationship table, a server code file may be obtained, where the code file may include a first call relationship between each interface and each Service layer (Service layer), a second call relationship between each Service layer and each Data access layer (Data access object), and a third call relationship between each Data access layer and each database table.
For example, fig. 6B is a diagram illustrating various layers of calling relationships in a server code file, according to an example embodiment. As shown in fig. 6B, a first call relationship exists between the get interface and the Service layer "userservice.getuser", a second call relationship exists between the Service layer "userservice.getuser" and the Dao layer "userdao.user", and a third call relationship exists between the Dao layer "userdao.user" and the database table "userTable".
In step S602, determining a dependency relationship between each interface and each database table based on the first call relationship, the second call relationship, and the third call relationship.
In an embodiment, after the first, second, and third call relationships are determined, the dependency relationship between each interface and each database table may be determined based on the first, second, and third call relationships.
Still taking fig. 6B as an example, it may be determined that the get interface and the database table "userTable" have an association relationship based on a first call relationship between the get interface and the Service layer "userservice.
In step S603, an interface dependency relationship table is generated based on the dependency relationship between the plurality of interfaces associated with the same database table.
In an embodiment, after determining the dependency relationship between the get interface and the database table "userTable", each interface associated with the database table "userTable" may be determined: get interface, add interface and delete interface, and then can determine the dependency relationship between these interfaces based on whether each interface needs to modify the data characteristics. For example, "add interface → get interface" (i.e., a data change of the add interface affects the validity of the cache data corresponding to the get interface) and "delete interface → get interface" (i.e., a data change of the delete interface affects the validity of the cache data corresponding to the get interface). Further, the interface dependency relationship table can be obtained by forming a table based on these dependency relationships.
As can be seen from the above description, in this embodiment, by obtaining a server code file, and determining a dependency relationship between each interface and each database table based on the first call relationship, the second call relationship, and the third call relationship, an interface dependency relationship table can be generated based on a dependency relationship between multiple interfaces associated with the same database table, a basis can be laid for subsequently searching for a target interface based on the interface dependency relationship table, and it can be realized that whether the target interface is applicable to the scheme of the present disclosure embodiment is determined based on the interface dependency relationship table accurately, so that smooth implementation of the scheme can be ensured, and the implementability of the scheme is improved.
Fig. 7 is a block diagram illustrating an apparatus for managing data according to an example embodiment. The method for managing data in this embodiment may be used in a server (e.g., a server or a server cluster composed of multiple servers), or may also be used in a terminal device (e.g., a smart phone, a tablet computer, or a desktop computer). As shown in fig. 7, the apparatus includes: a dependent interface query module 110 and a cache expiration table update module 120, wherein:
a dependent interface query module 110 configured to perform query, in response to a preset interface being called to change target data in a database, for a dependent interface dependent on the preset interface from a pre-acquired interface dependency relationship table, where the interface dependency relationship table is used to record a dependency relationship between interfaces, the preset interface includes an interface for adding, deleting, or modifying data, and the dependent interface includes an interface for acquiring data, which is dependent on the preset interface;
the cache expiration table updating module 120 is configured to execute target data changed based on the preset interface, and update the content corresponding to the dependent interface in the locally stored cache expiration table to obtain an updated cache expiration table.
As can be seen from the above description, in this embodiment, a dependency interface dependent on a preset interface is queried from an interface dependency relationship table by changing target data in a database in response to calling the preset interface, and based on the target data changed by the preset interface, content corresponding to the dependency interface in a cache expiration table is updated to obtain an updated cache expiration table, so that the cache expiration table stored locally can be timely maintained, and further, data can be subsequently provided to a user based on the cache expiration table, so that user waiting time can be reduced, user experience can be improved, and waste of network resources can be avoided.
Fig. 8 is a block diagram illustrating an apparatus for managing data according to still another exemplary embodiment. The method for managing data in this embodiment may be used in a server (e.g., a server or a server cluster composed of multiple servers), or may also be used in a terminal device (e.g., a smart phone, a tablet computer, or a desktop computer). The functions of the dependent interface query module 210 and the cache expired table updating module 220 are the same as those of the dependent interface query module 110 and the cache expired table updating module 120 in the embodiment shown in fig. 7, and are not described herein again. As shown in fig. 8, in a case where the apparatus for managing data is applied to a server, the apparatus for managing data may further include:
a cache expiration table sending module 230 configured to execute sending the updated cache expiration table to a terminal device, so that the terminal device replaces a locally stored cache expiration table of the terminal device with the updated cache expiration table.
In an embodiment, the apparatus for managing data may further include a target data providing module 240;
the target data providing module 240 may include:
a target interface lookup unit 241 configured to perform, in response to receiving a first request for invoking a target interface to obtain target data, lookup the target interface from the interface dependency table;
a first data detection unit 242, configured to perform, in response to finding the target interface, detecting whether first cache data corresponding to the target data exists locally;
a first data determining unit 243 configured to perform, when the first cache data exists, determining whether the first cache data is valid based on the cache expiration table;
a first data providing unit 244 configured to perform providing the first buffered data as target data to a sender of the first request when the first buffered data is valid.
In an embodiment, the target data providing module 240 may further include:
a second request sending unit 245, configured to execute sending a second request for obtaining the target data to a target device when the first cache data does not exist or exists but is invalidated, where the target device includes a server if the method for managing data is applied to a terminal device; in the case that the method for managing data is applied to a server, the target device comprises a database;
a second data providing unit 246, configured to perform providing, as target data, data returned by the target device in response to the second request to a sender of the first request, and store, as second cached data of the target data, in the local, and record a caching time of the second cached data.
In an embodiment, the first data detecting unit 242 may be further configured to perform:
responding to the searched target interface, and judging whether the type of the target interface is the interface type of the acquired data;
and responding to the type of the target interface as the interface type of the acquired data, and detecting whether first cache data corresponding to the target data exists locally.
In one embodiment, the cache expiration table may contain a modification time of the target data in the database;
the first data judging unit is further configured to perform:
obtaining the caching time of the first caching data;
if the caching time is later than the modification time, determining that the first caching data is valid;
and if the caching time is earlier than or equal to the modification time, determining that the first cache data is invalid.
In an embodiment, in a case that the apparatus for managing data is applied to a server, the apparatus for managing data further includes a dependency relationship table generating module 250;
the dependency relationship table generating module 250 may include:
a code file obtaining unit 251, configured to execute obtaining of a code file of a server, where the code file includes a first call relationship between each interface and each service layer, a second call relationship between each service layer and each data access layer, and a third call relationship between each data access layer and each database table;
a dependency relationship determining unit 252 configured to perform determining a dependency relationship between the respective interface and the respective database table based on the first call relationship, the second call relationship, and the third call relationship;
a dependency relationship table generating unit 253 configured to perform generating an interface dependency relationship table based on a dependency relationship between a plurality of interfaces associated by the same database table.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
It should be noted that, all the above-mentioned optional technical solutions may be combined arbitrarily to form the optional embodiments of the present disclosure, and are not described in detail herein.
The embodiment of the apparatus for managing data of the present invention can be applied to network devices. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a device in a logical sense, the device is formed by reading, by a processor of a device in which the device is located, corresponding computer program instructions in a nonvolatile memory into a memory for running, where the computer program is used to execute the method for managing data provided in the embodiment shown in fig. 1 to 6B. From a hardware level, as shown in fig. 9, which is a hardware structure diagram of the device for managing data according to the present invention, besides the processor, the network interface, the memory and the nonvolatile memory shown in fig. 9, the device may also include other hardware, such as a forwarding chip responsible for processing packets, etc.; the device may also be a distributed device in terms of hardware structure, and may include multiple interface cards to facilitate expansion of message processing at the hardware level.
On the other hand, the present application also provides a computer-readable storage medium, which, when a computer program stored in the storage medium is executed by a processor of an electronic device for managing data, enables the electronic device for managing data to perform the method for managing data provided by the embodiment shown in fig. 1 to 6B.
In another aspect, the present application also provides a computer program product, which, when executed by a processor of an electronic device for managing data, enables the electronic device for managing data to execute the method for managing data provided by the embodiments shown in fig. 1 to 6B.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (12)
1. A method for managing data is applied to a terminal device or a server side, and comprises the following steps:
in response to receiving a first request for calling a target interface to acquire target data, searching the target interface from a pre-acquired interface dependency relationship table;
responding to the searched target interface, and detecting whether first cache data corresponding to the target data exists locally;
if the first cache data exists, judging whether the first cache data is valid based on a locally stored cache expiration table;
if the first cache data is valid, the first cache data is used as target data and provided to a sender of the first request;
the method further includes updating the locally stored cache expiration table based on:
responding to a preset interface calling to change data in a database, and inquiring a dependency interface depending on the preset interface from an interface dependency relationship table, wherein the interface dependency relationship table is used for recording the dependency relationship among all interfaces, the preset interface comprises an interface used for adding, deleting or modifying data, and the dependency interface comprises a target interface depending on the preset interface and used for acquiring the target data;
updating data corresponding to the dependent interface in a locally stored cache expiration table based on the data changed by the preset interface to obtain an updated cache expiration table;
the step of detecting whether the first cache data corresponding to the target data exists locally in response to the target interface being found includes:
responding to the searched target interface, and judging whether the type of the target interface is the interface type of the acquired data;
and responding to the type of the target interface as the interface type of the acquired data, and detecting whether first cache data corresponding to the target data exists locally.
2. The method for managing data according to claim 1, wherein in a case where the method for managing data is applied to a server, the method for managing data further comprises:
and sending the updated cache expiration table to the terminal equipment so that the terminal equipment replaces the locally stored cache expiration table of the terminal equipment with the updated cache expiration table.
3. The method for managing data of claim 1, further comprising:
if the first cache data does not exist or the first cache data exists but is invalid, sending a second request for acquiring the target data to target equipment, wherein the target equipment comprises a server under the condition that the method for managing the data is applied to terminal equipment; in the case that the method for managing data is applied to a server, the target device comprises a database;
and providing data returned by the target equipment in response to the second request as target data to a sender of the first request, storing the data serving as second cache data of the target data in the local, and recording the cache time of the second cache data.
4. The method of claim 1, wherein the cache expiration table comprises modification time of the target data in the database;
the step of determining whether the first cache data is valid based on the cache expiration table includes:
obtaining the caching time of the first caching data;
if the caching time is later than the modification time, determining that the first caching data is valid;
and if the caching time is earlier than or equal to the modification time, determining that the first cache data is invalid.
5. The method for managing data according to claim 1, wherein in case that the method for managing data is applied to a server, the method for managing data further comprises constructing the interface dependency table based on the following steps:
acquiring a code file of a server, wherein the code file comprises a first calling relation between each interface and each service layer, a second calling relation between each service layer and each data access layer and a third calling relation between each data access layer and each database table;
determining a dependency relationship between each interface and each database table based on the first call relationship, the second call relationship and the third call relationship;
and generating an interface dependency relationship table based on the dependency relationship among a plurality of interfaces associated with the same database table.
6. An apparatus for managing data, applied to a terminal device or a server, includes: a target data providing module;
the target data providing module includes:
the target interface searching unit is configured to execute searching of a target interface from a pre-acquired interface dependency relationship table in response to receiving a first request for calling the target interface to acquire target data;
the first data detection unit is configured to execute detection of whether first cache data corresponding to the target data exists locally or not in response to the target interface being found;
a first data determination unit configured to perform, when the first cache data exists, determining whether the first cache data is valid based on a locally stored cache expiration table;
a first data providing unit configured to perform, when the first cache data is valid, providing the first cache data as target data to a sender of the first request;
the apparatus also includes updating the locally stored cache expiration table based on: a dependent interface query module configured to perform query of a dependent interface dependent on a preset interface from the interface dependency relationship table in response to a preset interface being called to change data in a database, where the interface dependency relationship table is used to record a dependency relationship between interfaces, the preset interface includes an interface for adding, deleting or modifying data, and the dependent interface includes a target interface dependent on the preset interface and used to obtain the target data;
the cache expired table updating module is configured to execute data changed based on the preset interface, and update data corresponding to the dependent interface in a locally stored cache expired table to obtain an updated cache expired table;
the first data detection unit is further configured to perform:
responding to the searched target interface, and judging whether the type of the target interface is the interface type of the acquired data;
and responding to the type of the target interface as the interface type of the acquired data, and detecting whether first cache data corresponding to the target data exists locally.
7. The apparatus for managing data according to claim 6, wherein in a case where the apparatus for managing data is applied to a server, the apparatus for managing data further comprises:
a cache expiration table sending module configured to send the updated cache expiration table to a terminal device, so that the terminal device replaces a locally stored cache expiration table of the terminal device with the updated cache expiration table.
8. The apparatus for managing data of claim 6, wherein the target data providing module comprises:
a second request sending unit configured to execute sending a second request for acquiring the target data to a target device when the first cache data does not exist or exists but is invalid, wherein the target device includes a server if the method for managing data is applied to a terminal device; under the condition that the method for managing the data is applied to a server, the target equipment comprises a database;
and the second data providing unit is configured to provide data returned by the target device in response to the second request as target data to a sender of the first request, store the data as second cache data of the target data in the local area, and record cache time of the second cache data.
9. The apparatus for managing data according to claim 6, wherein the cache expiration table includes modification time of the target data in the database;
the first data judging unit is further configured to perform:
obtaining the caching time of the first caching data;
if the caching time is later than the modification time, determining that the first caching data is valid;
and if the caching time is earlier than or equal to the modification time, determining that the first cache data is invalid.
10. The apparatus for managing data according to claim 6, wherein in a case where the apparatus for managing data is applied to a server, the apparatus for managing data further comprises a dependency table generation module;
the dependency relationship table generation module comprises:
the code file acquisition unit is configured to execute acquisition of a server code file, wherein the code file comprises a first calling relation between each interface and each service layer, a second calling relation between each service layer and each data access layer and a third calling relation between each data access layer and each database table;
a dependency relationship determination unit configured to perform determining a dependency relationship between the respective interface and the respective database table based on the first call relationship, the second call relationship, and the third call relationship;
and the dependency relationship table generation unit is configured to generate an interface dependency relationship table based on the dependency relationship among the plurality of interfaces associated with the same database table.
11. An electronic device for managing data, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement a method of managing data as claimed in any one of claims 1 to 5.
12. A storage medium in which instructions, when executed by a processor of an electronic device managing data, enable the electronic device managing data to perform a method of managing data as claimed in any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911046015.0A CN110807040B (en) | 2019-10-30 | 2019-10-30 | Method, device, equipment and storage medium for managing data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911046015.0A CN110807040B (en) | 2019-10-30 | 2019-10-30 | Method, device, equipment and storage medium for managing data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110807040A CN110807040A (en) | 2020-02-18 |
| CN110807040B true CN110807040B (en) | 2023-03-24 |
Family
ID=69489584
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911046015.0A Active CN110807040B (en) | 2019-10-30 | 2019-10-30 | Method, device, equipment and storage medium for managing data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110807040B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111880773A (en) * | 2020-07-21 | 2020-11-03 | 北京达佳互联信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2008202360A1 (en) * | 2000-11-29 | 2008-06-19 | Virtual Key Graph | Methods of organizing data and processing queries in a database system, and database system and software product for implementing such methods |
| CN105930492A (en) * | 2016-05-05 | 2016-09-07 | 北京思特奇信息技术股份有限公司 | System and method for loading relational table data into cache |
| CN106453667A (en) * | 2016-12-20 | 2017-02-22 | 北京小米移动软件有限公司 | Method and device for updating cached data |
| CN106815329A (en) * | 2016-12-29 | 2017-06-09 | 网易无尾熊（杭州）科技有限公司 | A kind of data cached update method and device |
| CN107341212A (en) * | 2017-06-26 | 2017-11-10 | 努比亚技术有限公司 | A kind of buffering updating method and equipment |
| CN108536617A (en) * | 2018-03-30 | 2018-09-14 | 网易宝有限公司 | Buffer memory management method, medium, system and electronic equipment |
| CN109379395A (en) * | 2018-08-22 | 2019-02-22 | 中国平安人寿保险股份有限公司 | A kind of interface data buffer setting method and terminal device |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060271542A1 (en) * | 2005-05-25 | 2006-11-30 | Harris Steven T | Clustered object state using logical actions |
| CN100591078C (en) * | 2007-09-28 | 2010-02-17 | 北京金山软件有限公司 | A website buffering method and device |
| US7984123B2 (en) * | 2007-12-10 | 2011-07-19 | Oracle America, Inc. | Method and system for reconfiguring a virtual network path |
| CN103853727B (en) * | 2012-11-29 | 2018-07-31 | 深圳中兴力维技术有限公司 | Improve the method and system of big data quantity query performance |
| CN105373369A (en) * | 2014-08-25 | 2016-03-02 | 北京皮尔布莱尼软件有限公司 | Asynchronous caching method, server and system |
| CN105357293B (en) * | 2015-10-29 | 2019-02-15 | 努比亚技术有限公司 | A kind of update method and server of data buffer storage |
| US20170155735A1 (en) * | 2015-11-27 | 2017-06-01 | Data Accelerator Ltd | Predictively caching requests to reduce effects of latency in networked applications |
| CN105975352B (en) * | 2016-04-28 | 2019-08-30 | 努比亚技术有限公司 | A kind of caching data processing method and server |
| US10681133B2 (en) * | 2016-09-19 | 2020-06-09 | Tego, Inc. | Methods and systems for endpoint device operating system in an asset intelligence platform |
| CN106815287A (en) * | 2016-12-06 | 2017-06-09 | 中国银联股份有限公司 | A kind of buffer memory management method and device |
| CN106777085A (en) * | 2016-12-13 | 2017-05-31 | 东软集团股份有限公司 | A kind of data processing method, device and data query system |
| CN106790629A (en) * | 2017-01-03 | 2017-05-31 | 努比亚技术有限公司 | Data synchronization unit and its realize the method for data syn-chronization, client access system |
| CN107066570A (en) * | 2017-04-07 | 2017-08-18 | 聚好看科技股份有限公司 | Data managing method and device |
| CN110069267A (en) * | 2019-03-15 | 2019-07-30 | 平安普惠企业管理有限公司 | Data-updating method, device, computer equipment and storage medium |
-
2019
- 2019-10-30 CN CN201911046015.0A patent/CN110807040B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2008202360A1 (en) * | 2000-11-29 | 2008-06-19 | Virtual Key Graph | Methods of organizing data and processing queries in a database system, and database system and software product for implementing such methods |
| CN105930492A (en) * | 2016-05-05 | 2016-09-07 | 北京思特奇信息技术股份有限公司 | System and method for loading relational table data into cache |
| CN106453667A (en) * | 2016-12-20 | 2017-02-22 | 北京小米移动软件有限公司 | Method and device for updating cached data |
| CN106815329A (en) * | 2016-12-29 | 2017-06-09 | 网易无尾熊（杭州）科技有限公司 | A kind of data cached update method and device |
| CN107341212A (en) * | 2017-06-26 | 2017-11-10 | 努比亚技术有限公司 | A kind of buffering updating method and equipment |
| CN108536617A (en) * | 2018-03-30 | 2018-09-14 | 网易宝有限公司 | Buffer memory management method, medium, system and electronic equipment |
| CN109379395A (en) * | 2018-08-22 | 2019-02-22 | 中国平安人寿保险股份有限公司 | A kind of interface data buffer setting method and terminal device |
Non-Patent Citations (2)
| Title |
|---|
| Transactional Consistency and Automatic Management in an Application Data Cache;Ports, Dan R. K;《Proceedings of the 9th USENIX Symposium on Operating Systems Design and Implementation, OSDI 2010》;20101031;1-14 * |
| 基于多层缓存池机制的SOA服务协作研究与应用;陈艺丹;《中国优秀硕士学位论文全文数据库 信息科技辑》;20140915;I139-97 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110807040A (en) | 2020-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10491534B2 (en) | Managing resources and entries in tracking information in resource cache components | |
| US20180167444A1 (en) | Content delivery reconciliation | |
| US9451046B2 (en) | Managing CDN registration by a storage provider | |
| US20130067530A1 (en) | DNS-Based Content Routing | |
| US20140143647A1 (en) | Method for improving browser cache by reducing duplicate stored content | |
| US10645192B2 (en) | Identifying content files in a cache using a response-based cache index | |
| US9092731B1 (en) | Determining content item expansion prediction accuracy | |
| CN104714965A (en) | Static resource weight removing method, and static resource management method and device | |
| CN110795395B (en) | File deployment system and file deployment method | |
| CN109634753B (en) | Data processing method, device, terminal and storage medium for switching browser kernels | |
| CN110781149A (en) | Method, device, equipment and storage medium for managing live broadcast room information | |
| US20120259945A1 (en) | System and method for dynamically modifying content based on user expectations | |
| CN109873855A (en) | A kind of resource acquiring method and system based on block chain network | |
| CN110807040B (en) | Method, device, equipment and storage medium for managing data | |
| US20090083217A1 (en) | Web accelerator apparatus, system, and method | |
| WO2019041670A1 (en) | Method, device and system for reducing frequency of functional page requests, and storage medium | |
| CN107634854B (en) | Service data processing method and device | |
| CN105760396B (en) | A kind of webpage loading method and device | |
| CN111125580B (en) | Network resource acquisition method and device, electronic equipment and storage medium | |
| CN108549584B (en) | Method and device for degrading gray level of server side | |
| CN113138943A (en) | Method and device for processing request | |
| CN113360528A (en) | Data query method and device based on multi-level cache | |
| US20240089339A1 (en) | Caching across multiple cloud environments | |
| CN113873302B (en) | Content distribution method, content distribution device, storage medium and electronic equipment | |
| CN111614750B (en) | Data updating method, system, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |