WO2024066001A1

WO2024066001A1 - Data update method and apparatus, storage medium, and electronic apparatus

Info

Publication number: WO2024066001A1
Application number: PCT/CN2022/134785
Authority: WO
Inventors: 唐永将
Original assignee: 海尔优家智能科技（北京）有限公司; 青岛海尔科技有限公司; 海尔智家股份有限公司
Priority date: 2022-09-29
Filing date: 2022-11-28
Publication date: 2024-04-04
Also published as: CN115576966A

Abstract

The present disclosure relates to the technical field of smart home and provides a data update method and apparatus, a storage medium, and an electronic apparatus. The data update method comprises: acquiring an update identifier corresponding to log content of a first database, the update identifier being used for representing whether the log content of the first database is updated or not; when it is determined that the update identifier indicates that first data in the first database changes into second data, acquiring the second data from the first database, wherein the first data and the second data correspond to the same data identifier; and determining the first data stored in a cache, and updating the first data stored in the cache into the second data.

Description

Data updating method, device, storage medium and electronic device

This disclosure claims the priority of the Chinese patent application filed with the China Patent Office on September 29, 2022, with application number 202211203452.0 and invention name “Data update method, device, storage medium and electronic device”, the entire contents of which are incorporated by reference in this disclosure.

Technical Field

The present disclosure relates to the field of smart home technology, and in particular to a data updating method, device, storage medium and electronic device.

Background technique

At present, the process of data access is generally that users concurrently access the data of the business system, and the system returns response information. However, in the high-concurrency business scenarios of the modern Internet, for the large amount of data IO operations generated by irregular high-concurrency access, if these data access requests are directly sent to the database, it is very likely to directly cause the database to crash and become unavailable, thus causing more serious business failures or system abnormalities.

Based on the above problems, we need to introduce a layer of cache between the business system and the database system, so that high-concurrency users can query the cache first when requesting IO operations. However, with the introduction of cache technology, data inconsistency problems will arise, that is, the consistency problem between the database and the cached data after the update.

Therefore, in the related art, there is a technical problem of how to update the cached data to ensure that the data in the database is consistent with the cached data.

In the related art, an effective solution has not yet been proposed for the technical problem of how to update cached data to ensure that the data in the database is consistent with the cached data.

Summary of the invention

The embodiments of the present disclosure provide a data updating method, device, storage medium and electronic device to at least solve the technical problem in the related art of how to update cache data to ensure that the data in the database is consistent with the cache data.

According to an embodiment of the present disclosure, a data updating method is provided, including: obtaining an update identifier corresponding to log content of a first database, the update identifier being used to indicate whether the log content of the first database has been updated; when it is determined that the update identifier indicates that first data in the first database is changed to second data, obtaining the second data from the first database, wherein the first data and the second data correspond to the same data identifier; determining the first data stored in a cache, and updating the first data stored in the cache to the second data, wherein the cache and the first database have pre-synchronized the first data.

According to another embodiment of the embodiments of the present disclosure, a data updating device is also provided, including: a first updating module, configured to obtain an update identifier corresponding to the log content of a first database, wherein the update identifier is used to indicate whether the log content of the first database is updated; an obtaining module, configured to obtain the second data from the first database when it is determined that the update identifier indicates that the first data in the first database is changed to the second data, wherein the first data and the second data correspond to the same data identifier; a second updating module, configured to determine the first data stored in a cache, and update the first data stored in the cache to the second data, wherein the cache and the first database have pre-synchronized the first data.

According to another aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the above data updating method when running.

According to another aspect of the embodiments of the present disclosure, there is also provided an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the data updating method through the computer program.

In an embodiment of the present disclosure, an update identifier corresponding to the log content of the first database is obtained, and the update identifier is used to indicate whether the log content of the first database has been updated; when it is determined that the update identifier indicates that the first data in the first database is changed to, wherein the second data corresponds to the same data identifier as the first data, the second data is obtained from the first database; the first data stored in the cache is determined, and the first data stored in the cache is updated to the second data, wherein the cache and the first database have pre-synchronized the first data.

BRIEF DESCRIPTION OF THE 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 present disclosure.

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

FIG1 is a hardware structure block diagram of a computer terminal of a method for determining an intention instruction according to an embodiment of the present application;

FIG2 is a schematic diagram of a hardware environment of a data updating method according to an embodiment of the present disclosure;

FIG3 is a flow chart of a data updating method according to an embodiment of the present disclosure;

FIG4 is a flow chart of a data updating method according to an embodiment of the present disclosure;

FIG5 is a schematic diagram of a data updating method according to an embodiment of the present disclosure;

FIG6 is a schematic diagram of a method for updating data without caching according to an embodiment of the present disclosure;

FIG7 is a flow chart of a method for updating data with cache according to an embodiment of the present disclosure (I);

FIG8 is a flow chart of a method for updating data with cache according to an embodiment of the present disclosure (II);

FIG9 is a flow chart of a method for updating data with cache according to an embodiment of the present disclosure (III);

FIG. 10 is a structural block diagram of a data updating device according to an embodiment of the present disclosure.

Detailed ways

In order to enable those skilled in the art to better understand the scheme of the present disclosure, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without creative work should fall within the scope of protection of the present disclosure.

It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

The method embodiment provided in the embodiment of the present application can be executed in a computer terminal or a similar computing device. Taking running on a computer terminal as an example, FIG. 1 is a hardware structure block diagram of a computer terminal of a method for determining an intention instruction in an embodiment of the present application. As shown in FIG. 1 , the computer terminal may include one or more (only one is shown in FIG. 1 ) processors 202 (the processor 202 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 204 for storing data. In an exemplary embodiment, the above-mentioned computer terminal may also include a transmission device 106 and an input and output device 108 for communication functions. It can be understood by those of ordinary skill in the art that the structure shown in FIG. 1 is only for illustration, and it does not limit the structure of the above-mentioned computer terminal. For example, the computer terminal may also include more or fewer components than those shown in FIG. 1 , or have different configurations with equivalent functions as shown in FIG. 1 or more functions than those shown in FIG. 1 .

The memory 204 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the determination method of the intention instruction in the embodiment of the present application. The processor 202 executes various functional applications and data processing by running the computer program stored in the memory 204, that is, to implement the above method. The memory 204 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 204 may further include a memory remotely arranged relative to the processor 202, and these remote memories can be connected to the computer terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of a computer terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet wirelessly.

According to one aspect of the embodiments of the present disclosure, a data update method is provided. The data update method is widely used in whole-house intelligent digital control application scenarios such as smart home, smart home, smart home device ecology, and smart house ecology. Optionally, in this embodiment, the above data update method can be applied to a hardware environment composed of a terminal device 102 and a server 104 as shown in Figure 2. As shown in Figure 2, the server 104 is connected to the terminal device 102 through a network, and can be configured to provide services (such as application services, etc.) for the terminal or a client installed on the terminal. A database can be set on the server or independently of the server to provide data storage services for the server 104, and cloud computing and/or edge computing services can be configured on the server or independently of the server to provide data computing services for the server 104.

The above network may include but is not limited to at least one of the following: wired network, wireless network. The above wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the above wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth. The terminal device 102 may be but is not limited to a PC, a mobile phone, a tablet computer, a smart air conditioner, a smart range hood, a smart refrigerator, a smart oven, a smart stove, a smart washing machine, a smart water heater, a smart washing equipment, a smart dishwasher, a smart projection equipment, a smart TV, a smart clothes drying rack, a smart curtain, a smart audio and video, a smart socket, a smart speaker, a smart fresh air equipment, a smart kitchen and bathroom equipment, a smart bathroom equipment, a smart sweeping robot, a smart window cleaning robot, a smart mopping robot, a smart air purification equipment, a smart steamer, a smart microwave oven, a smart kitchen treasure, a smart purifier, a smart water dispenser, a smart door lock, etc.

In this embodiment, a data updating method is provided, which is applied to the above-mentioned computer terminal. FIG3 is a flow chart of the data updating method according to the embodiment of the present disclosure, and the flow chart includes the following steps:

Step S202, obtaining an update flag corresponding to the log content of the first database, wherein the update flag is used to indicate whether the log content of the first database has been updated;

It should be noted that the above update flag may indicate whether the log content of the entire first database is updated, or may indicate whether the log content of specified data in the first database is updated, and the present disclosure does not impose any limitation on this.

Step S204, when it is determined that the update identifier indicates that the first data in the first database is changed to the second data, acquiring the second data from the first database, wherein the first data and the second data correspond to the same data identifier;

The above data identifier can be understood as a unique identifier for identifying a data value. For example, in the form of a key-value pair, the data identifier can be understood as a key, and the data corresponding to the data identifier can be understood as a value. Specifically, for example, taking the data identifier as key A, the first data as data A1, and the second data as A2, the first data corresponding to key A can be expressed as {A, A1}. When the first data is updated to the second data, the second data corresponding to key A can be expressed as {A, A2}.

Step S206: determine the first data stored in the cache, and update the first data stored in the cache to the second data, wherein the cache and the first database have synchronized the first data in advance.

Through the above steps, an update identifier corresponding to the log content of the first database is obtained, and the update identifier is used to indicate whether the log content of the first database has been updated; when it is determined that the update identifier indicates that the first data in the first database is changed to the second data, the second data is obtained from the first database, wherein the first data and the second data correspond to the same data identifier; the first data stored in the cache is determined, and the first data stored in the cache is updated to the second data, wherein the cache and the first database have pre-synchronized the first data, which solves the technical problem of how to update the cache data in the related art to ensure that the data in the database and the cache data are consistent, and further when the cache data is updated, the data in the database and the cache data can be guaranteed to be consistent.

In an exemplary embodiment, after the first data stored in the cache is updated to the second data, the following scheme may further be implemented: when an update confirmation ACK (Acknowledge character) identifier generated when the cache updates the first data to the second data is obtained, a first query instruction is determined according to the ACK identifier; based on the first query instruction, third data is queried from a second database, the second database is a backup database of the first database, and the third data represents backup data of the second data; when it is determined that the second data and the third data are consistent, a notification message indicating that the update is successful is sent to the terminal device.

Through the above embodiment, whether the update is successful can be determined based on whether the third data in the second database is consistent with the second data, thereby improving the accuracy of the data update result.

In one embodiment, if the update confirmation ACK identifier generated when the cache updates the first data to the second data is not obtained, it can be determined that the above-mentioned cache has not been successfully updated, then the cache is re-updated based on a retry mechanism, and a retry message indicating the re-update is sent to the terminal device, wherein the reasons for the update failure may include network disconnection, program error, program failure due to insufficient storage space, etc., but the present disclosure is not limited to this.

Alternatively, when an update confirmation ACK identifier generated when the cache updates the first data to the second data is not obtained, the first data stored in the cache is directly updated to the third data.

In other embodiments, when it is determined that the second data and the third data are inconsistent, the second data in the cache is deleted, and the first data stored in the cache is updated to the third data.

In an exemplary embodiment, in order to better understand how to implement the process of updating the first data stored in the cache to the second data in the above-mentioned step S206, the following steps may be referred to: determining the backup time for backing up the second data of the first database to the second database; generating a delay queue for delaying the cache deletion operation according to the backup time, wherein the delay queue corresponds to a delayed execution time, the start time of the delayed execution time is the change time when the first data in the first database is changed to the second data, and the end time of the delayed execution time is later than the end time of the backup time; updating the first data stored in the cache to the second data according to the delayed execution time corresponding to the delay queue.

In an exemplary embodiment, a technical solution is proposed for the step of updating the first data stored in the cache to the second data according to the delayed execution time corresponding to the delay queue, specifically including: after the delayed execution time, deleting the first data in the cache based on the cache deletion operation; reading third data from the second database, and writing the third data into the cache.

In an exemplary embodiment, a technical solution for determining the backup time of backing up the second data in the first database to the second database is further proposed, and the specific steps include: determining the historical backup time when backing up the second data in the first database to the second database, and determining the backup time based on the historical backup time, including one of the following: setting the historical backup time with the longest usage time as the backup time; setting the historical backup time with the highest usage frequency as the backup time; setting the historical backup time with the latest usage time as the backup time.

Wherein, determining the backup time based on the historical backup time may further include determining the backup time based on an average of a plurality of the historical backup times.

In an exemplary embodiment, optionally, other technical solutions for determining the backup time required for backing up the second data in the first database to the second database are also proposed, specifically including: determining the backup time for backing up the second data in the first database to the second database according to the type of the first database, the type of the second database, and the network status when the second data in the first database is backed up to the second database, so as to determine the backup time for the second data in the first database to the second database according to the backup time.

In an exemplary embodiment, optionally, a scheme for sending a notification message of successful update to a terminal device is also proposed, and the specific schemes include: Scheme 1, when it is determined that the first data cannot be found in the first database, the second database and the cache, sending a notification message indicating a successful update to the terminal device; Scheme 2, when it is determined that the second data is found in both the first database and the cache, sending a notification message indicating a successful update to the terminal device; or, when it is determined that the third data is found in both the second database and the cache, sending a notification message indicating a successful update to the terminal device.

In order to better understand the process of the above data updating method, the implementation method flow of the above data updating is described below in combination with an optional embodiment, but it is not used to limit the technical solution of the embodiment of the present disclosure.

In this embodiment, a data updating method is provided. FIG4 is a flow chart of the data updating method according to the embodiment of the present disclosure. In conjunction with FIG4 , a technical solution is proposed. The specific steps are as follows:

Step S301: Execute the operation of writing data through thread A;

Step S302: executing data update operation through the business system;

Step S303: Database update is successful;

Step S304: subscribing to the log of the database through the message queue;

In one embodiment, after thread A successfully updates the database, it uses a message queue to monitor the database Binlog log and writes the log message into the message queue.

Step S305: when it is determined that the database has been updated according to the subscription message of the message queue, the cache is updated;

Step S306: After the cache is updated successfully, an ACK confirmation message is sent to the message queue;

Step S307: when the cache update fails, re-update the cache based on the retry mechanism;

In one embodiment, the cache module monitors the log messages in the message queue. If an updated log message is detected in the message queue, the consumption operation is immediately performed to update the cache. When it is determined that the cache module has successfully consumed the update log of the message queue, the cache is updated successfully, and an ACK mark is returned to the message queue to confirm the successful consumption. If the cache module fails to successfully consume the update log of the message queue due to network or other reasons, the cache is not updated successfully and the ACK mark cannot be fed back. If the message queue does not receive the ACK mark indicating successful cache consumption, the cache module is controlled to perform the consumption operation again based on the retry mechanism until the ACK mark returned by the cache module is received. Confirm that thread A has completed updating the cache.

Step S309: Execute the data reading operation through thread B;

Step S310: Thread B reads data from the cache;

Step S311: when the cache is empty, read data from the database;

Step S312: updating the cache according to the data read from the database;

Step S313: The cache feeds back to the business system whether the update is successful.

Through the above embodiment, after thread A updates the database, it subscribes to the binlog log of the database, pushes the message related to the binlog log of the database update to the message queue, implements the Binlog log monitored by the message queue, and synchronously updates the cache, so that decoupling work can be achieved without intruding into the business code of the system. In this way, during the operation of the business system, the cache layer can also synchronize the updated data of the database in time to ensure the consistency of the cache and database data.

In one embodiment, Figure 5 is a framework diagram of the data update method according to the embodiment of the present disclosure. As shown in Figure 5, the business system is used to write data to the database, the log subscription middleware (Canal) subscribes to the database to update the binlog log, and writes the Binlog log to the Message Queue. The cache module is set to consume the messages in the message queue to update the cache; the retry mechanism of the Message Queue ensures that the cache consumption message is ultimately successful.

In a high-concurrency business system, the business system usually reads more and writes less, and a one-master-multiple-slave database mode can be adopted, that is, the master database can be set to read and write, and the slave database can only read. This read-write separation method is to disperse the read and write operations of the database to different nodes, which can slightly improve the write performance and greatly improve the read performance. Based on this, this embodiment adopts a high-concurrency thread to initiate the read and write request of the business system, write the master database, read the slave database, thread A performs the database write operation, writes the master database; threads B and C perform the database read operation, read the slave database; wherein, after thread A successfully executes the write to the master database, another asynchronous thread is created to update the cache. When updating the cache, it is necessary to subscribe to the update log of the master database to determine the timing of updating the cache. Based on the purpose of delaying the cache deletion operation of the delay queue, it is necessary to set the delay time of the delay queue message to be greater than the delay time of the master-slave replication. After the master and slave databases synchronously update the data, the cache is deleted based on the delay time of the delay queue message, so that threads B and C read the slave database that has updated the data, and then write the data to the cache, and finally maintain the consistency of the database and the cache.

In other embodiments, Figure 6 is a schematic diagram of a cache-free data update method according to an embodiment of the present disclosure. As shown in Figure 6, a request can also be directly initiated to the business system to query the database to implement a cache-free data update method. However, this method is prone to database crashes or unresponsiveness in high concurrency scenarios.

Optionally, in one embodiment, in order to better understand the process of the above steps S309-S313, this process is described in conjunction with FIG. 7, which is a flow chart of a cached data update method according to an embodiment of the present disclosure (I), and the specific steps are as follows:

Step S601, initiating a data read request;

Step S602, determine whether there is data in the cache; if yes, execute step S606, if no, execute step S603;

Step S603: Load the data to be read from the database;

Step S604, determine whether the data read from the database is empty; if yes, execute step S606, if no, execute step S605;

Step S605, writing the data read from the database into the cache;

Step S606: Return the data read from the cache.

Based on the above embodiment, optionally, in combination with Figure 8, the situation of deleting the cache first and then updating the database is described. As shown in Figure 8, Figure 8 is a flow chart (II) of a data update method with a cache according to an embodiment of the present disclosure. When thread A updates the database, thread A first deletes the cache; then thread B reads the cache. At this time, the cache is empty. If thread B queries the database, thread A has not successfully updated the database at this time, and thread B still reads the old value. Subsequently, thread A successfully updates the database. Thread A updates the cache to the new value. Thread B writes the old value it reads into the cache to overwrite the new value written by thread A last time. The final result is that the cache contains the old value of thread B, while the database is the new value updated by thread A. At this time, the data is inconsistent with the cache.

In this embodiment, if the cache is deleted first, the database has not been successfully updated. At this time, there is no new data in the cache. Data needs to be read from the database and written into the cache. At this time, the data in the cache is old data. In this embodiment, data consistency can be achieved by delayed double deletion. In order to avoid the problem that other threads cannot read data from the cache when updating data, after updating the database, you can sleep for a period of time and then delete the cache again. However, this method cannot accurately estimate the sleep time value, and there may be problems with data inconsistency.

In other embodiments, optionally, the database is updated first in combination with FIG. 9 , which is a flow chart of a data update method with a cache according to an embodiment of the present disclosure (III). The case of deleting the cache is described. As shown in FIG. 9 , after thread A successfully updates the database, when updating the cache, if the cache fails to be deleted or there is no time to delete the cache, the update will fail. If thread B reads the cache, the value in the cache is the old value at this time, and a cache inconsistency result occurs at this time.

In this embodiment, if the database is updated successfully but the cache deletion fails, then the database contains the new value and the cache contains the old value. Subsequent read requests will obtain the old data. Only after the cache expires can the correct value be stored in the database. In this embodiment, after the database is updated successfully, a message can be sent to the message queue. After the client consumes the message queue, the cache is deleted. At this time, the retry mechanism of the queue is used to achieve the final consistency effect. However, after the message queue is introduced in this way, the problem of how to ensure the loss, delay, and timing of the message will also be introduced, which may cause data inconsistency.

Compared with the data update method of Figures 8-9, the embodiment of Figure 4 can obtain the tracking operation of the database in real time by subscribing to the Binlog log updated by the database operation. The message middleware system based on publish-subscribe is decoupled and some functions are implemented without intruding the business system. Write operations are performed through thread A, and the log middleware (Canal) is used to write messages to MQ (Kafka, racketmq) in real time; subscribe to the message queue message through the cache module to update the cache. If it fails, the retry mechanism can be used to repeat the update until the message is successfully updated. The use of the retry mechanism can increase the probability of cache updates, and the cache will not be updated again due to a single failure. In addition, by utilizing the message timing of the message queue, there will be no disorder in updating the cache, and the multi-threaded update and database timing problems can be solved.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present disclosure, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods of each embodiment of the present disclosure.

FIG10 is a structural block diagram of a data updating device according to an embodiment of the present disclosure; as shown in FIG10 , the device comprises:

A first update module 92, configured to obtain an update identifier corresponding to the log content of the first database, wherein the update identifier is used to indicate whether the log content of the first database has been updated;

An acquisition module 94 is configured to acquire the second data from the first database when it is determined that the update identifier indicates that the first data in the first database is changed to the second data, wherein the first data and the second data correspond to the same data identifier;

The second updating module 96 is configured to determine the first data stored in the cache, and update the first data stored in the cache to the second data, wherein the cache and the first database have pre-synchronized the first data.

Through the above-mentioned device, an update identifier corresponding to the log content of the first database is obtained, and the update identifier is used to indicate whether the log content of the first database has been updated; when it is determined that the update identifier indicates that the first data in the first database is changed to the second data, the second data is obtained from the first database, wherein the first data and the second data correspond to the same data identifier; the first data stored in the cache is determined, and the first data stored in the cache is updated to the second data, wherein the cache and the first database have pre-synchronized the first data, which solves the technical problem in the related art of how to update the cache data to ensure that the data in the database and the cache data are consistent, and further when the cache data is updated, it can ensure that the data in the database and the cache data are consistent.

In an exemplary embodiment, the above-mentioned data update device also includes: a determination module, which is configured to determine a first query instruction according to an update confirmation ACK identifier generated when the cache updates the first data to the second data; based on the first query instruction, query third data from a second database, the second database is a backup database of the first database, and the third data represents the backup data of the second data; when it is determined that the second data and the third data are consistent, send a notification message to the terminal device to indicate that the update is successful.

In one embodiment, if the update confirmation ACK identifier generated when the cache updates the first data to the second data is not obtained, it can be determined that the above cache has not been successfully updated, then the cache is re-updated based on a retry mechanism, and a retry message indicating the re-update is sent to the terminal device, wherein the reasons for the update failure may include network disconnection, program error, program failure due to insufficient storage space, etc., but the present disclosure is not limited to this.

In an exemplary embodiment, the second update module 96 is further configured to determine a backup time for backing up the second data of the first database to the second database; generate a delay queue for delaying cache deletion operations according to the backup time, wherein the delay queue corresponds to a delayed execution time, the start time of the delayed execution time is the change time when the first data in the first database is changed to the second data, and the end time of the delayed execution time is later than the end time of the backup time; and update the first data stored in the cache to the second data according to the delayed execution time corresponding to the delay queue.

In an exemplary embodiment, the second update module 96 is further configured to delete the first data in the cache based on the cache deletion operation after the delayed execution time; read the third data from the second database, and write the third data into the cache.

In an exemplary embodiment, the second update module 96 is further configured to determine the historical backup time when backing up the second data in the first database to the second database, and to determine the backup time based on the historical backup time, including one of the following: setting the historical backup time with the longest usage time as the backup time; setting the historical backup time with the highest usage frequency as the backup time; setting the historical backup time with the latest usage time as the backup time.

In an exemplary embodiment, the second update module 96 is further configured to determine a backup time for backing up the second data in the first database to the second database based on the type of the first database, the type of the second database, and the network status when the second data in the first database is backed up to the second database, so as to determine the backup time for backing up the second data in the first database to the second database based on the backup time.

In an exemplary embodiment, the above-mentioned data update device also includes: a sending module, which is configured to send a notification message indicating a successful update to a terminal device when it is determined that the first data cannot be found in the first database, the second database and the cache; or, when it is determined that the second data is found in both the first database and the cache, send a notification message indicating a successful update to the terminal device; or, when it is determined that the third data is found in both the second database and the cache, send a notification message indicating a successful update to the terminal device.

An embodiment of the present disclosure further provides a storage medium, which includes a stored program, wherein the program executes any of the above methods when it is run.

Optionally, in this embodiment, the storage medium may be configured to store program codes for executing the following steps:

S1, obtaining an update identifier corresponding to the log content of the first database, where the update identifier is used to indicate whether the log content of the first database has been updated;

S2, when it is determined that the update identifier indicates that the first data in the first database is changed to the second data, obtaining the second data from the first database, wherein the first data and the second data correspond to the same data identifier;

S3, determining the first data stored in the cache, and updating the first data stored in the cache to the second data, wherein the cache and the first database have synchronized the first data in advance.

An embodiment of the present disclosure further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

Optionally, the electronic device may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.

Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present disclosure can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present disclosure is not limited to any specific combination of hardware and software.

The above is only a preferred embodiment of the present disclosure. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present disclosure. These improvements and modifications should also be regarded as the protection scope of the present disclosure.

Claims

A data updating method, comprising:

Obtaining an update flag corresponding to the log content of the first database, where the update flag is used to indicate whether the log content of the first database has been updated;

When it is determined that the update identifier indicates that the first data in the first database is changed to the second data, acquiring the second data from the first database, wherein the first data and the second data correspond to the same data identifier;

Determine first data stored in a cache, and update the first data stored in the cache to the second data, wherein the cache and the first database have pre-synchronized the first data.
The data updating method according to claim 1, wherein, after updating the first data stored in the cache to the second data, the method further comprises:

In a case where an update confirmation ACK identifier generated when the cache updates the first data to the second data is obtained, determining a first query instruction according to the ACK identifier;

querying third data from a second database based on the first query instruction, where the second database is a backup database of the first database, and the third data represents backup data of the second data;

When it is determined that the second data and the third data are consistent, a notification message indicating that the update is successful is sent to the terminal device.
The data updating method according to claim 1, wherein updating the first data stored in the cache to the second data comprises:

Determining a backup time for backing up the second data of the first database to the second database;

Generate a delay queue for delaying cache deletion operations according to the backup time, wherein the delay queue corresponds to a delay execution time, the start time of the delay execution time is the change time when the first data in the first database is changed to the second data, and the end time of the delay execution time is later than the end time of the backup time;

The first data stored in the cache is updated to the second data according to the delayed execution time corresponding to the delay queue.
The data updating method according to claim 3, wherein updating the first data stored in the cache to the second data according to the delayed execution time corresponding to the delay queue comprises:

After the delayed execution time has elapsed, deleting the first data in the cache based on the cache deletion operation;

Read third data from the second database, and write the third data into the cache.
The data updating method according to claim 3, wherein determining the backup time for backing up the second data of the first database to the second database comprises:

Determining a historical backup time when backing up the second data in the first database to the second database, and determining the backup time based on the historical backup time, includes one of the following:

Setting the longest historical backup time as the backup time;

Setting the most frequently used historical backup time as the backup time;

The historical backup time with the latest usage time is set as the backup time.
The data updating method according to claim 3, wherein determining the backup time required to back up the second data in the first database to the second database comprises:

Determine the backup time for backing up the second data in the first database to the second database according to the type of the first database, the type of the second database and the network status when the second data in the first database is backed up to the second database, so as to determine the backup time for backing up the second data in the first database to the second database.
The data updating method according to claim 2, wherein the method further comprises:

When it is determined that the first data cannot be found in the first database, the second database, and the cache, sending a notification message indicating that the update is successful to the terminal device;

Alternatively, when it is determined that the second data is found in both the first database and the cache, a notification message indicating that the update is successful is sent to the terminal device;

Alternatively, when it is determined that the third data is found in both the second database and the cache, a notification message indicating that the update is successful is sent to the terminal device.
A data updating device, comprising:

A first update module, configured to obtain an update identifier corresponding to the log content of the first database, wherein the update identifier is used to indicate whether the log content of the first database has been updated;

an acquisition module, configured to acquire the second data from the first database when it is determined that the update identifier indicates that the first data in the first database is changed to the second data, wherein the first data and the second data correspond to the same data identifier;

The second updating module is configured to determine the first data stored in the cache and update the first data stored in the cache to the second data, wherein the cache and the first database have pre-synchronized the first data.
According to the data updating device according to claim 8, wherein the determining module is configured to determine a first query instruction according to an update confirmation ACK identifier generated when the cache updates the first data to the second data, upon obtaining the ACK identifier; query third data from a second database based on the first query instruction, the second database is a backup database of the first database, and the third data represents backup data of the second data; and send a notification message indicating that the update is successful to the terminal device when it is determined that the second data and the third data are consistent.
According to the data updating device of claim 8, wherein the second updating module 96 is further configured to determine a backup time for backing up the second data of the first database to the second database; generate a delay queue for delaying the cache deletion operation according to the backup time, wherein the delay queue corresponds to a delayed execution time, the start time of the delayed execution time is the change time when the first data in the first database is changed to the second data, and the end time of the delayed execution time is later than the end time of the backup time; and update the first data stored in the cache to the second data according to the delayed execution time corresponding to the delay queue.
According to the data updating device of claim 10, wherein the second updating module 96 is further configured to delete the first data in the cache based on the cache deletion operation after the delayed execution time has elapsed; read the third data from the second database, and write the third data into the cache.
According to the data updating device according to claim 10, wherein the second updating module 96 is also configured to determine the historical backup time when backing up the second data in the first database to the second database, and determining the backup time based on the historical backup time includes one of the following: setting the historical backup time with the longest usage time as the backup time; setting the historical backup time with the highest usage frequency as the backup time; setting the historical backup time with the latest usage time as the backup time.
According to the data updating device according to claim 10, wherein the second updating module 96 is also configured to determine the backup time when the second data in the first database is backed up to the second database according to the type of the first database, the type of the second database and the network status when the second data in the first database is backed up to the second database, so as to determine the backup time of the second data in the first database to the second database according to the backup time.
According to the data updating device according to claim 9, the data updating device further includes: a sending module, configured to send a notification message indicating a successful update to a terminal device when it is determined that the first data cannot be found in the first database, the second database and the cache; or, when it is determined that the second data is found in both the first database and the cache, send a notification message indicating a successful update to the terminal device; or, when it is determined that the third data is found in both the second database and the cache, send a notification message indicating a successful update to the terminal device.
A computer-readable storage medium, comprising a stored program, wherein the program executes the method described in any one of claims 1 to 7 when executed.
An electronic device comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the method described in any one of claims 1 to 7 through the computer program.