Data sharing and exchanging method and device

Abstract

The invention provides a data sharing and exchanging method and device, and the method comprises the steps: selecting database tables and fields of a source end and a destination end, generating a database table sharing and exchanging task, and monitoring the change of the corresponding database table by a source end database table trigger; the target end database table exchange execution engine obtains source end change data and sends the source end change data to the target user; selecting message servers of a source end and a destination end, generating a message sharing exchange task, monitoring a message theme of the message server of the source end, and sending the message theme to a target user by a message converter; the method comprises the following steps: selecting file systems of a source end and a destination end, generating a file sharing exchange task, monitoring file data change of the source end by a file access agent, and sending changed file data to a target user by a file delivery agent; sending the interface data from the source end interface to the destination end interface according to an interface data sharing exchange strategy; and scheduling sharing and exchange of database tables, messages, files and interface data to realize data sharing and exchange.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular, to a data sharing and exchange method and apparatus. Background Art

[0002] With the rapid development of cloud computing and big data technologies, data has become an important part of modern information system construction. The effective circulation and transfer of data are essential conditions for the operation of information systems. Data sharing and exchange between different systems, platforms, and networks need to follow certain standards and protocols. Due to different technical implementation methods between system platforms, technical barriers will be generated, making it difficult to share and exchange data between systems. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a data sharing and exchange method and apparatus to eliminate or improve one or more defects existing in the prior art.

[0004] One aspect of the present invention provides a data sharing and exchange method, the method comprising:

[0005] Execution steps for database table data sharing and exchange: Select database tables and fields under the source and destination data sources, generate a database table data sharing and exchange task file, obtain the database table data sharing and exchange task file by a database table trigger of the source data source and monitor data changes in the corresponding database table according to the database table data sharing and exchange task file to generate a change event file, obtain the change event file by a database table exchange execution engine of the destination data source and parse it to obtain the changed data in the database table under the source data source, and send the changed data to the target user;

[0006] Execution steps for message data sharing and exchange: Select message servers under the source and destination message sources, generate a message data sharing and exchange task, monitor message topics of the message server under the source message source according to the message data sharing and exchange task, and obtain the monitored message topics by a message converter and send them to the target user;

[0007] Execution steps for file data sharing and exchange: Select file systems accessed by the source and destination, generate a file data sharing and exchange task, obtain the file data sharing and exchange task by a file access agent and monitor file data changes in the file system accessed by the source according to the file data sharing and exchange task to generate a change event file, and obtain the change event file by a file delivery agent and send it to the target user;

[0008] Execution steps for interface data sharing and exchange: Configure a sharing and exchange policy for interface data, and send the interface data from the source interface to the destination interface according to the sharing and exchange policy of the interface data;

[0009] Scheduling execution steps: Schedule the execution steps of data sharing and exchange for database table data, message data, file data, and interface data to achieve data sharing and exchange.

[0010] In some embodiments of the present invention, in the execution steps of database table data sharing and exchange, the sending of changed data to the target user includes:

[0011] Synchronize the changed data to the database table under the destination data source for synchronous change; or,

[0012] Determine the subscription conditions and subscription parameters, configure the address of the message middleware specified by the user, and distribute the changed data to the message middleware specified by the user according to the subscription conditions and subscription parameters according to the configured address, so that users of external systems can subscribe to and consume the data received by the message middleware; or,

[0013] Push the changed data to the users of the external system through the interface.

[0014] In some embodiments of the present invention, the fields of the database tables under the source and destination data sources have a mapping relationship. In the case of no mapping relationship, the corresponding fields in the database tables under the source and destination data sources are the same.

[0015] In some embodiments of the present invention, in the execution steps of database table data sharing and exchange, in the case where the source and destination are physically isolated, by accessing a cross-network exchange device, the database table trigger sends the change event file across the network to the database table exchange execution engine.

[0016] In some embodiments of the present invention, in the execution steps of message data sharing and exchange, the sending of the monitored message topic to the target user includes:

[0017] Produce the monitored message topic to the message server under the destination message source; or,

[0018] Push the monitored message topic to the users of the external system through the interface.

[0019] In some embodiments of the present invention, the types of the message servers under the source message source and the destination message source are the same or different.

[0020] In some embodiments of the present invention, the message data sharing and exchange task includes: Select the message data to be shared and exchanged from the message server under the source message source.

[0021] In some embodiments of the present invention, in the execution steps of the file data sharing and exchange, sending the change event file to the target user includes:

[0022] Synchronizing the change event file to the file system accessed by the destination end for synchronous change; or,

[0023] Sending the change event file and the corresponding generated download link address to the message middleware, so that users of the external system can subscribe to and consume the file data received by the message middleware; or,

[0024] Pushing the download link address generated corresponding to the change event file to the users of the external system through the interface.

[0025] In some embodiments of the present invention, the file data sharing and exchange task includes: selecting the file data content, file type, and file size to be shared and exchanged from the file system accessed by the source end.

[0026] In some embodiments of the present invention, the execution steps of the interface data sharing and exchange further include: sending at least one type of data among database table data, message data, and file data from the source end interface to the destination end interface.

[0027] In some embodiments of the present invention, the sharing and exchange strategy of the interface data includes: at least including interface request types of addition, deletion, modification, and query.

[0028] In some embodiments of the present invention, the scheduling execution steps further include: performing timed scheduling on the execution steps of the database table data, message data, file data, and interface data sharing and exchange to achieve timed sharing and exchange of data.

[0029] On the other hand, the present invention provides a data sharing and exchange device, which includes: a computer device, the computer device includes a processor and a memory, the memory stores computer instructions, and the processor is used to execute the computer instructions stored in the memory. When the computer instructions are executed by the processor, the device implements the steps of the foregoing data sharing and exchange method.

[0030] On the other hand, the present invention provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements the steps of the foregoing data sharing and exchange method.

[0031] The data sharing and exchange method and device of the present invention, through unified scheduling of the execution steps of the database table data, message data, file data, and interface data sharing and exchange, realize the sharing and exchange of various types of data such as structured data, streaming data, unstructured data, and interface data across systems and platforms, and effectively solve the problem of difficult data sharing and exchange across systems and platforms.

[0032] Additional advantages, objects, and features of the present invention will be partly set forth in the description which follows, and will partly become obvious to those of ordinary skill in the art upon examination of the following, or may be learned by practice of the present invention. The objects and other advantages of the present invention may be realized and attained by the structure particularly pointed out in the specification and the drawings.

[0033] Those skilled in the art will understand that the objects and advantages that can be achieved by the present invention are not limited to those specifically described above, and the above and other objects that the present invention can achieve will be more clearly understood according to the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The drawings described herein are for further understanding of the present invention, form a part of this application, and do not limit the present invention.

[0035] Figure 1 It is a schematic flowchart of an embodiment of the data sharing and exchange method of the present invention;

[0036] Figure 2 It is a schematic flowchart of an embodiment of the execution steps of the database table data sharing and exchange of the present invention;

[0037] Figure 3 It is a schematic flowchart of an embodiment of the execution steps of the message data sharing and exchange of the present invention;

[0038] Figure 4 It is a schematic flowchart of an embodiment of the execution steps of the file data sharing and exchange of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0039] To make the objects, technical solutions, and advantages of the present invention more clearly understood, the present invention will be further described in detail below in conjunction with the embodiments and the drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but do not limit the present invention.

[0040] Here, it should also be noted that in order to avoid obscuring the present invention with unnecessary details, only the structures and / or processing steps closely related to the solution of the present invention are shown in the drawings, and other details less related to the present invention are omitted.

[0041] It should be emphasized that the term "comprising / including" when used herein refers to the presence of features, elements, steps, or components, but does not exclude the presence or addition of one or more other features, elements, steps, or components.

[0042] In the following, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0043] In view of the current situation of difficult data sharing and exchange between different systems and platforms, the embodiments of the present invention provide a data sharing and exchange method and device for user data, which can realize the sharing and exchange of structured database table data, unstructured text data, message data, and interface data.

[0044] Figure 1 It is a schematic flowchart of a data sharing and exchange method provided by the embodiments of the present invention. As Figure 1 shown, the data sharing and exchange method includes the following steps:

[0045] Step S110, the execution steps of database table data sharing and exchange: Select the database tables and fields under the source and destination data sources, generate a database table data sharing and exchange task file, and the database table trigger of the source data source obtains the database table data sharing and exchange task file and monitors the data changes of the corresponding database table according to the database table data sharing and exchange task file to generate a change event file. The database table exchange execution engine of the destination data source obtains the change event file and parses it to obtain the changed data in the database table under the source data source, and sends the changed data to the target user.

[0046] As Figure 2 shown, in the execution steps of the database table data sharing and exchange in step S110, the sending the changed data to the target user specifically includes: synchronizing the changed data to the database table under the destination data source for synchronous change; or, determining the subscription conditions and subscription parameters, configuring the address of the message middleware specified by the user, and distributing the changed data to the message middleware specified by the user according to the subscription conditions and subscription parameters according to the configured address, so that users of external systems can subscribe to and consume the data received by the message middleware; or, pushing the changed data to the users of external systems through an interface. Specifically, the subscription conditions and subscription parameters are respectively the fields corresponding to some or all of the changed data in the database table that the user wants to subscribe to determined based on the user's needs and the specific data under the fields.

[0047] Through the above solutions, the above three sharing and exchange methods of database table data are realized. Users can select the corresponding sharing and exchange method of database table data according to their needs, and support pushing the changed data or change content of the database table under the source data source to the database table under the destination data source for synchronous change, or pushing it to the message middleware to support users to obtain the changes of the database table under the source data source by subscribing, or enabling users of external systems to obtain the changes of the database table under the source data source in the form of data packets through an interface, so as to realize the sharing and exchange of database table data.

[0048] Specifically, first, in the data source management module of the database table data sharing and exchange module of the data sharing and exchange device, select the creation method as creating a new data source. The data source types supported for configuration in this data source, that is, the database table types, include: Kingbase, DM, GBase, Postgresql, Oracle, MySQL, Hive, GreenPlum, and many other types. Corresponding data source information for the above types is also configured. This data source information (i.e., database table information) includes: database table name, database table identifier, IP address, port, username, password, service name, and current schema name, etc. Perform a connection test on the data source according to the configured data source and database table information. Specifically, create a corresponding data source client according to the database table type, address, and username and password information. The data source client sends a connection request to the data source. If the data source client successfully establishes a connection with the data source, it indicates that the connection test is normal, and the data source and its information are saved. On the contrary, if the data source client fails to establish a connection with the data source, it indicates that the connection test is abnormal, throws a connection exception message, and reconfigures the data source information until the connection test is successful and saved. In addition to being used for the above connection test of the data source, this data source management module can also support the modification and deletion of database tables and their connections, and support the modification of the listening rules and listening frequencies of database tables. Then, connect to the data source with normal connection test through the source end and the destination end respectively, so as to configure the data source at the source end and the destination end respectively. If the source end and the destination end are not directly connected, such as in the case of a physically isolated network, deploy data sharing and exchange devices at the source end and the destination end respectively, and the source end and the destination end are connected to the corresponding data sources.

[0049] In the embodiment of the present invention, all database tables or a specific database table under the source end data source are selected according to user requirements, and the fields in the database table and the data under the fields are selected. This field can be all fields or custom fields selected by the user who wants to share and exchange. Correspondingly, the database table data sharing and exchange module supports custom configuration of SQL statements, so as to realize the configuration of the fields and field data of the database table under the source end data source that the user wants to share and exchange.

[0050] In the database table data sharing and exchange module of the data sharing and exchange device, the fields of the database tables under the source end and the destination end data sources have a mapping relationship. In the case of no mapping relationship, the corresponding fields in the database tables under the source end and the destination end data sources are the same. That is to say, when the mapping relationship between the fields in the source end database table and the destination end database table is not configured, the corresponding fields in the default-configured source end database table and the corresponding destination end database table are the same.

[0051] In the execution steps of database table data sharing and exchange, in the case where the source end and the destination end are physically isolated, by accessing a cross-network exchange device, the database table trigger sends the change event file across the network to the data exchange execution engine at the destination end, and then the data exchange execution engine sends the changes of the database table under the data source at the source end to the target user in the above three sharing and exchange methods, so that the method and device support the sharing and exchange of database table data between physically isolated devices.

[0052] Step S120, the execution steps of message data sharing and exchange: Select the message servers under the source end and destination end message sources, generate a message data sharing and exchange task, listen to the message topics of the message servers under the source end message source according to the message data sharing and exchange task, and the message converter obtains the listened message topics and sends them to the target user.

[0053] As Figure 3 shown, in the execution steps of the message data sharing and exchange in step S120, the sending of the listened message topics to the target user includes: producing the listened message topics to the message server under the destination end message source; or pushing the listened message topics to the users of the external system through an interface. Specifically, each message topic in the message server stores a type of message data.

[0054] Through the above solutions, the above two message data sharing and exchange methods are realized. Users can select the corresponding message data sharing and exchange method according to their needs. They can produce the message topics and corresponding message data of the message server under the source end message source to the message server under the destination end message source for users to consume and obtain, or push the message topics and message data of the source end message source to the users of the external system through an interface, so as to realize the sharing and exchange of message flow data in the form of message topics.

[0055] Specifically, first, select and add a message source and the type of the message source, that is, the type of the message server, in the message data sharing and exchange module of the data sharing and exchange device. Then, configure the corresponding message server information, which includes the name of the message server, IP address information, port information, message topic, and explanatory note information, etc. Conduct a connection test on the configured accessed message server based on the configured message server information. The specific steps of the connection test include: create a corresponding message source client according to the configured message source type, message source address, and port information, and the message source client initiates a connection request to the message server. If the message service client successfully establishes a connection with the message server, it indicates that the connection test is normal, and save the message servers and message server information of the configured source end and destination end. Otherwise, if the message service client fails to establish a connection with the message server, the connection test is abnormal, throw relevant connection exception information, and reconfigure the message server information until the connection test of the message servers of the configured source end and destination end is successful and saved. Then, message sources and message servers that support multiple types can be respectively configured at the source end and the destination end.

[0056] Specifically, the message data sharing and exchange task includes: select the message data to be shared and exchanged from the message server under the source end message source. That is, obtain the message topic of the message data to be shared and exchanged from the message server under the configured source end message source according to the user's needs. If the user wants to obtain historical message data, obtain the initial message topic from the beginning. If the user wants to obtain the latest message data, obtain the current latest message topic.

[0057] Specifically, in the message source management module of the message data sharing and exchange module of the data sharing and exchange device, the types of the source end message source and the destination end message source that can be supported for addition can be the same or different, that is, the types of the message servers under the source end message source and the destination end message source are the same or different. For example, the message server under the source end message source is kafka, and the message server under the destination end message source is RabbitMQ. Through the message converter, forward the messages of the message server under the source end message source to the message server under the destination end message source, realizing the sharing and exchange of message data from the source end to the destination end, so that the sharing and exchange of message data in the message server under the source end message source can be realized without modifying the message server under the destination end message source.

[0058] Step S130, the execution steps of file data sharing and exchange: Select the file systems accessed by the source end and the destination end, generate a file data sharing and exchange task, and have the file access agent obtain the file data sharing and exchange task and listen for changes in the file data of the file system accessed by the source end according to the file data sharing and exchange task to generate a change event file. Then, have the file delivery agent obtain the change event file and send it to the target user.

[0059] As Figure 4 shown, in the execution steps of the file data sharing and exchange, the sending the change event file to the target user includes: synchronizing the change event file to the file system accessed by the destination end for synchronous change; or, sending the change event file and the corresponding generated download link address to the message middleware, enabling users of the external system to subscribe to and consume the file data received by the message middleware; or, pushing the download link address corresponding to the change event file to the users of the external system through an interface.

[0060] Through the above solutions, the above three file data sharing and exchange methods are realized. Users can select the corresponding file data sharing and exchange method according to their needs. They can synchronize the changed file data in the file system accessed by the source end to the file system accessed by the destination end in the form of a text file for synchronous change, or push the changed file data in the form of a text file and its file download link address to the message middleware, enabling users to obtain the changes in the file data by subscribing and consuming, or enable users of the external system to obtain the changes in the file data in the form of a text file through an interface, thus realizing the sharing and exchange of file data.

[0061] Specifically, in the file data sharing and exchange module of the data sharing and exchange device, the types of file systems that can be accessed, including remote FTP file servers, distributed file systems HDFS, object storage systems MINIO, and local file systems of remote servers, etc., can be respectively configured to the source end and the destination end, and the corresponding type of file system can be selected from the above configured types of file systems. Similarly, after configuring the file systems accessed by the source end and the destination end, configure the corresponding file system information. Conduct a connection test on the file systems accessed by the source end and the destination end according to the configured file system information. Specifically, create a file system client according to the file system information, and have the file system client send a connection request to the file system. If the file system client successfully establishes a connection with the file system, it indicates that the connection test is normal, and save the configured file system and its information. Otherwise, if the file system client fails to establish a connection with the file system, it indicates that the connection test is abnormal, reconfigure the file system information, and re-execute the connection test until the connection test is successful and saved.

[0062] The file data sharing and exchange task includes: selecting the file data content, file type, and file size to be shared and exchanged from the file system accessed at the source end.

[0063] Step S140, the execution steps of interface data sharing and exchange: Configure the sharing and exchange policy of interface data, and send the interface data from the source interface to the destination interface according to the sharing and exchange policy of interface data.

[0064] The execution steps of the interface data sharing and exchange further include: sending at least one type of data among database table data, message data, and file data from the source interface to the destination interface.

[0065] Specifically, in the interface data sharing and exchange task of this step, the interface of a third-party system or external system is used as the source interface, and the interface of another third-party system or external system is used as the destination interface. Based on task scheduling, the external interface data, database table data, unstructured text data, and message data of the message server accessed by this data sharing and exchange device are pushed to the external system in the form of API by calling the configured source interface and destination interface, realizing data sharing and exchange.

[0066] The sharing and exchange policy of the interface data includes: at least including interface request types of addition, deletion, modification, and query, and performing corresponding operations on the interface data according to different request types of addition, deletion, modification, and query of the interface, and then sending it from the source interface to the destination interface. The address information of the interface includes request header parameter information and request body parameter information. After configuring the interface address information of the source end and the destination end, the interface can be tested for request connection online according to the configured interface address information. If the request connection is successful, the test is successful, and the configured interface address information is saved; otherwise, the interface address information is reconfigured until the request connection is successful.

[0067] Step S150, the scheduling execution step: Schedule the execution steps of database table data, message data, file data, and interface data sharing and exchange to realize data sharing and exchange.

[0068] In this step, the task scheduling and management module of the data sharing and exchange device supports unified task scheduling and management of the sharing and exchange execution steps of database table data, message data, file data, and interface data. Through the task scheduling and management of the above various types of data, the sharing and exchange of various types of data are realized. At the same time, it also supports configuring the sharing and exchange tasks of database table data, message data, file data, and interface data according to a timing policy, that is, configuring the sharing and exchange frequencies of database table data, message data, file data, and interface data, and realizing the addition, modification, deletion, start, and stop of sharing and exchange tasks through scheduling. Specifically, in the sharing and exchange execution step of the database table, the listening rules and listening frequencies of the database table triggers of the source data source can be configured. The database table triggers collect the content data of the database table under the source data source according to the listening rules and listening frequencies, monitor its changes, capture change events and generate change event files by periodically monitoring the changes of the database table under the source data source, and send the change event files to the database table exchange execution engine of the destination data source. Finally, the database table exchange execution engine of the destination data source pushes them to the target user in three database table sharing and exchange methods, realizing the change synchronization, subscription, and push of database table data. In the execution step of message data sharing and exchange, the timed sharing and exchange of message data in the form of message topics are realized by configuring the listening frequency of the message topics of the message server under the source message source. In the execution step of the file data sharing and exchange task, the file data and its changes are also obtained periodically by configuring the listening frequency of the file data accessed at the source end, and finally the content of the source end file data is shared and exchanged to the destination file system, message middleware, or external system periodically. In the execution step of interface data sharing and exchange, the timed sharing and exchange of interface data, database table data, message data, and file data are realized by configuring the exchange frequency of the interface. It also supports configuring the scheduling frequency, and performing timed scheduling on the execution steps of the sharing and exchange of database table data, message data, file data, and interface data according to the scheduling frequency, realizing the timed sharing and exchange of data.

[0069] Correspondingly to the above method, a data sharing and exchange device according to an embodiment of the present invention includes a computer device, the computer device includes a processor and a memory, computer instructions are stored in the memory, and the processor is used to execute the computer instructions stored in the memory. When the computer instructions are executed by the processor, the device implements the steps of the foregoing data sharing and exchange method.

[0070] The data sharing and exchange method and device according to the embodiments of the present invention are mainly used in scenarios where data sharing and interaction are carried out between various systems. Through the interaction of the database table data sharing and exchange module, the message data sharing and exchange module, the file data sharing and exchange module, the interface data sharing and exchange module, and the task scheduling and management module, the efficiency of sharing and exchanging the above various types of data across multiple systems is greatly improved, promoting the rapid iterative development of information systems.

[0071] The embodiments of the present invention also provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the foregoing data sharing and exchange method are implemented. The computer-readable storage medium may be a tangible storage medium, such as a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a floppy disk, a hard disk, a removable storage disk, a CD-ROM, or any other form of storage medium well-known in the technical field.

[0072] Those of ordinary skill in the art should understand that the various exemplary components, systems, and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software, or a combination of both. Specifically, whether to implement in hardware or software depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention. When implemented in hardware, it may be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in, a functional card, etc. When implemented in software, the elements of the present invention are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium or transmitted through a data signal carried in a carrier wave on a transmission medium or a communication link.

[0073] It should be clear that the present invention is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order between steps after understanding the spirit of the present invention.

[0074] In the present invention, the features described and / or illustrated for one embodiment can be used in the same or similar manner in one or more other embodiments, and / or combined with the features of other embodiments or replace the features of other embodiments.

[0075] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, various modifications and variations can be made to the embodiments of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A data sharing and exchange method, characterized in that, The method includes: Execution steps for database table data sharing and exchange: Select database tables and fields under the source and destination data sources, generate a database table data sharing and exchange task file. The database table trigger of the source data source obtains the database table data sharing and exchange task file and listens for data changes in the corresponding database table according to the database table data sharing and exchange task file, generating a change event file. The database table exchange execution engine of the destination data source obtains the change event file and parses it to obtain the changed data in the database table under the source data source, and sends the changed data to the target user. Execution steps for message data sharing and exchange: Select message servers under the source and destination message sources, generate a message data sharing and exchange task. Listen for the message topics of the message server under the source message source according to the message data sharing and exchange task. The message converter obtains the listened message topics and sends them to the target user. Execution steps for file data sharing and exchange: Select file systems accessed by the source and destination, generate a file data sharing and exchange task. The file access agent obtains the file data sharing and exchange task and listens for file data changes in the file system accessed by the source according to the file data sharing and exchange task, generating a change event file. The file delivery agent obtains the change event file and sends it to the target user. Execution steps for interface data sharing and exchange: Configure the sharing and exchange policy for interface data, and send the interface data from the source interface to the destination interface according to the sharing and exchange policy of the interface data. Scheduling execution steps: Schedule the execution steps for database table data, message data, file data, and interface data sharing and exchange to achieve data sharing and exchange.

2. The method according to claim 1, wherein In the execution steps of the database table data sharing and exchange, the sending of the changed data to the target user includes: Synchronizing the changed data to the database table under the destination data source for synchronous change; or, Determining subscription conditions and subscription parameters, configuring the address of the message middleware specified by the user, and distributing the changed data to the message middleware specified by the user according to the subscription conditions and subscription parameters at the configured address, so that users of external systems can subscribe to and consume the data received by the message middleware; or, Pushing the changed data to the users of the external system through an interface.

3. The method according to claim 1, wherein The fields of the database tables under the source and destination data sources have a mapping relationship. In the case of no mapping relationship, the corresponding fields in the database tables under the source and destination data sources are the same.

4. The method according to any one of claims 1 to 3, characterized in that, In the execution steps of the database table data sharing and exchange, in the case where the source and destination are physically isolated, by accessing a cross-network exchange device, the database table trigger sends the change event file across the network to the database table exchange execution engine.

5. The method according to claim 1, wherein In the execution steps of the message data sharing and exchange, the sending of the listened message topics to the target user includes: Producing the listened message topics to the message server under the destination message source; or, Pushing the listened message topics to the users of the external system through an interface.

6. The method according to claim 5, characterized in that, The types of the message servers under the source - side message source and the message servers under the destination - side message source are the same or different.

7. The method according to claim 1, wherein The message data sharing and exchange task includes: selecting the message data to be shared and exchanged from the message servers under the source - side message source.

8. The method according to claim 1, characterized in that, In the execution steps of the file data sharing and exchange, the step of sending the change event file to the target user includes: Synchronizing the change event file to the file system accessed by the destination - side for synchronous change; or, Sending the change event file and the corresponding generated download link address to the message middleware, so that users of the external system can subscribe to and consume the file data received by the message middleware; or, Pushing the download link address generated corresponding to the change event file to the users of the external system through an interface.

9. The method according to claim 1, characterized in that, The file data sharing and exchange task includes: selecting the file data content, file type, and file size to be shared and exchanged from the file system accessed by the source - side.

10. The method according to claim 1, characterized in that, The execution steps of the interface data sharing and exchange further include: sending at least one type of data among database table data, message data, and file data from the source - side interface to the destination - side interface.

11. The method according to claim 1, characterized in that, The sharing and exchange policy of the interface data includes: at least including interface request types of addition, deletion, modification, and query.

12. The method according to claim 1, wherein The scheduling execution steps further include: performing timed scheduling on the execution steps of the database table data, message data, file data, and interface data sharing and exchange to achieve timed data sharing and exchange.

13. A data sharing and exchange device, comprising a processor and a memory, characterized in that, The memory stores computer instructions, and the processor is used to execute the computer instructions stored in the memory. When the computer instructions are executed by the processor, the device implements the steps of the method described in any one of claims 1 to 12.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the method described in any one of claims 1 to 12.

Images