Data processing method, device and storage medium for consistent documents

Abstract

The present invention relates to the field of data synchronization, and discloses a data processing method, device and storage medium for consistent documents. The method includes: the front-end interaction system generates a document registration request based on a user interaction instruction; the document management system receives the document registration request, generates document storage data according to a preset storage structure; stores the document storage data in a preset document database to generate a document record; receives an interaction instruction, and generates a form operation instruction based on the interaction instruction and an interaction management table; the document management system receives the form operation instruction, performs verification and checking processing to generate a checking result; and executes an operation command on the document storage data in the document database according to the checking result and the document record corresponding to the form operation instruction to obtain updated document storage data. In the embodiment of the present invention, data processing transaction consistency of document operations in each system is achieved, effectively solving the technical problem that invalid data accumulation occupies storage resources.

Description

Technical Field

[0001] The present invention relates to the field of data synchronization, and particularly to a method, device, and storage medium for processing data with consistent documents. Background Art

[0002] Currently, the microservices architecture has been widely applied in multiple industries. From Internet companies to traditional industries, more and more enterprises are starting to adopt the microservices architecture to achieve better scalability, flexibility, and maintainability. This architecture model plays an important role in the digital transformation of enterprises. With the popularization of the microservices architecture, a complete ecosystem has gradually formed. From service discovery, configuration management, link tracing to monitoring and alerting, a series of microservices-related tools and services have emerged in an endless stream, providing enterprises with rich choices.

[0003] The integration of low-code platforms has accelerated innovation, enabling teams to create applications more efficiently. By quickly orchestrating service processes through visual tools, developers can significantly shorten the development cycle. However, the increase in the number of microservices has brought management complexity. Under the microservices architecture, the deletion / restore functions of multiple system documents are developed repeatedly. By adding a "deleted or not" field to the database table to mark the data status, each system needs to be implemented separately, which cannot uniformly manage historical data and occupies storage space. Therefore, in view of the accumulation of invalid data due to inconsistent transaction processing of document data between multiple systems under the current microservices architecture, occupying storage resources, a new technology is needed to solve the current problem. Summary of the Invention

[0004] The main objective of the present invention is to solve the technical problem of the accumulation of invalid data due to inconsistent transaction processing of document data between multiple systems under the current microservices architecture, occupying storage resources.

[0005] In the first aspect of the present invention, a method for processing data with consistent documents is provided. The method for processing data with consistent documents is applied to a system for processing data with consistent documents. The system for processing data with consistent documents includes: a document management system and a front-end interaction system. The method for processing data with consistent documents includes:

[0006] Based on a user interaction instruction, the front-end interaction system generates a document registration request and sends the document registration request to the document management system. The document registration request includes: an ID key, a business unique key, and an identification unique key.

[0007] The document management system receives the document registration request and encapsulates the ID key, the business unique key, and the identification unique key according to a preset storage structure to generate document storage data.

[0008] Store the document storage data in a preset document database, generate a document record, and send a successful registration message to the front-end interaction system;

[0009] The front-end interaction system receives the successful registration message and generates an interaction management table based on the successful registration message;

[0010] Receive an interaction instruction for a document in the interaction management table, generate a form operation instruction based on the interaction instruction and the interaction management table, and send the form operation instruction to the document management system, where the form operation instruction includes: an operation ID key, an operation business unique key, an operation identification unique key, and an operation command;

[0011] The document management system receives the form operation instruction, performs a verification and comparison process by corresponding the operation ID key, the operation business unique key, and the operation identification unique key one by one with the ID key, the business unique key, and the identification unique key, and generates a verification result;

[0012] Execute the operation command on the document storage data in the document database according to the verification result and the document record corresponding to the form operation instruction, and obtain the updated document storage data.

[0013] Optionally, in the first implementation manner of the first aspect of the present invention, the process of corresponding the operation ID key, the operation business unique key, and the operation identification unique key one by one with the ID key, the business unique key, and the identification unique key for verification and comparison to generate a verification result includes:

[0014] Perform a consistency verification and comparison process on the operation ID key and the ID key to obtain a first verification result;

[0015] Perform a consistency verification and comparison process on the operation business unique key and the business unique key to obtain a second verification result;

[0016] Perform a consistency verification and comparison process on the operation identification unique key and the identification unique key to obtain a third verification result.

[0017] Optionally, in the second implementation manner of the first aspect of the present invention, the process of executing the operation command on the document storage data in the document database according to the verification result and the document record corresponding to the form operation instruction to obtain the updated document storage data includes:

[0018] When the first verification result is consistent, the second verification result is consistent, and the third verification result is consistent, then execute the operation command on the document storage data in the document database based on the document record corresponding to the form operation instruction to obtain the updated document storage data.

[0019] Optionally, in the third implementation manner of the first aspect of the present invention, the operation of performing the operation command on the document storage data in the document database according to the document record corresponding to the verification result and the form operation instruction to obtain the updated document storage data further includes:

[0020] When the first verification result is inconsistent, the operation command is forced to be skipped, and an alarm message is sent to the front-end interaction system.

[0021] Optionally, in the fourth implementation manner of the first aspect of the present invention, the operation of performing the operation command on the document storage data in the document database according to the document record corresponding to the verification result and the form operation instruction to obtain the updated document storage data further includes:

[0022] When the first verification result is consistent and the second verification result is inconsistent, the business unique key corresponding to the document record and the document storage data is adjusted according to the preset conflict configuration.

[0023] Optionally, in the fifth implementation manner of the first aspect of the present invention, the adjustment process of the business unique key corresponding to the document record and the document storage data according to the preset conflict configuration includes:

[0024] When the conflict configuration is the overwrite setting, the business unique key corresponding to the document record and the document storage data is modified to the operation business unique key;

[0025] When the conflict configuration is the skip setting, the operation command is forced to be skipped, a conflict log of the business unique key is generated, and an information that the business unique key is not overwritten is sent to the front-end interaction system.

[0026] Optionally, in the sixth implementation manner of the first aspect of the present invention, the operation of performing the operation command on the document storage data in the document database according to the document record corresponding to the verification result and the form operation instruction to obtain the updated document storage data further includes:

[0027] When the first verification result is consistent, the second verification result is consistent, and the third verification result is inconsistent, the operation command is forced to be skipped, and a manual intervention request message is sent to the front-end interaction system.

[0028] Optionally, in the seventh implementation manner of the first aspect of the present invention, the operation of performing the operation command on the document storage data in the document database according to the document record corresponding to the verification result and the form operation instruction to obtain the updated document storage data includes:

[0029] When the verification result is consistent, according to the document record corresponding to the form operation instruction, the document storage data in the document database is backed up to a preset NoSQL database to obtain the document storage data backed up by the NoSQL database;

[0030] According to the document record corresponding to the form operation instruction, the operation command is executed on the document storage data in the document database to obtain the updated document storage data.

[0031] The second aspect of the present invention provides a data processing device for consistent documents, including: a memory and at least one processor, wherein instructions are stored in the memory, and the memory and the at least one processor are interconnected by a line; the at least one processor calls the instructions in the memory to enable the data processing device for consistent documents to execute the above-mentioned data processing method for consistent documents.

[0032] The third aspect of the present invention provides a computer-readable storage medium, in which instructions are stored, and when it runs on a computer, it enables the computer to execute the above-mentioned data processing method for consistent documents.

[0033] In the embodiment of the present invention, by setting three keys, namely the ID key, the business unique key, and the identification unique key, to determine the value data of the storage table, the database data in multiple systems is integrated into a form management system. When performing addition, deletion, modification, and query of document data, the three keys are verified. Based on the verification results of the three keys and the registration record corresponding to the form operation instruction, the document storage data in the document database is operated and processed, and the unified data storage and adjustment are realized by using the form management system, achieving the consistency of data processing transactions for document operations in each system, and effectively solving the technical problem that invalid data accumulation occupies storage resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 It is a schematic diagram of an embodiment of the data processing method for consistent documents in the embodiment of the present invention;

[0035] Figure 2 It is a schematic diagram of an embodiment of step 107 of the data processing method for consistent documents in the embodiment of the present invention;

[0036] Figure 3 It is a schematic diagram of an embodiment of the data processing device for consistent documents in the embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0037] The embodiment of the present invention provides a data processing method, device and storage medium for consistent documents.

[0038] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Instead, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the accompanying drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0039] In the description of the embodiments of the present disclosure, the term "including" and its similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. There may also be other explicit and implicit definitions hereinafter.

[0040] For ease of understanding, the specific process of the embodiments of the present invention will be described below. Please refer to Figure 1 , a schematic diagram of an embodiment of the data processing method for consistent documents in the embodiments of the present invention. The data processing method for consistent documents is applied to a data processing system for consistent documents. The data processing system for consistent documents includes: a document management system and a front-end interaction system. The data processing method for consistent documents includes:

[0041] 101. The front-end interaction system generates a document registration request based on a user interaction instruction and sends the document registration request to the document management system. The document registration request includes: an ID key, a business unique key, and an identification unique key.

[0042] In this embodiment, the front-end interaction system can be various microservice systems such as Docker, Dubbo, and SpringCloud microservice architectures. When a user sets the ID key in the front-end interaction system, it is the user ID. When setting the business unique key, it is the business branch object that the current form needs to process. When setting the identification unique key, it is a combination such as the user ID + creation time + physical address of the current device. The ID key, business unique key, and identification unique key are combined to generate a document registration request, and the registration request is sent to the document management system based on a pre-set interface. The interface address can be: / recycle / table / register.

[0043] An example of the document registration request can be as follows:

[0044] ## Request parameter example

[0045] {

[0046] "system": "order_system",

[0047] "table": "t_order",

[0048] "unique_keys":

[0049] {"type": "PRIMARY", "fields": ["id"]}, ## ID key

[0050] {"type": "BUSINESS", "fields": ["order_no"]}, ## Business unique key

[0051] {"type": "COMPOSITE", "fields": ["user_id", "create_time", "mac_id"]} ## Identification unique key

[0052] }。

[0053] 102. The document management system receives the document registration request, and encapsulates the ID key, the business unique key, and the identification unique key according to a preset storage structure to generate document storage data;

[0054] In this embodiment, the document management system receives the document registration request, and based on the pre-set storage structure content, encapsulates the ID key, the business unique key, and the identification unique key of the document registration request, and converts the document data pushed by the document registration request into the JOSN format and writes it into the storage structure to generate document storage data. The specific storage structure form can refer to the following code structure:

[0055] ## Unique key rule storage structure

[0056] CREATE TABLE unique_key_rule (

[0057] rule_id INT PRIMARY KEY,

[0058] system_code VARCHAR(32),

[0059] table_name VARCHAR(64),

[0060] key_type ENUM('PRIMARY', 'BUSINESS', 'COMPOSITE'),

[0061] key_fields JSON-- ##Storage field list );

[0063] The code first sets the document table name, then injects 'PRIMARY', 'BUSINESS', and 'COMPOSITE' into the storage structure identifier, and converts the document data into JOSN format and writes it at the end to generate the document storage data.

[0064] 103. Storing the document storage data in a preset document database, generating a document record, and sending successful registration information to the front-end interactive system;

[0065] In this embodiment, the document storage data is stored in a document database, a document record storing the document storage data is generated, and successful registration information is fed back to the front-end interactive system.

[0066] 104. The front-end interaction system receives the successful registration information, and generates an interaction management table based on the successful registration information;

[0067] In this embodiment, the front-end interactive system receives the successful registration information, and then based on the successful registration information, uses the parameters corresponding to the document registration request as data in the interactive management to generate an interactive management table.

[0068] 105. Receive an interaction instruction for a document in the interaction management table, generate a form operation instruction based on the interaction instruction and the interaction management table, and send the form operation instruction to the document management system, wherein the form operation instruction includes: an operation ID key, an operation business unique key, an operation identification unique key, and an operation command;

[0069] In this embodiment, a user's interactive instruction for a document in the interactive management table is received, such as an operation of adding, deleting, modifying, or checking a document data, a form operation instruction is generated, and the form operation instruction is sent to the document management system. The form operation instruction may contain an operation ID key for confirming the location of the operation form data, an operation business unique key, an operation identification unique key, and an operation command to be performed, and the operation command may be to delete data, add data, modify data, or query data, etc.

[0070] 106. The document management system receives the form operation instruction, performs verification and check processing on the operation ID key, the operation business unique key, and the operation identification unique key in a one-to-one correspondence with the ID key, the business unique key, and the identification unique key, and generates a verification result;

[0071] In this embodiment, the document management system receives the form operation instruction and needs to perform verification and comparison processing on the operation ID key, the operation business unique key, and the operation identification unique key with the ID key, the business unique key, and the identification unique key in the document record one by one to obtain a verification result.

[0072] Specifically, the following specific implementation manners are included in step 106:

[0073] 1061. Perform consistency verification and comparison processing on the operation ID key and the ID key to obtain a first verification result;

[0074] 1062. Perform consistency verification and comparison processing on the operation business unique key and the business unique key to obtain a second verification result;

[0075] 1063. Perform consistency verification and comparison processing on the operation identification unique key and the identification unique key to obtain a third verification result.

[0076] In steps 1061 - 1063, verify one by one according to the operation ID key, the operation business unique key, and the operation identification unique key, and perform comparison in sequence to obtain the first verification result, the second verification result, and the third verification result.

[0077] The specific processing process can refer to the following code:

[0078] ## Check for ID key conflicts

[0079] SELECT COUNT(*) FROM t_order WHERE id = {backup_data.id};

[0080] ## Check for business unique key conflicts

[0081] SELECT COUNT(*) FROM t_order WHERE order_no = {backup_data.order_no};

[0082] ## Check for identification unique key conflicts

[0083] SELECT COUNT(*) FROM t_order WHERE user_id = {backup_data.user_id}

[0084] AND create_time = {backup_data.create_time}.

[0085] 107. Execute the operation command on the document storage data in the document database according to the verification result and the document record corresponding to the form operation instruction, to obtain the updated document storage data.

[0086] In this embodiment, based on the specific situation of the verification result, use the document record corresponding to the form operation instruction to query the document storage data stored in the document database, and then execute the operation command in the database to obtain the updated document storage data.

[0087] In the steps of Embodiment 1061 - 1063, Step 107 includes the following specific implementation manners:

[0088] 1071. When the first verification result is consistent, the second verification result is consistent, and the third verification result is consistent, then based on the document record corresponding to the form operation instruction, execute the operation command on the document storage data in the document database to obtain the updated document storage data.

[0089] In Step 1071, when the first verification result, the second verification result, and the third verification result are all consistent results, directly based on the document record corresponding to the form operation instruction, query the document storage data in the document database, and then execute the operation command on the document storage data to obtain the updated document storage data.

[0090] In the steps of Embodiment 1061 - 1063, Step 107 also includes the following specific implementation manners:

[0091] 1072. When the first verification result is inconsistent, then forcibly skip the operation command and send an alarm message to the front - end interaction system.

[0092] In Step 1072, when the first verification result is inconsistent, directly determine that the user is incorrect, directly forcibly skip the operation command, and send an alarm message to the front - end interaction system to solve the ID key inconsistent conflict result.

[0093] In the steps of Embodiment 1061 - 1063, Step 107 also includes the following specific implementation manners:

[0094] 1073. When the first verification result is consistent and the second verification result is inconsistent, then according to the preset conflict configuration, perform adjustment processing on the business unique key corresponding to the document record and the document storage data.

[0095] In step 1073, when the first verification result is consistent, but the second verification result is inconsistent, there is a conflict configuration. The conflict configuration is an option provided for users to flexibly match business scenarios and usage environments. Based on their own needs, users set the conflict configuration, and based on the conflict configuration, adjust and process the business unique key corresponding to the document record and the document stored data.

[0096] Specifically, step 1073 includes the following specific implementation manners:

[0097] 10731. When the conflict configuration is set to overwrite, modify the business unique key corresponding to the document record and the document stored data to the operation business unique key.

[0098] 10732. When the conflict configuration is set to skip, forcibly skip the operation command, generate a conflict log for the business unique key, and send a message indicating that the business unique key is not overwritten to the front-end interaction system.

[0099] In steps 10731-10732, there are at least two types of conflict configurations. One is the overwrite setting. When the second verification result is inconsistent, overwrite the original business unique key with the operation business unique key to facilitate users to flexibly adjust business objects and migrate data to different business scenarios.

[0100] The other is the skip setting. In this case, no overwriting is performed and the operation command is also forcibly skipped, and a conflict log for the business unique key is generated to facilitate users to adjust the conflict configuration based on the log record, and then a message indicating that the business unique key is not overwritten is sent to the front-end interaction system.

[0101] In steps 1061-1063 of the embodiment, step 107 also includes the following specific implementation manners:

[0102] 1074. When the first verification result is consistent, the second verification result is consistent, and the third verification result is inconsistent, forcibly skip the operation command and send a manual intervention request message to the front-end interaction system.

[0103] In step 1074, when the first verification result is consistent, the second verification result is consistent, and the third verification result is inconsistent, it is necessary to forcibly skip the operation command and send a manual intervention request message to the front-end interaction system. This conflict is relatively comprehensive and cannot be solved by the system itself, and manual intervention is required to solve the problem of the conflict of the unique identification key.

[0104] Specifically, please refer to Figure 2 , Figure 2 which is a schematic diagram of an embodiment of step 107 of the data processing method for consistent documents in the embodiment of the present invention. In step 107, the following steps can be executed:

[0105] 1075. When the verification result is consistent, according to the document record corresponding to the form operation instruction, back up the document storage data in the document database to a preset NoSQL database to obtain the document storage data backed up by the NoSQL database.

[0106] 1076. According to the document record corresponding to the form operation instruction, execute the operation command on the document storage data in the document database to obtain the updated document storage data.

[0107] In steps 1075-1076, when the verification result is considered consistent, first back up the document storage data of the documents to be operated in the document database to the NoSQL database, and then execute the operation command on the document storage data based on the document record corresponding to the form operation instruction. This backup can support users to roll back data and reduce the losses caused by user operation errors. After the user issues a recovery instruction, find the data that needs to be rolled back and restored from the NoSQL database.

[0108] In the embodiment of the present invention, by setting three keys, namely the ID key, the business unique key, and the identification unique key, to determine the value data of the storage table, the database data in multiple systems is integrated into a form management system. When performing addition, deletion, modification, and query of document data, the three keys are verified. Based on the verification results of the three keys and the registration record corresponding to the form operation instruction, the document storage data in the document database is operated and processed. The form management system realizes unified data storage and adjustment, realizes the data processing transaction consistency of document operations in each system, and effectively solves the technical problem that invalid data accumulation occupies storage resources.

[0109] Figure 3 FIG. 14 is a schematic structural diagram of a data processing device for consistent documents provided by an embodiment of the present invention. The data processing device 300 for consistent documents may vary greatly due to configuration or performance differences, and may include one or more processors (central processing units, CPU) 310 (for example, one or more processors) and a memory 320, and one or more storage media 330 for storing application programs 333 or data 332 (for example, one or more mass storage devices). Among them, the memory 320 and the storage media 330 can be transient storage or persistent storage. The program stored in the storage media 330 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the data processing device 300 for consistent documents. Further, the processor 310 can be set to communicate with the storage media 330 and execute a series of instruction operations in the storage media 330 on the data processing device 300 for consistent documents.

[0110] The data processing device 300 based on document consistency may further include one or more power supplies 340, one or more wired or wireless network interfaces 350, one or more input / output interfaces 360, and / or one or more operating systems 331, such as Windows Server, Mac OS X, Unix, Linux, Free BSD, etc. Those skilled in the art can understand that Figure 3 The structure of the data processing device based on document consistency shown does not constitute a limitation on the data processing device based on document consistency, and it may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0111] The present invention also provides a computer-readable storage medium. The computer-readable storage medium can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When the instructions run on a computer, the computer is caused to execute the steps of the data processing method based on document consistency.

[0112] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0113] In addition, although the operations are depicted in a particular order, this should be understood to require that the operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed to achieve the desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features described in the context of separate embodiments can also be implemented in combination in a single implementation. Conversely, the various features described in the context of a single implementation can also be implemented separately or in any suitable sub-combination in multiple implementations.

[0114] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. On the contrary, the specific features and acts described above are merely example forms for implementing the claims.

Claims

1. A document-consistent data processing method, characterized in that: The document-consistent data processing method is applied to a document-consistent data processing system, the document-consistent data processing system includes: a document management system, a front-end interactive system, and the document-consistent data processing method includes: The front-end interactive system generates a document registration request based on the user interaction instruction, and sends the document registration request to the document management system, wherein the document registration request includes: an ID key, a business unique key, and an identification unique key; The document management system receives the document registration request, and encapsulates the ID key, the business unique key, and the identification unique key according to a preset storage structure to generate document storage data; Storing the document storage data in a preset document database, generating a document record, and sending successful registration information to the front-end interactive system; The front-end interaction system receives the successful registration information, and generates an interaction management table based on the successful registration information; Receiving an interaction instruction for a document in the interaction management table, generating a form operation instruction based on the interaction instruction and the interaction management table, and sending the form operation instruction to the document management system, wherein the form operation instruction includes: an operation ID key, an operation business unique key, an operation identification unique key, and an operation command; The document management system receives the form operation instruction, performs verification and check processing on the operation ID key, the operation business unique key, and the operation identification unique key in a one-to-one correspondence with the ID key, the business unique key, and the identification unique key, and generates a verification result; According to the verification result and the document record corresponding to the form operation instruction, the operation command is executed on the document storage data in the document database to obtain updated document storage data; The step of performing verification and checking on the operation ID key, the operation service unique key, and the operation identification unique key in one-to-one correspondence with the ID key, the service unique key, and the identification unique key to generate a verification result includes: Performing a consistency check between the operation ID key and the ID key to obtain a first check result; Performing a consistency check on the operation business unique key and the business unique key to obtain a second check result; Performing a consistency check on the operation identifier unique key and the identifier unique key to obtain a third check result; Wherein, executing the operation command on the document storage data in the document database according to the verification result and the document record corresponding to the form operation instruction to obtain the updated document storage data further includes: When the first checking result is consistent and the second checking result is inconsistent, the document record and the business unique key corresponding to the document storage data are adjusted according to the preset conflict configuration; Wherein, adjusting the business unique key corresponding to the document record and the document storage data according to the preset conflict configuration includes: When the conflict configuration is an overwrite setting, the business unique key corresponding to the document record and the document storage data is modified to the operation business unique key; When the conflict configuration is a skip setting, the operation command is forcibly skipped, a conflict log of the business unique key is generated, and the business unique key non-coverage information is sent to the front-end interactive system.

2. The document-consistent data processing method according to claim 1, characterized in that: The step of executing the operation command on the document storage data in the document database according to the verification result and the document record corresponding to the form operation instruction to obtain the updated document storage data comprises: When the first verification result is consistent, the second verification result is consistent, and the third verification result is consistent, the operation command is executed on the document storage data in the document database based on the document record corresponding to the form operation instruction to obtain updated document storage data.

3. The document-consistent data processing method according to claim 1, characterized in that: The step of executing the operation command on the document storage data in the document database according to the verification result and the document record corresponding to the form operation instruction to obtain updated document storage data further comprises: When the first checking result is inconsistent, the operation command is forcibly skipped and an alarm message is sent to the front-end interactive system.

4. The document-consistent data processing method according to claim 1, characterized in that: The step of executing the operation command on the document storage data in the document database according to the verification result and the document record corresponding to the form operation instruction to obtain updated document storage data further comprises: When the first check result is consistent, the second check result is consistent, and the third check result is inconsistent, the operation command is forcibly skipped and a manual intervention request message is sent to the front-end interactive system.

5. The document-consistent data processing method according to claim 1, characterized in that: The step of executing the operation command on the document storage data in the document database according to the verification result and the document record corresponding to the form operation instruction to obtain the updated document storage data comprises: When the verification result is consistent, the document storage data in the document database is backed up to a preset NoSQL database according to the document record corresponding to the form operation instruction, so as to obtain the document storage data backed up by the NoSQL database; According to the document record corresponding to the form operation instruction, the operation command is executed on the document storage data in the document database to obtain updated document storage data.

6. A document-consistent data processing device, characterized in that: The document-consistent data processing device comprises: a memory and at least one processor, the memory stores instructions, and the memory and the at least one processor are interconnected via a line; The at least one processor calls the instructions in the memory to enable the document-consistent data processing device to execute the document-consistent data processing method according to any one of claims 1 to 5.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, a document-consistent data processing method as described in any one of claims 1 to 5 is implemented.

Images