Data synchronization method and device, storage medium and computer program

Abstract

The invention relates to a data synchronization method and device, a storage medium and a computer program. The method comprises the steps that whether a service instance data table of a source end is changed or not is detected; in response to the change of the service instance data table of the source end, obtaining change information, and analyzing the change information to obtain a data table identifier; according to the data table identifier, searching an interface corresponding to the data table identifier in preset synchronous configuration information to obtain a target push interface; and calling the target push interface, and synchronizing the change data in the service instance data table of the source end to the target end according to the change information. When the service instance data table of the source end is changed, the data table identifier of the changed data is obtained, the target push interface corresponding to the data table identifier is searched according to the preset synchronization configuration information, and the target push interface is called to synchronize the data from the source end, so that a synchronization program does not need to be developed for each service instance, and the data synchronization efficiency is improved. The efficiency of synchronizing the data from the source end to the target end is effectively improved.

Description

Technical Field

[0001] The present disclosure relates to the technical field of data synchronization, and in particular to a data synchronization method, apparatus, device, storage medium and computer program. Background Art

[0002] With the continuous development of the Industrial Internet, the service instance data of different cloud management platforms need to be temporarily unified. Since different cloud management platforms have different types of databases, such as MySQL, Oracle, SQLServer and other databases, and the table structure of each service instance database is also different, how to aggregate and store various service instance data from different sources according to the reception standards of the Industrial Internet platform is a problem faced by the Industrial Internet platform during its construction.

[0003] In the existing technology, customized development is performed for the synchronization of each service instance. This method has poor adaptability. When a new service instance is connected for synchronization, a full process of development and construction is required. Summary of the invention

[0004] The present disclosure provides a data synchronization method, device, storage medium and computer program.

[0005] In a first aspect, the present disclosure provides a data synchronization method, comprising:

[0006] Check whether there are any changes in the service instance data table on the source side;

[0007] In response to a change in the service instance data table of the source end, acquiring change information, parsing the change information, and obtaining a data table identifier;

[0008] According to the data table identifier, searching for an interface corresponding to the data table identifier in the preset synchronization configuration information to obtain a target push interface;

[0009] The target push interface is called to synchronize the changed data in the service instance data table of the source end to the target end according to the changed information.

[0010] In one embodiment, the step of obtaining change information in response to a change in the service instance data table of the source end, parsing the change information, and obtaining a data table identifier includes:

[0011] In response to a change in the service instance data table of the source end, obtaining the change information, and sending the change information to a message queue;

[0012] The change information in the message queue is obtained, the change information is parsed, and the data table identifier is obtained.

[0013] In one embodiment, the steps of acquiring the change information in the message queue, parsing the change information, and obtaining the data table identifier include:

[0014] Using the data synchronization service to detect whether there is change information in the message queue;

[0015] In response to the data synchronization service detecting that there is change information in the message queue, the data synchronization service is used to obtain the change information in the message queue, parse the change information, and obtain the data table identifier.

[0016] In one embodiment, the step of detecting whether there is a change in the service instance data table at the source end includes:

[0017] Use the data collection service to detect whether there are any changes in the service instance data table at the source end;

[0018] The step of obtaining the change information in response to the change of the service instance data table of the source end and sending the change information to the message queue comprises:

[0019] In response to the change of the service instance data table of the source end, the change information is obtained by using the data collection service, and the change information is sent to the message queue.

[0020] In one embodiment, the step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information includes:

[0021] Calling the target push interface to obtain the change data from the service instance data table of the source end according to the change information;

[0022] The changed data is parsed to obtain parsed data without a format, the parsed data is assembled according to a preset data receiving format to obtain data to be synchronized, and the data to be synchronized is written into the service instance data table of the target end.

[0023] In one embodiment, the step of searching for an interface corresponding to the data table identifier in preset synchronization configuration information according to the data table identifier to obtain a target push interface includes:

[0024] According to the data table identifier, searching for an interface corresponding to the data table identifier in the preset synchronization configuration information, obtaining a target push interface and an interface address, an interface calling method, and an interface authentication parameter of the target push interface;

[0025] The step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information includes:

[0026] The target push interface is called using the interface address of the target push interface, the interface calling method and the authentication parameters of the interface, and the changed data in the service instance data table of the source end is synchronized to the target end according to the change information.

[0027] In one embodiment, after the step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information, the step further includes:

[0028] Detect whether the changed data in the service instance data table of the source end is synchronized to the target end;

[0029] When the changed data in the service instance data table of the source end fails to be synchronized to the target end, synchronization failure information indicating the synchronization failure is fed back to the message service;

[0030] In response to the synchronization failure information, the target push interface is called to resynchronize the changed data in the service instance data table of the source end to the target end according to the change information.

[0031] In a second aspect, the present disclosure provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method described in the above aspect.

[0032] In a third aspect, the present disclosure provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the method described in the above aspects when executed by a processor.

[0033] In a fourth aspect, the present disclosure provides a computer program product, including a computer program, which implements the steps of the method described in the above aspects when executed by a processor.

[0034] The present invention provides a data synchronization method, device, storage medium and computer program. When a service instance data table at a source end changes, the data table identifier of the changed data is obtained, a target push interface corresponding to the data table identifier is searched according to preset synchronization configuration information, and the target push interface is called to synchronize data from the source end. In this way, there is no need to develop a synchronization program for each service instance, which effectively improves the efficiency of synchronizing data from the source end to the target end. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The present disclosure will be described in more detail below based on embodiments and with reference to the accompanying drawings:

[0036] Figure 1 A flowchart of a data synchronization method provided by an embodiment of the present disclosure;

[0037] Figure 2 A schematic diagram of a synchronization architecture of a data synchronization method provided in one embodiment of the present disclosure.

[0038] In the drawings, the same reference numerals are used for the same components, and the drawings are not drawn to scale. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the technical solution of the present disclosure, and to fully understand and implement how the present disclosure applies technical means to solve technical problems and achieve the corresponding technical effects, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only embodiments of a part of the present disclosure, not all of the embodiments. The embodiments of the present disclosure and the various features in the embodiments can be combined with each other without conflict, and the technical solutions formed are all within the scope of protection of the present disclosure. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work should fall within the scope of protection of the present disclosure.

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

[0041] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0042] It is worth mentioning that the data synchronization method in each embodiment of the present application can be applied to data synchronization between different computer devices and different databases, and can also be applied to data synchronization between the cloud management platform and the industrial Internet platform on the industrial Internet platform. In the following embodiments, the data synchronization method is applied to data synchronization between the cloud management platform and the industrial Internet platform on the industrial Internet platform as an embodiment to further illustrate.

[0043] Embodiment 1

[0044] Figure 1 The following is a flow chart of a data synchronization method provided by an embodiment of the present disclosure. Figure 1 As shown, a data synchronization method includes:

[0045] Step 110: Check whether there is any change in the service instance data table at the source end.

[0046] In this embodiment, the source end is a cloud management platform, that is, a cloud management platform. In this embodiment, the addition, deletion, modification, insertion and other operations of the service instance data table of the source end are monitored in real time. When the above operations occur, the service instance data table is changed.

[0047] Step 120: In response to the change of the service instance data table at the source end, obtain change information, parse the change information, and obtain a data table identifier.

[0048] In this embodiment, when there is a change in the service instance data table at the source end, the change information is obtained, and the data table identifier in the change information is obtained. Specifically, the change information carries the data table identifier, which can be a data table name, or a data table code, number, etc., for distinguishing and identifying different data tables.

[0049] It is worth mentioning that the change information is only used to record or carry the data table identifier and the changed event, and the change information does not carry the changed data. Since the amount of change data is generally large, this step only needs to obtain the change information, not the change data.

[0050] Step 130: According to the data table identifier, search for an interface corresponding to the data table identifier in the preset synchronization configuration information to obtain a target push interface.

[0051] In this embodiment, the preset synchronization configuration information records the corresponding relationship between each data table identifier and the interface at the source end, such as Figure 2As shown, each data table of the source database corresponds to an interface, which is used to synchronize data from the source to the target. The target push interface is one of the multiple interfaces, which is an interface selected according to the data table identifier. In this embodiment, according to the correspondence between the source data table identifiers and the interfaces recorded in the preset synchronization configuration information, the interface corresponding to the data table identifier is found, which is the target push interface.

[0052] Step 140: Call the target push interface to synchronize the changed data in the service instance data table of the source end to the target end according to the changed information.

[0053] In this embodiment, the target end is an industrial Internet platform. Specifically, in this embodiment, the target push interface is called to synchronize the change data in the service instance data table of the source end to the service instance summary table of the industrial Internet platform according to the change information.

[0054] In this embodiment, the target push interface is called, and the target push interface is used to transmit the changed data, and the changed data is transmitted from the service instance data table of the source end to the target end, thereby realizing data synchronization. In this embodiment, in the process of calling the interface, synchronization is performed according to the change information, that is, the change information is transmitted to the target push interface. The change information carries the data table identifier. Therefore, the target push interface can determine the data table in the service instance data table that has changed according to the data table identifier, and obtain the changed data from the data table. In addition, the change information can also record the amount of the changed data and the position of the changed data in the data table, including the starting position and the ending position. In this way, the target push interface can accurately obtain the changed data from the service instance data table and then synchronize.

[0055] In the above embodiment, when the service instance data table at the source end changes, the data table identifier of the changed data is obtained, the target push interface corresponding to the data table identifier is searched according to the preset synchronization configuration information, and the target push interface is called to synchronize data from the source end. Whenever the data of a service instance needs to be synchronized, the corresponding relationship and mapping relationship between the data table identifier and the interface of the corresponding service instance data table only need to be added to the preset synchronization configuration information to realize the synchronization configuration. In this way, there is no need to develop a synchronization program for each service instance, which effectively improves the efficiency of synchronizing data from the source end to the target end.

[0056] Embodiment 2

[0057] Based on the above embodiment, in this embodiment, the step of obtaining change information in response to the change of the service instance data table of the source end, parsing the change information, and obtaining the data table identifier includes:

[0058] In response to a change in the service instance data table of the source end, obtaining the change information, and sending the change information to a message queue;

[0059] The change information in the message queue is obtained, the change information is parsed, and the data table identifier is obtained.

[0060] In this embodiment, the change information of the change data in the service instance data table of the source end is sent to a message queue, and the data table identifier is used as the identifier type of this message. It is worth mentioning that, as described in the above embodiment, the change information carries the data table identifier and records the event of the change, but the change information itself is not equivalent to the change data. Due to the large amount of data of the change data, it cannot be directly sent to the message queue, nor can it be stored in the message queue. The change information can be understood as a message. Therefore, in this embodiment, only the change information of the event of recording the change of the service instance data table of the source end is sent to the message queue, and the first-in-first-out principle of the message queue is used to obtain the change information entering the message queue in sequence according to the time of entering the message queue, and the change information is parsed to obtain the data table identifier. By storing the change information through the message queue, the change of the service instance data table at the source end can be decoupled from the subsequent data synchronization of the source end and the target end, the stability and reliability of data synchronization can be improved, and the asynchronous processing of data change and data synchronization can be realized. In addition, the change of the service instance data table at the source end is more accurate and easy to monitor.

[0061] Embodiment 3

[0062] Based on the above embodiment, in this embodiment, the steps of acquiring the change information in the message queue, parsing the change information, and obtaining the data table identifier include:

[0063] Using the data synchronization service to detect whether there is change information in the message queue;

[0064] In response to the data synchronization service detecting that there is change information in the message queue, the data synchronization service is used to obtain the change information in the message queue, parse the change information, and obtain the data table identifier.

[0065] In this embodiment, the data synchronization service is a synchronization process or service on the server. The data synchronization service acts as a consumer of the message queue. The data synchronization service monitors the change information entering the message queue in real time. When new change information is detected in the message queue, the newly entered change information in the message queue is obtained, and the message in the message queue is consumed. After obtaining the change information, the change information is parsed to obtain the data table identifier. In this embodiment, using the data synchronization service to consume and monitor the message queue can effectively avoid the omission of change information, maintain data synchronization, and improve the reliability of data synchronization.

[0066] Embodiment 4

[0067] Based on the above embodiments, in this embodiment, the step of detecting whether there is a change in the service instance data table of the source end includes: using a data acquisition service to detect whether there is a change in the service instance data table of the source end; the step of obtaining the change information in response to the change of the service instance data table of the source end, and sending the change information to the message queue includes: in response to the change of the service instance data table of the source end, using the data acquisition service to obtain the change information, and sending the change information to the message queue.

[0068] In this embodiment, the data acquisition service is a data acquisition process or service on the server, and the data acquisition service acts as a producer of the message queue. In this embodiment, the data acquisition service monitors in real time whether the service instance data table at the source end has changed. When the data in the service instance data table at the source end changes, the change information is generated and sent to the message queue. In this embodiment, the data acquisition server acts as a producer. When the service instance data table at the source end changes, the message of the message queue is generated and sent to the message queue. In this way, the service instance data table at the source end can be effectively monitored to avoid missing data changes.

[0069] Embodiment 5

[0070] Based on the above embodiment, in this embodiment, the step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information includes:

[0071] Calling the target push interface to obtain the change data from the service instance data table of the source end according to the change information;

[0072] The changed data is parsed to obtain parsed data without a format, the parsed data is assembled according to a preset data receiving format to obtain data to be synchronized, and the data to be synchronized is written into the service instance data table of the target end.

[0073] In this embodiment, the target push interface is first called to obtain the change data from the service instance data table of the source end, and then the change data is parsed to obtain data without format, that is, parsed data, and then the parsed data is assembled according to the preset data receiving format to obtain synchronized data. It is worth mentioning that the preset data receiving format is the data receiving format of the industrial Internet platform. In this way, the data is converted into a format that matches the data receiving format of the industrial Internet platform, and the synchronized data is written to the service instance data table of the industrial Internet platform. In this way, by transforming the format of the data, the data can be made more compatible, thereby effectively improving the efficiency of data writing.

[0074] Embodiment 6

[0075] Based on the above embodiment, in this embodiment, the step of searching for an interface corresponding to the data table identifier in the preset synchronization configuration information according to the data table identifier to obtain a target push interface includes:

[0076] According to the data table identifier, searching for an interface corresponding to the data table identifier in the preset synchronization configuration information, obtaining a target push interface and an interface address, an interface calling method, and an interface authentication parameter of the target push interface;

[0077] The step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information includes:

[0078] The target push interface is called using the interface address of the target push interface, the interface calling method and the authentication parameters of the interface, and the changed data in the service instance data table of the source end is synchronized to the target end according to the change information.

[0079] In this embodiment, the preset synchronization configuration information also records the interface address, interface calling method and interface authentication parameters of each interface. Among them, the interface address includes the network address, port number, etc., and the interface calling method includes HTTP / HTTPS (Hypertext Transfer Protocol) request method, RPC (Remote Procedure Call) method, database interface, message queue, shared memory, etc. The authentication parameters of the interface include the authentication account and password of the interface. In this way, according to the data table identifier, the target push interface corresponding to the data table identifier can be found in the preset synchronization configuration information, as well as the interface address, interface calling method and interface authentication parameters of the target push interface of the target push interface. Based on the determined interface address, interface calling method and interface authentication parameters, the target push interface is called, so that the source end can be quickly accessed, the change data is obtained from the service instance data table of the source end, and the change data is synchronized to the target end.

[0080] Embodiment 7

[0081] Based on the above embodiment, in this embodiment, after the step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information, the following steps are further included:

[0082] Detect whether the changed data in the service instance data table of the source end is synchronized to the target end;

[0083] When the changed data in the service instance data table of the source end is successfully synchronized to the target end, a synchronization success message indicating the successful synchronization is fed back to the message service;

[0084] When the changed data in the service instance data table of the source end fails to be synchronized to the target end, synchronization failure information indicating the synchronization failure is fed back to the message service;

[0085] In response to the synchronization failure information, the target push interface is called to resynchronize the changed data in the service instance data table of the source end to the target end according to the change information.

[0086] In this embodiment, after executing data synchronization from the source end to the target end, the result of data synchronization is fed back to the message service. When the synchronization is successful, the message service receives the synchronization success information. When the synchronization fails, the message synchronization responds to the synchronization failure information, calls the target push interface again, re-synchronizes the data, and retries the sending process to avoid data synchronization loss.

[0087] Embodiment 8

[0088] Based on the above embodiments, this embodiment provides an application example.

[0089] In this embodiment, first, a synchronization configuration page is established on the industrial Internet platform, and the configuration information is recorded in the synchronization configuration page. The configuration information is the synchronization configuration information in the above embodiments. The configuration information includes the name of the source cloud management platform data table that needs to be connected for synchronization, the target synchronization interface pushed to the industrial Internet platform, and the calling method of the interface and the authentication account password. When it is necessary to monitor a service instance data table of the cloud management platform and synchronize the data to the industrial Internet platform, a new synchronization configuration is added to the synchronization configuration page. The name of the source table data that needs to be monitored for synchronization is configured, and the target interface for pushing data to the industrial Internet platform is configured (this interface needs to be developed separately according to data processing requirements).

[0090] After the data synchronization configuration is completed, the data acquisition service monitors the service instance data table that needs to be synchronized at the source end (i.e., the cloud management platform). When the service instance data table data is added, deleted, or modified, the data change information is sent to a message queue, and the data table name is used as the identification type of this message. At the same time, a data synchronization service is built. The data synchronization service consumes and monitors the change table data in the message queue (i.e., obtains the change data information from the message queue in real time). After obtaining the change data information, it parses the message identification type name (i.e., the synchronized data table name) in the data, and then uses the identification type name of the current message to query the target push interface of the synchronization configuration in the data synchronization configuration, and calls the interface according to the configured interface address, interface call method, and interface authentication method, and transmits the information of the changed data to the interface. After the interface receives the changed data information, it parses the changed data information and assembles it according to the data receiving format of the industrial Internet platform, and then writes the assembled data into the service instance summary table of the industrial Internet platform. At this point, the incremental synchronization of a piece of data from the cloud management platform to the industrial Internet platform is completed. When the service instance data tables of other cloud management platforms need to be synchronized, you only need to develop a data synchronization target push interface, and then create a synchronization configuration item in the synchronization configuration page to complete the synchronization configuration access of a source service instance data table and initiate the synchronization function.

[0091] The specific process is as follows:

[0092] (1) Build a synchronization configuration page to realize the mapping relationship between the data table name of the source cloud management platform and the target synchronization interface (target push interface) to be pushed;

[0093] (2) Build a data monitoring service. Use the data monitoring service to connect to the source cloud management platform database and monitor the tables that need to be synchronized. When the data in the table that needs to be synchronized is changed, the data change information is sent to the message queue in the form of a message.

[0094] (3) Build a data synchronization service. The data synchronization service consumes data change messages in the message queue in real time and extracts the table name of the data change from the change message, such as Figure 2 As shown, query the data synchronization interface corresponding to this table in the synchronization configuration according to the table name, initiate a call to the synchronization interface, and transmit the data change message to the data synchronization interface for data synchronization and other business processing. After the data synchronization interface is called successfully, the result of the successful synchronization is fed back to the message service, that is, the synchronization of a piece of data is completed; if the synchronization process fails, the result of the failure is fed back to the message service so that the message service can retry the sending process to ensure that data synchronization is not lost.

[0095] The method of this embodiment can realize real-time incremental synchronization of table data of different data sources according to the data receiving standard of the industrial Internet platform through simple synchronization configuration and synchronization interface development, thereby eliminating the need for customized development of synchronization of table data of each data source.

[0096] Embodiment 9

[0097] In this embodiment, a data synchronization device is provided, including:

[0098] Change detection module, used to detect whether there are changes in the service instance data table on the source side;

[0099] A table identifier acquisition module, configured to respond to a change in the service instance data table of the source end, acquire change information, parse the change information, and obtain a data table identifier;

[0100] A target push interface obtaining module is used to search for an interface corresponding to the data table identifier in the preset synchronization configuration information according to the data table identifier, and obtain the target push interface;

[0101] The synchronization module is used to call the target push interface and synchronize the changed data in the service instance data table of the source end to the target end according to the changed information.

[0102] This embodiment also includes other modules or sub-modules corresponding to each of the above method embodiments, which are used to execute the steps or corresponding sub-steps of the methods in the above embodiments, and are not listed and described one by one in this embodiment.

[0103] Embodiment 10

[0104] On the basis of the above embodiments, this embodiment provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method described in the above embodiments.

[0105] In some implementations of this embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method described in the above embodiment are implemented.

[0106] In some implementations of this embodiment, a computer program product is provided, including a computer program, which implements the steps of the method described in the above embodiment when executed by a processor.

[0107] The processor may include, but is not limited to, one or more processors or microprocessors. Each processor may be an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a controller, a microcontroller, a microprocessor or other electronic components to execute the method in the above embodiments.

[0108] Computer-readable storage media can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Computer-readable storage media may include, but are not limited to, for example, random access memory (RAM), read-only memory (ROM), flash memory, EPROM memory, EEPROM memory, registers, computer storage media (such as hard disks, floppy disks, solid-state drives, removable disks, Blu-ray disks, etc.).

[0109] The computer-readable storage medium may also store at least one computer executable program, such as a computer-readable instruction. The computer-readable storage medium includes, but is not limited to, for example, a volatile memory and / or a non-volatile memory. The volatile memory may include, for example, a random access memory (RAM) and / or a cache memory (cache), etc. The computer-readable storage medium may include, for example, a read-only memory (ROM), a hard disk, a flash memory, etc. For example, a non-transitory computer-readable storage medium may be connected to a computing device such as a computer, and then, when the computing device runs the computer-readable instructions stored on the computer-readable storage medium, the various methods described above may be performed.

[0110] In addition, the computer device may also include (but not limited to) a data bus, an input / output (I / O) bus, a display, and input / output devices (eg, keyboard, mouse, speaker, etc.), etc.

[0111] The processor may communicate with external devices via an I / O bus via a wired or wireless network.

[0112] In one embodiment, the at least one computer executable instruction may also be compiled into or constitute a software product / computer program product, wherein one or more computer executable instructions are executed by a processor to perform the various functions and / or method steps in the embodiments described in the present technology.

[0113] In the embodiments provided in the present disclosure, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0114] It should be noted that in the present disclosure, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element limited by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0115] Although the embodiments disclosed in the present disclosure are as above, the above contents are only embodiments adopted for facilitating the understanding of the present disclosure and are not intended to limit the present disclosure. Any technician in the technical field to which the present disclosure belongs can make any modifications and changes in the form and details of the implementation without departing from the spirit and scope disclosed in the present disclosure, but the scope of patent protection of the present disclosure shall still be subject to the scope defined in the attached claims.

Claims

1. A data synchronization method, characterized in that: include: Check whether there are any changes in the service instance data table on the source side; In response to a change in the service instance data table of the source end, acquiring change information, parsing the change information, and obtaining a data table identifier; According to the data table identifier, searching for an interface corresponding to the data table identifier in the preset synchronization configuration information to obtain a target push interface; The target push interface is called to synchronize the changed data in the service instance data table of the source end to the target end according to the changed information.

2. The method according to claim 1, characterized in that The step of obtaining change information in response to a change in the service instance data table of the source end, parsing the change information, and obtaining a data table identifier comprises: In response to a change in the service instance data table of the source end, obtaining the change information, and sending the change information to a message queue; The change information in the message queue is obtained, the change information is parsed, and the data table identifier is obtained.

3. The method according to claim 2, characterized in that The steps of acquiring the change information in the message queue, parsing the change information, and obtaining the data table identifier include: Using the data synchronization service to detect whether there is change information in the message queue; In response to the data synchronization service detecting that there is change information in the message queue, the data synchronization service is used to obtain the change information in the message queue, parse the change information, and obtain the data table identifier.

4. The method according to claim 2, characterized in that: The step of detecting whether there is a change in the service instance data table at the source end includes: Use the data collection service to detect whether there are any changes in the service instance data table at the source end; The step of obtaining the change information in response to the change of the service instance data table of the source end and sending the change information to the message queue comprises: In response to the change of the service instance data table of the source end, the change information is obtained by using the data collection service, and the change information is sent to the message queue.

5. The method according to claim 1, characterized in that The step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information includes: Calling the target push interface to obtain the change data from the service instance data table of the source end according to the change information; The changed data is parsed to obtain parsed data without a format, the parsed data is assembled according to a preset data receiving format to obtain data to be synchronized, and the data to be synchronized is written into the service instance data table of the target end.

6. The method according to claim 1, characterized in that The step of searching, according to the data table identifier, for an interface corresponding to the data table identifier in the preset synchronization configuration information to obtain a target push interface comprises: According to the data table identifier, searching for an interface corresponding to the data table identifier in the preset synchronization configuration information, obtaining a target push interface and an interface address, an interface calling method, and an interface authentication parameter of the target push interface; The step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information includes: The target push interface is called using the interface address of the target push interface, the interface calling method and the authentication parameters of the interface, and the changed data in the service instance data table of the source end is synchronized to the target end according to the change information.

7. The method according to claim 2, characterized in that After the step of calling the target push interface and synchronizing the changed data in the service instance data table of the source end to the target end according to the change information, the following step further includes: Detect whether the changed data in the service instance data table of the source end is synchronized to the target end; When the changed data in the service instance data table of the source end fails to be synchronized to the target end, synchronization failure information indicating the synchronization failure is fed back to the message service; In response to the synchronization failure information, the target push interface is called to resynchronize the changed data in the service instance data table of the source end to the target end according to the change information.

8. A computer device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 7.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images