CN111339200A - Data verification method and data verification system based on database synchronization - Google Patents
Data verification method and data verification system based on database synchronization Download PDFInfo
- Publication number
- CN111339200A CN111339200A CN202010127502.6A CN202010127502A CN111339200A CN 111339200 A CN111339200 A CN 111339200A CN 202010127502 A CN202010127502 A CN 202010127502A CN 111339200 A CN111339200 A CN 111339200A
- Authority
- CN
- China
- Prior art keywords
- data
- server
- verification
- time
- database
- 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.)
- Pending
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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
Abstract
The application provides a data verification method and a data verification system based on database synchronization, which are applicable to the technical field of data verification, and the method comprises the following steps: the method comprises the steps that a third-party verification server is used for sending verification instructions to a main server and a standby server in a fixed period, the main server and the standby server determine data to be verified based on the latest modification time of each piece of data in a main database and the standby database, the verification server determines the data to be compared between the main server and the standby server and sends corresponding query instructions, the main server and the standby server determine the data to be compared according to the query instructions and send the data to the verification server, and finally the verification server compares all the data to judge whether real data synchronization is successful or not. The embodiment of the application greatly reduces the performance influence on the main server, balances the processing task amount of the whole verification and improves the verification efficiency.
Description
Technical Field
The application belongs to the technical field of data verification, and particularly relates to a data verification method and a data verification system based on database synchronization.
Background
The MySQL main database and the backup database are respectively installed in the main server and the backup server, in a high concurrency architecture, synchronization between the main database and the backup database is indispensable, however, due to network delay or operation errors and other reasons, the condition that the main database and the backup database are not synchronized often occurs, in order to ensure normal use of the main server and the backup server, how to effectively perform consistency check on data between the main database and the backup database to judge whether synchronization of the main database and the backup database is successful becomes a problem to be solved urgently.
In order to implement data consistency check of the main and standby databases, the related technology judges whether data consistency check is needed according to a synchronous log recorded by the main and standby servers, when the data consistency check is needed, the main server and the standby server calculate data check values of data stored in respective databases, and the main server compares the two data check values to judge whether the data of the main and standby databases are consistent, so that the data consistency check of the main and standby databases can be implemented, but the performance of the main database is greatly influenced, and the efficiency and the reliability are low.
Disclosure of Invention
In view of this, embodiments of the present application provide a data verification method and a terminal device based on database synchronization, which can solve the problem of low verification efficiency and reliability when data consistency of a primary database and a backup database is verified.
A first aspect of an embodiment of the present application provides a data verification method based on database synchronization, including:
when data in the main database changes, the main server updates a first field value of the data to be the time of the data change;
when the data in the standby database is changed, the standby server updates the first field value of the data to the time of the data change;
the method comprises the steps that a checking server synchronously sends checking instructions to a main server and a standby server at first time intervals;
if the master server receives a verification instruction, first data of a first field value in the master database belonging to a first time period are sent to the verification server;
if the standby server receives a checking instruction, second data of a first field value in the standby database belonging to the first time period are sent to the checking server;
the verification server generates a first query instruction corresponding to the first data and sends the first query instruction to the standby server, and generates a second query instruction corresponding to the second data and sends the second query instruction to the main server;
the standby server sends third data pointed by the first query instruction in the standby database to the verification server;
the master server sends fourth data pointed by the second query instruction in the master database to the verification server;
and if the checking server detects that the first data is the same as the third data and the second data is the same as the fourth data, judging that the synchronization of the main database and the standby database is successful.
A first aspect of an embodiment of the present application provides a data verification system, including: the system comprises a main server, a standby server and a verification server;
the main server is used for updating a first field value of the data to the time of data change when the data in the main database changes;
the standby server is used for updating the first field value of the data to the time of data change when the data in the standby database are changed;
the checking server is used for synchronously sending checking instructions to the main server and the standby server at a first time interval;
the main server is further used for sending first data of a first field value in the main database belonging to a first time period to the verification server if a verification instruction is received;
the standby server is further used for sending second data of the first field value in the standby database belonging to the first time period to the verification server if a verification instruction is received;
the verification server is further used for generating a first query instruction corresponding to the first data and sending the first query instruction to the standby server, and generating a second query instruction corresponding to the second data and sending the second query instruction to the main server;
the standby server is further used for sending third data pointed by the first query instruction in the standby database to the verification server;
the master server is further used for sending fourth data pointed by the second query instruction in the master database to the verification server;
the verification server is further configured to determine that the synchronization between the primary database and the backup database is successful when it is detected that the first data is the same as the third data and the second data is the same as the fourth data.
Compared with the prior art, the embodiment of the application has the advantages that: the method comprises the steps that a third-party verification server is used for sending verification instructions to a main server and a standby server in a fixed period, the main server and the standby server determine data to be verified based on the latest modification time of each piece of data in a main database and the standby database, the verification server determines the data to be compared between the main server and the standby server and sends corresponding query instructions, the main server and the standby server determine the data to be compared according to the query instructions and send the data to the verification server, and finally the verification server compares all the data to judge whether real data synchronization is successful or not. The whole verification process is initiated by the verification server actively and periodically, so that the verification is more accurate and reliable compared with the situation that the main server and the standby server passively determine when to perform verification according to the synchronous log information, meanwhile, in the whole verification process, the verification server completes specific data comparison peer-to-peer operation, and the main server only needs to perform simple data updating moment recording and data searching output operation, so that the performance influence on the main server is greatly reduced, the processing task amount of the whole verification is balanced, and the verification efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic flow chart illustrating an implementation of a data verification method based on database synchronization according to an embodiment of the present application;
fig. 2 is a schematic flow chart illustrating an implementation of a data verification method based on database synchronization according to a second embodiment of the present application;
fig. 3 is a schematic flow chart illustrating an implementation of a data verification method based on database synchronization according to a third embodiment of the present application;
fig. 4 is a system interaction diagram of a data verification system according to a fourth embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
In order to facilitate understanding of the present application, a brief description is first given here, in the related art, since the primary and secondary servers store a synchronization log locally for recording synchronization time corresponding to the primary and secondary databases, and the primary server detects whether the synchronization logs of the two servers are the same at regular time, if the synchronization logs are the same, the primary and secondary databases are considered to be successfully synchronized, and if the synchronization logs are not the same, the primary and secondary servers are required to calculate data check values of data stored in the respective databases, and then the primary server compares the two data check values to determine whether the data of the primary and secondary databases are consistent, but it is found in the actual situation that, on one hand, the synchronization logs are records of historical synchronization conditions, the real-time performance is extremely poor, and the real-time synchronization condition of the primary and secondary databases cannot be truly reflected, and on the other hand, the synchronization logs cannot reflect the data consistency condition of, when the actually selected master and slave database synchronization method is unreliable, the unreliable subsequent consistency check result is directly caused, so that the reliability of the consistency check method based on the synchronization logs is extremely low, in addition, when the synchronization logs are different, the master and slave servers need to calculate the data check value, for a high-concurrency practical application scene, the high-frequency data check value calculation consumes a long time and a large number of resources, which undoubtedly brings a great workload to the master server and influences the performance of the master database, so that the efficiency and the reliability of the related master and slave database data consistency check method are both low, and the performance of the master database is influenced.
In order to improve the efficiency and reliability of the method for checking the data consistency of the main and standby databases, in the embodiment of the application, a checking server of a third party is preset to be responsible for checking the data consistency of the main and standby databases and judging whether the main and standby databases are synchronized successfully or not. The checking server sends a checking instruction to the main and standby servers in a fixed period, the main and standby servers determine data to be checked based on the latest modification time of each piece of data in the main and standby databases, the checking server determines the data to be compared between the main and standby servers and sends a corresponding query instruction, the main and standby servers determine the data to be compared according to the query instruction and send the data to the checking server, and finally the checking server compares all the data to judge whether real data synchronization is successful. The whole verification process is initiated by the verification server actively and periodically, compared with the situation that the main server and the standby server passively determine when to verify according to the synchronous log information, the verified data is updated in real time, the verification result is more accurate and reliable, meanwhile, in the whole verification process, the verification server completes specific data comparison peer-to-peer operation, and the main server only needs to perform simple data updating moment recording and data searching and outputting operation, so that the performance influence on the main server is greatly reduced, the processing task amount of the whole verification is balanced, and the verification efficiency is improved.
Meanwhile, some terms that may be involved in the embodiments of the present application are described as follows:
the first field is a column of fields specially used for recording the latest modification time of each piece of data in the data table, in the embodiment of the application, each data table in the main database and the standby database has a column of first fields, and when the data in the data table changes, the embodiment of the application can record the time when the data changes into the first field value corresponding to the data, so as to realize timely recording and updating of the latest modification time of each piece of data.
And the checking instruction is generated by the checking server at a fixed time interval and synchronously sent to the main server and the standby server, is used for triggering the main server and the standby server to search the data content required to be checked at the time and sends the data content to the checking server. In some embodiments, the verification instruction further includes time data sent by the verified server, so as to help the active/standby server to accurately determine the time period range required to be verified at the time, and thus accurately find out the data content required to be verified.
And if the main server is supposed to send Zhang III personal information data to the check server after receiving the check instruction, the check server generates an inquiry instruction for inquiring Zhang III personal information data and sends the inquiry instruction to the standby server, and the standby server searches Zhang III personal information data in the standby database according to the inquiry instruction after receiving the inquiry instruction and sends the inquiry instruction to the check server for data comparison.
The data change amount refers to a quantized value of a data change condition of the database within a period of time, where a specific quantization method is not limited herein and may be selected or set by a skilled person according to actual requirements, in some embodiments, the total amount of data that changes in the database within a period of time may be counted, and the total amount may be used as the data change amount, and in other embodiments, the total number of times that data changes in the database within a period of time may be counted and used as the data change amount.
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance. It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements in some embodiments of the application, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first instruction may be named a second instruction, and similarly, a second instruction may be named a first instruction, without departing from the scope of the various described embodiments. The first instruction and the second instruction are both instructions, but they are not the same instruction.
The data verification method and the data verification system based on database synchronization in the embodiment of the application are detailed as follows:
fig. 1 shows a flowchart of an implementation of a data verification method based on database synchronization according to an embodiment of the present application, which is detailed as follows:
s101, when data in the main database changes, the main server updates the first field value of the data to the time of the data change.
In this embodiment of the present application, the master server directly updates the first field value of the changed data to the changed time while the data in the master data is changed, so as to implement real-time recording of the data change time, for example, suppose that the data table 1 in the master database is as follows:
TABLE 1
| User name | Sex | Age (age) | First field |
| Zhang three | For male | 25 | 10：00：00 |
| Li four | For male | 25 | 10：00：00 |
| Wangwu tea | Woman | 24 | 10：00：00 |
If Zhang III is 10: 02: 00 is modified to 26, at this time, the main server updates the first field corresponding to zhang triplet, and modifies the value of the first field to 10: 02: 00, modified table 2 is formed as follows:
TABLE 2
| User name | Sex | Age (age) | First field |
| Zhang three | For male | 26 | 10：02：00 |
| Li four | For male | 25 | 10：00：00 |
| Wangwu tea | Woman | 24 | 10：00：00 |
Therefore, the latest modification time of each piece of data can be accurately obtained through the first field value.
S102, when the data in the standby database changes, the standby server updates the first field value of the data to the time of the data change.
The operation of updating the first word value by the standby server is the same as that of the main server, and reference may be specifically made to the description of S101, and only the main server needs to be replaced by the standby server, which is not described herein again.
S103, the checking server synchronously sends checking instructions to the main server and the standby server at a first time interval.
In the embodiment of the present application, the verification server may periodically start the consistency verification on the primary and secondary databases, specifically, the verification server may periodically generate a verification instruction and simultaneously send the generated verification instruction to the primary and secondary servers, where a value of a first time interval for specifically generating the verification instruction is not limited here, and may be set by a technician according to an actual requirement, for example, may be set to any value within 4 to 10 minutes.
And S104, if the main server receives the verification instruction, sending the first data of the first field value in the main database belonging to the first time period to the verification server.
After receiving the check instruction, the main server searches for data that has changed in the first time period from the main database, specifically, determines all data in the main database one by one according to whether the first field value is in the first time period, and if so, determines the data as the first data, thereby completing the search for the first data. The specific starting time and the ending time of the first time period are not limited herein, and may be set by a technician according to actual needs, but it should be understood that, since the embodiment of the present application is an operation of periodic verification, in order to ensure the reliability of the verification result, the first time period may be preferably set while satisfying the following requirements:
1. the total duration of the first time period is greater than or equal to the first time interval, for example, when the first time interval is set to 5 minutes, the total duration of the first time period should be greater than or equal to 5 minutes.
2. In each check, the time difference between the ending time of the first time period and the sending time of the corresponding check instruction should be a fixed value, or the time difference between the ending time of the first time period and the receiving time of the current check instruction should be a fixed value. For example, assume that the verification server: 00: 00, and sending the check instruction once every 5 minutes, wherein the sending time of the corresponding check instruction is respectively 10: 00: 00. 10: 05: 00. 10: 10: 00 …, assuming no network delay between the checking server and the main/standby server, the receiving time of the corresponding checking instruction is completely consistent with the sending time, and on the basis, the ending time of the first time period of the first, second and third checking is 10: 00: 00. 10: 05: 00 and 10: 10: the 00 time difference should be the same, for example, 10: 00: 00. 10: 05: 00 and 10: 10: 00 is the respective termination time, or 09: 59: 00. 10: 04: 00 and 10: 09: and 00 is each termination time.
On the basis of meeting the requirement of the point 2, although the data range of single detection may change along with the change of the first time period, because the embodiment of the present application is a periodic verification process, overall, the embodiment of the present application can achieve continuous and seamless verification on synchronization of the data of the main and standby databases, thereby ensuring accuracy and reliability of the data consistency verification of the main and standby databases.
After the first data changing within the first time period is found out, the main server directly sends the first data to the verification server for subsequent data comparison and verification.
As an embodiment of the present application, the start time and the end time of the first period are set as:
the verification instruction comprises own instruction sending time data, the starting time of the first time period is the instruction sending time of the verification instruction received by the main server last time, and the ending time is the instruction sending time of the verification instruction received by the main server this time.
In this embodiment of the present application, the sending times of two adjacent verification instructions are respectively used as the starting time and the ending time of the first time period, and specifically, in this embodiment of the present application, the quality sending time is stored in the verification instruction sent at the current time, so that the main server can determine the sending time of the instruction of the current time verification instruction each time the main server receives the verification instruction, and similarly, the sending time of the instruction of the verification instruction received at the previous time is also known data.
In the above example, assume that the verification server is from 10: 00: 00, and sending the check instruction once every 5 minutes, wherein the sending time of the corresponding check instruction is respectively 10: 00: 00. 10: 05: 00. 10: 10: 00 …, on this basis, when the master server receives the verification instruction for the second time, it can determine that the corresponding instruction sending time is 10: 05: 00, and meanwhile, knowing that the instruction sending time of the first received verification instruction is 10: 00: 00, and further determining that when the verification instruction is received for the second time, the corresponding first time period is 10: 00: 00-10: 05: time period between 00.
And S105, if the standby server receives the verification instruction, sending second data of the first field value in the standby database belonging to the first time period to the verification server.
The principle of searching for the second data by the standby server is the same as the principle of searching for the first data by the main server, and reference may be specifically made to the description of S104, which is not repeated herein.
It should be noted that, in order to ensure the reliability of the verification of the primary and secondary databases, the first data and the second data should be data that changes in the primary and secondary databases in the same time period, and therefore, the backup server also searches for data that changes in the first time period and sends the changed data in the first time period, but a method for the backup server to specifically determine the start time and the end time of the first time period is not limited herein, and may be set by a technician, including but not limited to, for example, setting a method for determining the start time and the end time that are completely consistent with those of the primary server for the backup server, or sending the data to the backup server after the start time and the end time of the first time period are determined by the primary server.
And S106, verifying the server, generating a first query instruction corresponding to the first data and sending the first query instruction to the standby server, and generating a second query instruction corresponding to the second data and sending the second query instruction to the main server.
After receiving the first data and the second data, the verification server needs to determine various comparison objects of the first data and the second data, for example, assuming that the first data is personal information of zhang san and the second data is personal information of lie san, at this time, the verification server needs to search the personal information of zhang san from the backup database, search the personal information of lie san from the primary database, and compare the personal information with the first data and the second data, respectively, to ensure reliability of consistency verification. Therefore, after receiving the first data and the second data, the verification server in the embodiment of the application may simultaneously generate a corresponding first query instruction and a corresponding second query instruction, and respectively send the first query instruction and the second query instruction to the standby server and the main server to inform the standby server and the main server of the need for data search, where some attribute information related to the first data may be recorded in the first query instruction, and some attribute information related to the second data may be recorded in the second query instruction, so as to ensure the subsequent accurate search of the data of the main and standby databases.
And S107, the standby server sends the third data pointed by the first query instruction in the standby database to the verification server.
After receiving the first query instruction, the standby server searches data in the standby database according to the attribute information recorded in the instruction, for example, if the first query instruction records "zhang san" and "personal information", at this time, the standby server will search the personal information data of zhang san from the standby database, and send the personal information data as third data to the verification server.
And S108, the master server sends the fourth data pointed by the second query instruction in the master database to the verification server.
After receiving the second query instruction, the main server searches the data in the main database according to the attribute information recorded in the instruction, for example, assuming that "liqi" and "personal information" are recorded in the first query instruction, the main server will search the personal information data of liqi from the main database and send the personal information data as fourth data to the verification server.
And S109, if the verification server detects that the first data is the same as the third data and the second data is the same as the fourth data, determining that the synchronization of the main database and the standby database is successful.
After receiving the third data and the fourth data, the verification server compares the first data with the third data, and compares the second data with the fourth data to determine whether the data change conditions of the main and standby databases in the first time period are completely consistent, and if so, it indicates that the main and standby databases are successfully synchronized in the first time period.
On the contrary, if the first data and the third data are different and/or the second data and the fourth data are different, the embodiment of the application can directly determine that the synchronization of the main database and the standby database fails.
In the embodiment of the application, in order to improve the efficiency and reliability of the data consistency check method for the main and standby databases, a check server of a third party is preset to be responsible for performing data consistency check on the main and standby databases and judging whether the main and standby databases are successfully synchronized. The checking server sends a checking instruction to the main and standby servers in a fixed period, the main and standby servers determine data to be checked based on the latest modification time of each piece of data in the main and standby databases, the checking server determines the data to be compared between the main and standby servers and sends a corresponding query instruction, the main and standby servers determine the data to be compared according to the query instruction and send the data to the checking server, and finally the checking server compares all the data to judge whether real data synchronization is successful. The whole verification process is initiated by the verification server actively and periodically, compared with the situation that the main server and the standby server passively determine when to verify according to the synchronous log information, the verified data is updated in real time, the verification result is more accurate and reliable, meanwhile, in the whole verification process, the verification server completes specific data comparison peer-to-peer operation, and the main server only needs to perform simple data updating moment recording and data searching and outputting operation, so that the performance influence on the main server is greatly reduced, the processing task amount of the whole verification is balanced, and the verification efficiency is improved.
As an embodiment of the present application, considering that there is no column of fields specially storing the latest modification time of data in the data tables of the actual primary and secondary databases, in this embodiment of the present application, a column of first fields is inserted into each data table in the primary and secondary databases in advance to ensure the normal execution of the first embodiment of the present application, before S101 and S102, the following operations are performed:
the primary server inserts a column of first fields in each data table within the primary database.
The standby server inserts a column of the first field in each data table in the standby database.
For example, assume the data tables in the original database are as follows in table 3:
TABLE 3
| User name | Sex | Age (age) |
| Zhang three | For male | 25 |
| Li four | For male | 25 |
| Wangwu tea | Woman | 24 |
In this case, the embodiment of the present application inserts a list of first fields on the basis of table 3, so as to form table 4:
TABLE 4
| User name | Sex | Age (age) | First field |
| Zhang three | For male | 25 | |
| Li four | For male | 25 | |
| Wangwu tea | Woman | 24 |
Since it is not possible to know whether each row of data in the table has changed and the time of the change when the first field column is just inserted, after the first field is inserted, all the first field values may be initialized to null values in the embodiment of the present application.
As an embodiment of the present application, on the basis of the foregoing embodiments, in consideration that an operation of deleting data in a primary and secondary database may exist in an actual application, but in order to ensure normal operation of a production environment, in the embodiment of the present application, data is not directly deleted, but a deletion identifier is added to data to be deleted to mark that the data needs to be deleted, and in order to ensure consistency check reliability of the primary and secondary databases, an operation of adding the deletion identifier is also regarded as an operation of changing the data, so that whether the data is subsequently deleted or not may be checked at the same time, where the specific operation includes:
and if the master server receives a first deletion request for the data in the master database, adding a deletion identifier for the data corresponding to the first deletion request, and judging that the data corresponding to the first deletion request is changed.
And if the standby server receives a second deletion request for the data in the standby database, adding a deletion identifier for the data corresponding to the second deletion request, and judging that the data corresponding to the second deletion request is changed.
In this embodiment, corresponding to the operation of adding the deletion identifier, the verification server may compare whether the substantial content of the comparison data is the same or not, and also may compare whether the comparison data has the deletion identifier or not at the same time when performing data comparison, for example, when comparing the first data and the third data, it may also determine whether the first data and the third data have the deletion identifier or not, and only when the data content of the first data and the third data is the same and the deletion identifier has or does not exist at the same time, it may determine that the first data and the third data are the same, or conversely, if only one of the first data and the third data has the deletion identifier, it may directly determine that the first data and the third data are not the same.
As an embodiment of the present application, considering that the throughput of the MySQL database with a high concurrent architecture in a production environment is relatively large, the length of the first interval time greatly affects the workload of the whole data consistency check, if the first interval time is too short, the workload of the data consistency check is directly very large, and if the first interval time is too long, the real-time performance of the check is weak, and it is difficult to ensure the normal operation of the active and standby servers.
In consideration of the fact that in an actual situation, there may still be a certain difference between the actual activity of the user and the requirement for the stability of the database data in different time periods, for example, the data volume of the user may obviously decrease at ordinary night, therefore, in this embodiment, the time interval may be set according to the actual user activity time period and the real-time data throughput condition, and the data verification method is determined, so as to achieve the balance between the verification efficiency and the verification workload each time while ensuring the normal operation of the main and standby servers, as shown in fig. 2, on the basis of the above embodiments, the second embodiment of the present application may adjust the value of the first time interval in real time, and the specific adjustment flow includes:
s201, the master server counts data variation of the master database in a second time period, and obtains an adjustment coefficient corresponding to a first time, wherein the first time is a time for starting to count the data variation, and an end time of the second time period is the first time.
While the above embodiments are performed, the embodiments of the present application will count the corresponding user activity in advance for different time periods, and predict the next data variation and the requirement for the stability of the database according to different user liveness and actual data variation, therefore, a corresponding time interval is selected, for example, the more alive the user is, the higher the stability requirement on the database is, at the moment, the more frequent verification is needed to prevent the possible influence of the asynchronous master database and the standby database on the user, but when the data variation is small, the too frequent verification is not needed actually, which consumes too much resources and causes cost waste, therefore, the activity condition of the user in the next time period can be read, the data variation of the next time period is estimated according to the data variation of the previous time period, and a better time interval is comprehensively set.
Specifically, the embodiment of the present application may analyze the activity of the user in different time periods in advance, calculate a data variation ratio between the time periods to obtain a scaling factor between the different time periods, and set a corresponding adjustment factor between each two adjacent time periods according to the actual scaling factor. The selection of the starting time of the second time period is not limited, and can be set by a technician according to actual requirements, for example, the total duration of the second time period can be set to be 5 hours, and at this time, the corresponding starting time can be determined according to the total duration and the actual situation of the first time.
And S202, the main server processes the data variation according to the adjustment coefficient to obtain a data variation prediction quantity corresponding to a third time period, wherein the starting time of the third time period is the first time or is later than the first time.
After the adjustment coefficient and the data variation are obtained, the data variation is multiplied by the adjustment coefficient, so that a reliable predicted value (i.e., a data variation predicted value) of the data variation of the next third time period can be obtained. The starting time and the ending time of the third time period are not limited herein, and may be set by a technician according to actual needs, for example, the starting time may be set as the first time, and the total duration of the third time period is 5 hours, at which time the corresponding ending time may be calculated.
S203, the main server obtains the data change prediction quantity and the verification interval duration corresponding to the third time period, and sends the verification interval duration to the verification server.
As can be seen from the above description, the user activity and the data variation are both negatively related to the first time interval, so that in the embodiment of the present application, the corresponding check interval duration may be set in advance according to different user activities and data variations, so as to achieve balance between the check efficiency and the check workload each time while ensuring normal operation of the active and standby servers, and meanwhile, since the user activities in different time periods are relatively stable, for example, the activity of a user may significantly decrease in the morning, in the embodiment of the present application, each time period and the corresponding user activity may be mapped in advance, so as to obtain the corresponding check interval duration under different time periods and data variations. On this basis, according to the data change prediction quantity and the specific third time period, the main server in the embodiment of the application can query the corresponding verification interval duration and directly send the verification interval duration to the verification server.
S204, the checking server updates the value of the first time interval to the checking interval duration when receiving the checking interval duration.
After receiving the check interval duration, the check server can directly modify the value of the first time interval into the duration value, so that the first time interval is effectively updated, and the balance between the check efficiency and the check workload of each time can be realized while the normal work of the main and standby servers is ensured at the real-time first time interval.
It should be noted that, in this embodiment of the present application, a specific triggering manner of S201 is not limited, and may be set by a technician according to an actual requirement, in some embodiments, a periodic trigger may be set, at which a time point may be set as a first triggering time, and on the basis, the master server performs the operation of S201 according to a set periodic interval, so as to implement periodic update of the first time interval, in other embodiments, a fixed time point trigger may also be set, at which several triggered time points may be preset by the technician, and when the time points are reached again, the master server performs the operation of S201.
As an embodiment of the present application, considering that the requirements of different actual scenes on the stability of the primary and secondary databases may have a certain difference, the higher the stability requirement is, the higher the requirement on the reliability of the data comparison policy is, but generally, the higher the reliability of the comparison policy corresponding to the comparison workload is, the lower the verification speed is, so as to fully satisfy the different requirements on the verification reliability and speed in different scenes, as shown in fig. 3, on the basis of the second embodiment of the present application, the third embodiment of the present application sets a corresponding appropriate comparison policy in advance according to different scenes, and selects an appropriate comparison policy in the current scene according to the actual user liveness condition and the actual data change prediction amount condition, where the selection process includes:
s301, the main server obtains the user activity corresponding to the third time period, and sends the data change prediction quantity and the user activity to the verification server.
As can be seen by referring to the description of the second embodiment of the present application, in the embodiment of the present application, the user activity of each time period is analyzed in advance, and therefore, at this time, only the user activity corresponding to the third time period needs to be directly read and sent to the verification server, where a specific representation value of the user activity is not limited here and can be set by a technician, for example, in some embodiments, the number of times that the user accesses the primary database may be directly used as the user activity, or the number of users that access the primary database may be used as the user activity.
S302, the verification server updates a corresponding data comparison strategy according to the data change prediction quantity and the user activity, wherein the data comparison strategy is used for detecting whether the first data and the third data are the same and detecting whether the second data and the fourth data are the same.
In the embodiment of the application, requirements for stability and verification speed of the main and standby databases in the current scene are determined based on the user activity and the data change prediction amount, and comparison strategies for some matters are preset, for example, when the data change prediction amount is small, the requirement for the verification speed is not high, at this time, the setting can be performed only by considering the user activity condition, for example, when the user activity is high, the requirement for stability of the main and standby databases is high, at this time, comparison strategies with higher reliability can be set, for example, field-by-field comparison is performed on data, and when the user activity is low, the requirement for stability of the main and standby databases is low, comparison strategies with a lower reliability, for example, the verification strategies based on a hash algorithm, and the like. On this basis, in step S302, an appropriate comparison policy can be selected directly according to the user activity and the data change prediction measure, and then the selected comparison policy is used to replace the old comparison policy, so that the verification server can perform data comparison by using a more reasonable new comparison policy when performing comparison between the first data and the third data and comparison between the second data and the fourth data, and detect whether the data are the same.
Corresponding to the method of the foregoing embodiment, fig. 4 shows a system interaction diagram of the data verification system provided in the fourth embodiment of the present application, and for convenience of explanation, only the part related to the embodiment of the present application is shown. Each execution end server in the data verification system may be an execution subject corresponding to the data verification method based on database synchronization provided in the first embodiment.
Referring to fig. 4, the data verification system includes: the system comprises a main server, a standby server and a verification server.
S401, the master server is used for updating the first field value of the data to the time of data change when the data in the master database changes.
S402, the standby server is used for updating the first field value of the data to the time of the data change when the data in the standby database changes.
And S403, the checking server is used for synchronously sending a checking instruction to the main server and the standby server at a first time interval.
S404, the main server is further configured to, if the verification instruction is received, send the first data of the first field value in the main database belonging to the first time period to the verification server.
S405, the standby server is further configured to send, to the verification server, second data, in which the first field value in the standby database belongs to the first time period, if the verification instruction is received.
And S406, the verification server is further used for generating a first query instruction corresponding to the first data and sending the first query instruction to the standby server, and generating a second query instruction corresponding to the second data and sending the second query instruction to the main server.
And S407, the standby server is further configured to send the third data pointed by the first query instruction in the standby database to the verification server.
S408, the master server is further configured to send fourth data pointed by the second query instruction in the master database to the verification server.
And S409, the verification server is further used for judging that the synchronization of the main database and the standby database is successful when the first data and the third data are detected to be the same and the second data and the fourth data are detected to be the same.
On the basis of the fourth embodiment of the present application, in the fifth embodiment of the present application, the check instruction includes instruction sending time data of the check instruction itself, the starting time of the first time period is an instruction sending time in the check instruction received by the primary server last time, and the ending time is an instruction sending time in the check instruction received by the primary server this time.
On the basis of the fourth embodiment of the present application, in the sixth embodiment of the present application, the master server is further configured to insert a column of the first field in each data table in the master database;
the standby server is also configured to insert a column of the first field in each data table in the standby database.
On the basis of the fourth to sixth embodiments of the present application, in a seventh embodiment of the present application, when a first deletion request for data in a master database is received, adding a deletion identifier to the data corresponding to the first deletion request, and determining that the data corresponding to the first deletion request has changed;
and the standby server is further used for adding a deletion identifier to the data corresponding to the second deletion request and judging that the data corresponding to the second deletion request is changed when receiving the second deletion request for the data in the standby database.
On the basis of the fourth to sixth embodiments of the present application, in an eighth embodiment of the present application, the master server further counts data variation of the master database in a second time period, and obtains an adjustment coefficient corresponding to a first time, where the first time is a time at which the data variation starts to be counted, and an end time of the second time period is the first time;
the main server is further used for processing the data variation according to the adjustment coefficient to obtain a data variation prediction quantity corresponding to a third time period, and the starting time of the third time period is the first time or is later than the first time;
the main server is further used for acquiring the data change prediction quantity and the verification interval duration corresponding to the third time period, and sending the verification interval duration to the verification server;
the verification server is further configured to update the value of the first time interval to the verification interval duration when the verification interval duration is received.
On the basis of the eighth embodiment of the present application, in the ninth embodiment of the present application, the main server is further configured to obtain a user activity corresponding to a third time period, and send the data change prediction amount and the user activity to the verification server;
the verification server is further used for updating a corresponding data comparison strategy according to the data change prediction quantity and the user activity, and the data comparison strategy is used for detecting whether the first data and the third data are the same and detecting whether the second data and the fourth data are the same.
The process of implementing the respective function of each server in the data verification system provided in the embodiment of the present application may specifically refer to the descriptions of the first to third embodiments shown in fig. 1 to 3 and other related embodiments, which are not described herein again.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance. It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements in some embodiments of the application, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first table may be named a second table, and similarly, a second table may be named a first table, without departing from the scope of various described embodiments. The first table and the second table are both tables, but they are not the same table.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
All or part of the flow in the method of the embodiments may be implemented by a computer program, which may be stored in a computer readable storage medium and executed by a processor, to instruct related hardware to implement the steps of the embodiments of the methods. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
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 units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application, and are intended to be included within the scope of the present application.
Claims (10)
1. A data verification method based on database synchronization is characterized by comprising the following steps:
when data in the main database changes, the main server updates a first field value of the data to be the time of the data change;
when the data in the standby database is changed, the standby server updates the first field value of the data to the time of the data change;
the method comprises the steps that a checking server synchronously sends checking instructions to a main server and a standby server at first time intervals;
if the master server receives a verification instruction, first data of a first field value in the master database belonging to a first time period are sent to the verification server;
if the standby server receives a checking instruction, second data of a first field value in the standby database belonging to the first time period are sent to the checking server;
the verification server generates a first query instruction corresponding to the first data and sends the first query instruction to the standby server, and generates a second query instruction corresponding to the second data and sends the second query instruction to the main server;
the standby server sends third data pointed by the first query instruction in the standby database to the verification server;
the master server sends fourth data pointed by the second query instruction in the master database to the verification server;
and if the checking server detects that the first data is the same as the third data and the second data is the same as the fourth data, judging that the synchronization of the main database and the standby database is successful.
2. The database synchronization-based data verification method according to claim 1, wherein the verification instruction includes instruction sending time data of the verification instruction itself, the starting time of the first time period is an instruction sending time of the verification instruction last received by the primary server, and the ending time is an instruction sending time of the verification instruction received by the primary server this time.
3. The database synchronization-based data verification method as claimed in claim, wherein the main server further comprises, before the time of updating the first field value of the data to the data change:
the main server inserts a column of first fields in each data table in the main database;
before the time when the first field value of the data is updated to the data change, the standby server further includes:
the standby server inserts a column of first fields in each data table within the standby database.
4. The database synchronization-based data verification method of any one of claims 1 to 3, further comprising:
if the master server receives a first deletion request for data in the master database, adding a deletion identifier for the data corresponding to the first deletion request, and judging that the data corresponding to the first deletion request is changed;
and if the standby server receives a second deletion request for the data in the standby database, adding a deletion identifier to the data corresponding to the second deletion request, and judging that the data corresponding to the second deletion request is changed.
5. The database synchronization-based data verification method of any one of claims 1 to 3, further comprising:
the master server counts data variation of the master database in a second time period and acquires an adjustment coefficient corresponding to a first time, wherein the first time is the time for starting to count the data variation, and the termination time of the second time period is the first time;
the main server processes the data variation according to the adjustment coefficient to obtain a data variation prediction quantity corresponding to a third time period, wherein the starting time of the third time period is the first time or later than the first time;
the main server acquires the data change prediction quantity and the verification interval duration corresponding to the third time period, and sends the verification interval duration to the verification server;
and the verification server updates the value of the first time interval to the verification interval duration when receiving the verification interval duration.
6. The database synchronization-based data verification method of claim 5, further comprising:
the main server acquires the user activity corresponding to the third time period and sends the data change prediction quantity and the user activity to the verification server;
and the verification server updates a corresponding data comparison strategy according to the data change prediction quantity and the user activity, wherein the data comparison strategy is used for detecting whether the first data is the same as the third data or not and detecting whether the second data is the same as the fourth data or not.
7. A data verification system, comprising: the system comprises a main server, a standby server and a verification server;
the main server is used for updating a first field value of the data to the time of data change when the data in the main database changes;
the standby server is used for updating the first field value of the data to the time of data change when the data in the standby database are changed;
the checking server is used for synchronously sending checking instructions to the main server and the standby server at a first time interval;
the main server is further used for sending first data of a first field value in the main database belonging to a first time period to the verification server if a verification instruction is received;
the standby server is further used for sending second data of the first field value in the standby database belonging to the first time period to the verification server if a verification instruction is received;
the verification server is further used for generating a first query instruction corresponding to the first data and sending the first query instruction to the standby server, and generating a second query instruction corresponding to the second data and sending the second query instruction to the main server;
the standby server is further used for sending third data pointed by the first query instruction in the standby database to the verification server;
the master server is further used for sending fourth data pointed by the second query instruction in the master database to the verification server;
the verification server is further configured to determine that the synchronization between the primary database and the backup database is successful when it is detected that the first data is the same as the third data and the second data is the same as the fourth data.
8. The data verification system of claim 7, further comprising:
the master server is further used for adding a deletion identifier to data corresponding to a first deletion request when the first deletion request for the data in the master database is received, and judging that the data corresponding to the first deletion request is changed;
and the standby server is further used for adding a deletion identifier to the data corresponding to the second deletion request and judging that the data corresponding to the second deletion request is changed when receiving the second deletion request of the data in the standby database.
9. The data verification system of claim 7, further comprising:
the master server is also used for counting the data variation of the master database in a second time period and acquiring an adjusting coefficient corresponding to a first time, wherein the first time is the time for starting counting the data variation, and the end time of the second time period is the first time;
the main server is further configured to process the data variation according to the adjustment coefficient to obtain a data variation prediction amount corresponding to a third time period, where an initial time of the third time period is the first time or is later than the first time;
the main server is further configured to obtain the data change prediction quantity and a verification interval duration corresponding to the third time period, and send the verification interval duration to the verification server;
and the verification server is further used for updating the value of the first time interval to the verification interval duration when the verification interval duration is received.
10. The data verification system of claim 9, further comprising:
the main server is further configured to obtain the user activity corresponding to the third time period, and send the data change prediction amount and the user activity to the verification server;
the verification server is further configured to update a corresponding data comparison strategy according to the data change prediction quantity and the user activity, where the data comparison strategy is used to detect whether the first data is the same as the third data, and detect whether the second data is the same as the fourth data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010127502.6A CN111339200A (en) | 2020-02-28 | 2020-02-28 | Data verification method and data verification system based on database synchronization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010127502.6A CN111339200A (en) | 2020-02-28 | 2020-02-28 | Data verification method and data verification system based on database synchronization |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111339200A true CN111339200A (en) | 2020-06-26 |
Family
ID=71179686
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010127502.6A Pending CN111339200A (en) | 2020-02-28 | 2020-02-28 | Data verification method and data verification system based on database synchronization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111339200A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111835467A (en) * | 2020-07-28 | 2020-10-27 | 中国平安财产保险股份有限公司 | Message sending method, device, computer equipment and storage medium |
| CN112527894A (en) * | 2020-11-27 | 2021-03-19 | 聚好看科技股份有限公司 | Database consistency checking method and system |
| CN112765124A (en) * | 2020-12-30 | 2021-05-07 | 深圳市捷顺科技实业股份有限公司 | Checking method for automatic checking data and server |
| CN113076310A (en) * | 2021-04-30 | 2021-07-06 | 浙江太美医疗科技股份有限公司 | Data verification method, system and computer readable medium for real-time data warehouse |
| CN113110369A (en) * | 2021-03-09 | 2021-07-13 | 广东安朴电力技术有限公司 | Hierarchical control system time synchronization method and communication architecture |
| CN113220779A (en) * | 2021-04-27 | 2021-08-06 | 阿波罗智联(北京)科技有限公司 | Data processing method, device, storage medium and program product |
| CN114513498A (en) * | 2021-12-29 | 2022-05-17 | 广东电网有限责任公司广州供电局 | File transmission checking method and device, computer equipment and storage medium |
| CN112765124B (en) * | 2020-12-30 | 2024-05-17 | 深圳市捷顺科技实业股份有限公司 | Verification method for automatically verifying data and server |
-
2020
- 2020-02-28 CN CN202010127502.6A patent/CN111339200A/en active Pending
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111835467A (en) * | 2020-07-28 | 2020-10-27 | 中国平安财产保险股份有限公司 | Message sending method, device, computer equipment and storage medium |
| CN111835467B (en) * | 2020-07-28 | 2022-03-29 | 中国平安财产保险股份有限公司 | Message sending method, device, computer equipment and storage medium |
| CN112527894A (en) * | 2020-11-27 | 2021-03-19 | 聚好看科技股份有限公司 | Database consistency checking method and system |
| CN112527894B (en) * | 2020-11-27 | 2023-04-14 | 聚好看科技股份有限公司 | Database consistency checking method and system |
| CN112765124A (en) * | 2020-12-30 | 2021-05-07 | 深圳市捷顺科技实业股份有限公司 | Checking method for automatic checking data and server |
| CN112765124B (en) * | 2020-12-30 | 2024-05-17 | 深圳市捷顺科技实业股份有限公司 | Verification method for automatically verifying data and server |
| CN113110369A (en) * | 2021-03-09 | 2021-07-13 | 广东安朴电力技术有限公司 | Hierarchical control system time synchronization method and communication architecture |
| CN113110369B (en) * | 2021-03-09 | 2022-09-09 | 广东安朴电力技术有限公司 | Hierarchical control system time synchronization method and communication system |
| CN113220779A (en) * | 2021-04-27 | 2021-08-06 | 阿波罗智联(北京)科技有限公司 | Data processing method, device, storage medium and program product |
| CN113076310A (en) * | 2021-04-30 | 2021-07-06 | 浙江太美医疗科技股份有限公司 | Data verification method, system and computer readable medium for real-time data warehouse |
| CN114513498A (en) * | 2021-12-29 | 2022-05-17 | 广东电网有限责任公司广州供电局 | File transmission checking method and device, computer equipment and storage medium |
| CN114513498B (en) * | 2021-12-29 | 2024-04-02 | 广东电网有限责任公司广州供电局 | File transmission verification method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111339200A (en) | Data verification method and data verification system based on database synchronization | |
| US11379461B2 (en) | Multi-master architectures for distributed databases | |
| CN111464615B (en) | Request processing method, device, server and storage medium | |
| US20140101225A1 (en) | Consistency-based service-level agreements in cloud storage environments | |
| WO2019057193A1 (en) | Data deletion method and distributed storage system | |
| CN106021468A (en) | Updating method and system for distributed caches and local caches | |
| CN112016030B (en) | Message pushing method, device, server and computer storage medium | |
| CN111159219B (en) | Data management method, device, server and storage medium | |
| US20150234883A1 (en) | Method and system for retrieving real-time information | |
| CN111562889B (en) | Data processing method, device, system and storage medium | |
| CN111767297B (en) | Big data processing method, device, equipment and medium | |
| WO2020228287A1 (en) | Iot-mq message storage method, device, computer apparatus and storage medium | |
| CN111327684A (en) | Quota management method and device of distributed object storage system | |
| CN106549983B (en) | Database access method, terminal and server | |
| CN111522870A (en) | Database access method, middleware and readable storage medium | |
| CN114205455B (en) | Application positioning processing method and device | |
| US7058773B1 (en) | System and method for managing data in a distributed system | |
| CN113672652A (en) | Data access method, device, equipment and storage medium | |
| CN113760640A (en) | Monitoring log processing method, device, equipment and storage medium | |
| CN114253938A (en) | Data management method, data management device, and storage medium | |
| CN111814001B (en) | Method and device for feeding back information | |
| CN108959546B (en) | Distributed key value storage system data weak consistency measuring method based on reverse order pair | |
| CN113746868B (en) | Method, device, equipment and medium for optimizing server performance | |
| WO2022222665A1 (en) | Request recognition method and apparatus, and device and storage medium | |
| CN116595025B (en) | Dynamic updating method, terminal and medium of vector tile |
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 |