CN117453822A - Cross-environment data synchronization method, device and equipment - Google Patents

Abstract

The application provides a cross-environment data synchronization method, device and equipment. The method is applied to the server side of the first system and comprises the following steps: acquiring an import request, wherein the import request is used for indicating to acquire a file to be synchronized; acquiring a file to be synchronized according to the importing request; determining a plurality of entities to be imported of a database of a first system according to files to be synchronized; each entity to be imported characterizes each datum; the entity to be imported has an attribute and an attribute value; if the plurality of entities to be imported comprise all entities in the preset first data table, converting the identification of the entity to be imported into the identification of the corresponding entity in the first data table to obtain the converted entity to be imported; the first data table comprises a designated entity of a database of the first system and an identification of the designated entity; and storing the converted entity to be imported into a database of the first system according to the identification of the converted entity to be imported. The method improves the data synchronization efficiency.

Description

Cross-environment data synchronization method, device and equipment

Technical field

The present application relates to the field of data synchronization, and in particular, to a cross-environment data synchronization method, device and equipment.

Background technique

In the field of e-commerce, the product center system is used to manage product data. However, the data synchronization of the commodity center system in different environments is limited by network isolation, that is, the database of the commodity center system in the production environment is not connected to the network of the commodity center database in the non-production environment, resulting in the commodity center system in the production environment being disconnected. The product data of cannot be directly synchronized with the product data of the product center in a non-production environment.

Currently, the synchronization method between the product data of the product center system in the production environment and the product data of the product center in the non-production environment usually requires the user to download the data to be synchronized from the product center system in the export environment and use the preset Fill the specific template to be synchronized with the preset specific template, and then import it into the product center system in the import environment.

However, in the above method, the data to be synchronized needs to be manually converted into the format in a specific template, resulting in low efficiency of data synchronization.

Contents of the invention

This application provides a cross-environment data synchronization method, device and equipment to solve the technical problem of low data synchronization efficiency.

In the first aspect, this application provides a cross-environment data synchronization method. The method is applied to the server of the first system and includes:

Obtain an import request, wherein the import request is used to instruct to obtain the file to be synchronized; and obtain the file to be synchronized according to the import request;

According to the files to be synchronized, multiple entities to be imported in the database of the first system are determined; wherein each entity to be imported represents each data; the entities to be imported have attributes and attribute values;

If it is determined that the multiple entities to be imported include all entities in the preset first data table, then the identifier of the entity to be imported is converted into the identifier of the corresponding entity in the first data table, and the converted entity is obtained. entities to be imported; wherein the first data table includes the designated entity of the database of the first system and the identification of the designated entity;

According to the identification of the converted entity to be imported, the converted entity to be imported is stored in the database of the first system.

Optionally, the import request carries import parameters; the import parameters include the import type and the import information corresponding to the import type; if it is determined that the multiple entities to be imported include the preset first data table All entities, then convert the identifier of the entity to be imported into the identifier of the corresponding entity in the first data table to obtain the converted entity to be imported, including:

If it is determined that the multiple entities to be imported include all entities in the preset first data table, and the import type is an update type, then the import information corresponding to the preset matching rules and the update type is determined. The number of data in the database of the first system corresponding to the entity to be imported;

When it is determined that the number of data in the database of the first system corresponding to the entity to be imported is one, the identifier of the entity to be imported is converted into the identifier of the corresponding entity in the first data table. , get the converted entity to be imported;

When it is determined that the number of data in the database of the first system corresponding to the entity to be imported is greater than one, then the data in the database of the first system corresponding to the entity to be imported is output to the third system. A client of a system, and obtains the data in the database of the first system that is finally selected by the user; and uses the data in the database of the first system that is finally corresponding to update the files to be synchronized; And repeat the step of determining multiple entities to be imported into the database of the first system based on the files to be synchronized.

Optionally, the method also includes:

If it is determined that the multiple entities to be imported include all entities in the preset first data table, and the import type is a new type, then the entities to be imported will be imported according to the import information corresponding to the new type. The identifier is converted into the identifier of the corresponding entity in the first data table, and the converted entity to be imported is obtained.

Optionally, the import request carries import parameters and files to be synchronized; according to the import request, obtaining the files to be synchronized includes:

Upload the files to be synchronized to the first intermediate system corresponding to the first system;

Receive the storage address of the file to be synchronized returned by the first intermediate system, and generate an import log according to the import parameters sent by the client of the first system and the storage address of the file to be synchronized;

According to the storage address of the file to be synchronized in the import log, the file to be synchronized is downloaded from the first intermediate system corresponding to the first system.

Optionally, the file to be synchronized includes data of the target commodity to be synchronized; according to the file to be synchronized, multiple entities to be imported into the database of the first system are determined, including:

Decrypt the file to be synchronized to obtain each decrypted data; wherein each decrypted data is each entity to be synchronized; the entity to be synchronized is an entity of the database of the second system ;The entity to be synchronized has attributes and attribute values;

According to the preset second data table, the entities to be synchronized are converted into entities to be imported into the database of the first system; wherein the second data table includes the entities to be synchronized into the database of the second system. The corresponding relationship between the entity and the entity to be imported in the database of the first system.

Optionally, after converting the entities to be synchronized into entities to be imported into the database of the first system according to the preset second data table, the method further includes:

According to the preset third data table, the entities to be imported in the database of the first system are filtered.

Optionally, the method also includes:

If it is determined that the multiple entities to be imported do not include any entity in the preset first data table, prompt information is returned to the client of the first system, and the prompt information indicates that the import of data has failed.

Optionally, storing the converted entity to be imported in the database of the first system according to the identification of the converted entity to be imported includes:

Multiple data sets are generated according to the preset fourth data table and the converted identification of the entity to be imported; wherein the fourth data table includes the preset data set and the converted identification of the entity to be imported. , and the data table of the database of the first system, and the corresponding relationship between the three; the data set includes a plurality of converted entities to be imported;

Based on the thread corresponding to the data set, a plurality of converted entities to be imported in the data set are stored in the corresponding data table of the database of the first system.

In the second aspect, a cross-environment data synchronization method is applied to the server of the second system, including:

Receive an export request initiated by the client of the second system, wherein the export request is used to indicate that the data of the target commodity to be synchronized needs to be exported, and the export request carries export parameters; and generates based on the export parameters Export log;

Generate messages to be processed according to the export log, and send the messages to be processed to a preset message queue; wherein the message queue includes at least one message to be processed;

Obtain the messages to be processed in the preset message queue; and obtain data from the preset database according to the acquired messages to be processed; wherein the preset database includes data of at least one commodity;

Generate a file to be synchronized based on the acquired data, and send the file to be synchronized to the client of the second system;

Wherein, the file to be synchronized is the file to be synchronized according to any one of the first aspects.

Optionally, the export parameters include the identification of the target product to be synchronized; the export log includes the identification of the export log, the export parameters and the export status; the export status represents whether the export data is successful.

Optionally, sending the pending message to the message queue includes:

Based on the identification of the export log as the message primary key and the export parameter as the message body, the message to be processed is sent to the message queue.

Optionally, generate files to be synchronized based on the obtained data, including:

Encrypt the obtained data to obtain encrypted data;

The encrypted data is encapsulated to obtain the file to be synchronized.

Optionally, sending the file to be synchronized to the client of the second system includes:

Upload the files to be synchronized to the second intermediate system corresponding to the second system;

Receive the storage address of the file to be synchronized returned by the second intermediate system, and write the storage address of the file to be synchronized into the export log, and determine that the export status is export successful; wherein, The above storage address is used to obtain the file to be synchronized;

Download the file to be synchronized from the second intermediate system according to the storage address of the file to be synchronized; and send the file to be synchronized to the client of the second system.

In the third aspect, this application provides a cross-environment data synchronization device, which is applied to the server of the first system and includes:

An acquisition unit, configured to acquire an import request, where the import request is used to instruct the acquisition of files to be synchronized; and to acquire the files to be synchronized according to the import request;

Determining unit, configured to determine multiple entities to be imported in the database of the first system according to the files to be synchronized; wherein each entity to be imported represents each data; the entities to be imported have attributes and attribute values;

A conversion unit configured to convert the identification of the entity to be imported into the identification of the corresponding entity in the first data table when it is determined that the multiple entities to be imported include all entities in the preset first data table. Identify, obtain the converted entity to be imported; wherein, the first data table includes the designated entity of the database of the first system and the identification of the designated entity;

A storage unit configured to store the converted entity to be imported into the database of the first system according to the identification of the converted entity to be imported.

In the fourth aspect, this application provides a cross-environment data synchronization device, which is applied to the server of the second system and includes:

A receiving unit configured to receive an export request initiated by the client of the second system, wherein the export request is used to indicate that the data of the target commodity to be synchronized needs to be exported, and the export request carries export parameters; and based on The export parameters generate export logs;

A generation unit configured to generate messages to be processed according to the export log, and send the messages to be processed to a preset message queue; wherein the message queue includes at least one message to be processed;

An acquisition unit, configured to acquire messages to be processed in the preset message queue; and to acquire data from a preset database according to the acquired messages to be processed; wherein the preset database includes data of at least one commodity;

A sending unit, configured to generate a file to be synchronized based on the acquired data, and send the file to be synchronized to the client of the second system;

Wherein, the file to be synchronized is the file to be synchronized according to any one of the first aspects.

In a fifth aspect, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

The memory stores computer execution instructions;

The processor executes the computer execution instructions stored in the memory to implement the method as described in any one of the first aspect or the second aspect.

In a sixth aspect, the present application provides a computer-readable storage medium in which computer-executable instructions are stored, and when executed by a processor, the computer-executable instructions are used to implement the first aspect or the second aspect. any one of the methods.

The cross-environment data synchronization method, device and equipment provided by this application achieves data accuracy by converting the data in the files to be synchronized into entities in the database of the first system, and based on the preset first data table. The data identity in the file to be synchronized is verified and replaced with the identity of the entity in the database. According to the identity of the converted entity to be imported, the converted entity to be imported can be directly stored in the first system. in the database. Compared with the existing technology where data can be stored only after manually using a specific template to process the data, this method can achieve the format of the data in the file to be synchronized and the data in the database without manually using a specific template for data filling. conversion to store the data in the files to be synchronized into the database, improving the efficiency of data synchronization.

Description of the drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

Figure 1 is a schematic diagram of an application scenario provided by this application;

Figure 2 is a schematic flow chart of a cross-environment data synchronization method provided by this application;

Figure 3 is a schematic flow chart of a cross-environment data synchronization method provided by this application;

Figure 4 is a schematic flow chart of a cross-environment data synchronization method provided by this application;

Figure 5 is a schematic flow chart of a cross-environment data synchronization method provided by this application;

Figure 6 is a schematic structural diagram of a cross-environment data synchronization device provided by this application;

Figure 7 is a schematic structural diagram of a cross-environment data synchronization device provided by this application;

Figure 8 is a schematic structural diagram of a cross-environment data synchronization device provided by this application;

Figure 9 is a schematic structural diagram of a cross-environment data synchronization device provided by this application;

Figure 10 is a schematic structural diagram of an electronic device provided by this application.

Through the above-mentioned drawings, clear embodiments of the present application have been shown, which will be described in more detail below. These drawings and text descriptions are not intended to limit the scope of the present application's concepts in any way, but are intended to illustrate the application's concepts for those skilled in the art with reference to specific embodiments.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the appended claims.

First, let’s explain the terms involved in this application:

Production environment: refers to the environment used to deploy and operate software products.

Non-production environment: refers to the environment where software products are developed, tested, etc.

In the existing technology, the data synchronization of the commodity center system in different environments is limited by network isolation, that is, the database of the commodity center system in the production environment is not connected to the network of the database of the commodity center in the non-production environment, resulting in the failure of the commodity center system in the production environment. The product data of the product center system cannot be directly synchronized with the product data of the product center in a non-production environment.

Currently, the synchronization method between the product data of the product center system in the production environment and the product data of the product center in the non-production environment usually requires the user to download the data to be synchronized from the product center system in the export environment and use the preset Fill the specific template to be synchronized with the preset specific template, and then import it into the product center system in the import environment.

However, in the above method, the data to be synchronized needs to be manually converted into the format in a specific template, resulting in low efficiency of data synchronization.

In view of this, this application provides a cross-environment data synchronization method. Based on the file to be synchronized, the identification of the data in the file to be synchronized is converted into the identification of the entity in the database of the imported environment. That is, according to the identification of the entity , store the data in the file to be synchronized into the database of the imported environment. This method does not require manual use of specific templates to process the data to be imported, which improves the efficiency of data synchronization.

Figure 1 is a schematic diagram of an application scenario provided by this application. As shown in Figure 1, it includes a first system, a first intermediate system corresponding to the first system, a second system, and a second intermediate system corresponding to the second system.

The above-mentioned first system and second system may be commodity center systems or other business systems. The above-mentioned first system and second system are respectively deployed in different environments. For example, the above-mentioned first system is deployed in a production environment, and the above-mentioned second system is deployed in a non-production environment. It should be noted that this application only takes the first system as a system for data import and the second system as a system for data export as an example, and does not limit the environments in which the first system and the second system are located.

Taking the first system as an example, the first system may include a server and a client. The server of the first system may be deployed in a server or a server cluster to process the business logic of the first system; The client may be a World Wide Web (Web) version client or an application (Application, app) version client, which is not limited in this application. The client of the first system is used to display the front-end display interface of the server of the first system and receive instructions triggered by the user. The client of the first system can be deployed on electronic devices, such as mobile phones, computers, tablets, etc. Optionally, the first system may also include a database of the first system, used to store business data of the first system. The structure of the above-mentioned second system is similar and will not be described again here.

It should be noted that the client of the first system and the client of the second system are deployed on the same electronic device.

The first intermediate system corresponding to the above-mentioned first system is used to store files to be synchronized in the first system, and may be, for example, a cloud storage system such as Object Storage Service (OSS). The above-mentioned second intermediate system is similar and will not be described again here. It should be noted that this application does not limit the form of the first intermediate system corresponding to the first system and the second intermediate system corresponding to the second system. They may be the same or different.

The technical solution of the present application and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

Figure 2 is a schematic flowchart of a cross-environment data synchronization method provided by this application. This method is applied to the server of the above-mentioned first system. As shown in Figure 2, the method includes:

S101. The server of the first system obtains an import request, where the import request is used to instruct to obtain the file to be synchronized; and obtains the file to be synchronized according to the import request.

For example, the above-mentioned import request may be triggered by the user through the client of the above-mentioned first system.

In one example, the above-mentioned import request carries the file to be synchronized, and the file to be synchronized can be obtained according to the import request; in another example, the above-mentioned import request carries the storage address of the file to be synchronized, and the above-mentioned The server of the first system can obtain the file to be synchronized from the first intermediate system corresponding to the first system according to the storage address.

S102. The server of the first system determines multiple entities to be imported in the database of the first system based on the files to be synchronized.

Among them, each entity to be imported represents each data; the above-mentioned entity to be imported has attributes and attribute values.

For example, the database of the first system includes multiple entities, and the multiple entities have a corresponding relationship with each data in the file to be synchronized.

In one example, the server of the first system can convert each data in the file to be synchronized into the first file according to the file to be synchronized and the preset correspondence table between data and entities. Multiple entities to be imported from the system's database. In another example, the preset field of the file to be synchronized represents the default entity of the database of the first system. The server of the first system can use the file to be synchronized and the preset preset field. The corresponding relationship table with entities converts each data in the above-mentioned files to be synchronized into multiple entities to be imported into the database of the first system.

For example, the above files to be synchronized include: {Product name: Computer 1234, ID: A1, Quantity: 10 units}, and the entities to be imported are: {Product name: Computer, ID: A1, Quantity: 10 units}.

S103. If the server of the first system determines that the multiple entities to be imported include all entities in the preset first data table, it converts the identifiers of the entities to be imported into the identifiers of the corresponding entities in the first data table. , get the converted entity to be imported.

Wherein, the above-mentioned first data table includes the designated entity of the database of the first system and the identifier of the designated entity.

For example, all entities in the above-mentioned first data table refer to data necessary for the first system, that is, all entities in the first data table are indispensable data. This step can determine the data in the entities to be imported. Is the required data missing? If necessary data is missing, it is considered that there is an error in the data to be imported. The name and identifier of the converted entity to be imported are consistent with the name and identifier of the corresponding entity in the database of the first system.

In one example, the server of the first system may traverse the multiple entities to be imported based on the entities in the first data table, and determine whether all entities in the first data table belong to the multiple entities to be imported. . Optionally, if it is determined that the multiple entities to be imported do not include all entities in the preset first data table, a prompt message indicating that the import fails is output to the client of the first system. If it is determined that the multiple entities to be imported include all entities in the preset first data table, then according to the above-mentioned first data table, the identifier of the entity to be imported is converted into the identifier of the corresponding entity in the first data table, Get the converted entity to be imported.

For example, the above files to be synchronized include: {Product name: Computer 1234, ID: A1, Quantity: 10 units}, and the entities to be imported are: {Product name: Computer, ID: A1, Quantity: 10 units}, conversion The final entities to be imported are: {Product name: Computer, Identification: B1, Quantity: 10 units}.

It should be noted that in the aforementioned step S102, although the data in the file to be synchronized is converted into entities in the database of the first system, the identifier corresponding to the data is not converted. Therefore, in step S103, the After each entity to be imported is verified, the identifiers of the multiple entities to be imported are converted into identifiers of corresponding entities in the database of the first system to facilitate subsequent storage processes and improve data synchronization efficiency.

S104. The server of the first system stores the converted entity to be imported in the database of the first system according to the converted identification of the entity to be imported.

For example, as mentioned above, the identity of the converted entity to be imported is consistent with the identity of the corresponding entity in the database of the first system. Therefore, the identity of the entity to be imported can be determined based on the converted identity of the entity to be imported. The location of the corresponding entity in the database of the first system is stored in the database of the first system.

In this embodiment, by converting the data in the files to be synchronized into entities in the database of the first system, and based on the preset first data table, data accuracy verification and the data in the files to be synchronized are implemented. The data identifier is replaced with the identifier of the entity in the database. According to the converted identifier of the entity to be imported, the converted entity to be imported can be directly stored in the database of the first system. Compared with the existing technology where data can be stored only after manually using a specific template to process the data, this method can achieve the format of the data in the file to be synchronized and the data in the database without manually using a specific template for data filling. conversion to store the data in the files to be synchronized into the database, improving the efficiency of data synchronization.

Figure 3 is a schematic flowchart of a cross-environment data synchronization method provided by this application. This method is applied to the server of the above-mentioned second system. As shown in Figure 3, the method includes:

S201. The server of the second system receives an export request initiated by the client of the second system. The export request is used to indicate that the data of the target commodity to be synchronized needs to be exported. The export request carries export parameters; and based on the Export parameters generate export logs.

For example, the client of the second system receives the export request triggered by the user, and sends the export request to the server of the second system.

In one example, the above export parameters include the identification of the target product to be synchronized, and the export log is generated based on the export parameters and the preset file generation function. In another example, the above-mentioned export parameters include the name and identification of the target product to be synchronized, and the export log is generated based on the export parameters and the preset file generation function.

In one example, the export log may include the export log's identifier and export parameters; it may also include the export log's identifier, export parameters, and export status. The export status can be used to indicate whether the export data is successful. For example, the export status can be exporting or successful. This method can use the export log to intuitively see whether the data is exported successfully, improving the convenience of data synchronization.

S202. The server of the second system generates a message to be processed according to the export log, and sends the message to be processed to a message queue; wherein the message queue includes at least one message to be processed.

In one example, the identifier of the export log can be used as the primary key of the message, the export parameters can be used as the message body, the message to be processed can be generated, and the message to be processed can be sent to the above message queue. It is also possible to preset the message primary key corresponding to the export log, use the export log identifier and the export parameters together as the message body, generate the message to be processed, and send the message to be processed to the above message queue.

For example, the server of the second system can be divided into a first module and a second module, and the first module, the second module and the message queue server together form the message queue of the second system. The first module can serve as a producer of the message queue and is used to generate messages to be processed according to the export log. The second module serves as a consumer and is used to obtain messages from the message queue for processing. It should be noted that this application does not limit the division method of the server side of the second system. The server of the above message queue may be a server in the server of the second system, or may be another server located in the cloud, which is not limited in this application.

S203. The server of the second system obtains the messages to be processed in the preset message queue; and obtains data from the preset database according to the obtained messages to be processed; wherein the above-mentioned preset database includes data of at least one commodity.

For example, as mentioned above, the above-mentioned message to be processed includes export parameters, and the export parameters may include the identification of the target product to be synchronized. Therefore, according to the message to be processed, the preset database of the second system can be Obtain the data of the target product to be synchronized.

Using message queue for data export can realize asynchronous export of large amounts of data. For example, if the message queue is not used for data export, after the user triggers the export request using the front-end display interface of the client of the second system, he needs to stay on this interface until the data export is successful; and the user does not need to wait on this interface for this step. , at the same time, the data of other products can also be exported, which facilitates the export of large amounts of data and improves the efficiency of data export, that is, the efficiency of data synchronization.

S204. The server of the second system generates a file to be synchronized based on the acquired data, and sends the file to be synchronized to the client of the second system.

Wherein, the above-mentioned files to be synchronized are the files to be synchronized mentioned in the previous embodiment.

For example, the file to be synchronized is generated based on the acquired data and a preset file generation function. And the file to be synchronized is sent to the client of the second system.

In one example, the server of the second system can directly send the file to be synchronized to the client of the second system; or the server of the second system can upload the file to be synchronized to the second system. In the second intermediate system corresponding to the system, receive the storage address returned by the second intermediate system, download the file to be synchronized from the second intermediate system according to the storage address, and record the storage address in the export log .

In this embodiment, by using the message queue, the server of the second system obtains the data of the target product to be synchronized, generates the file to be synchronized, and sends it to the client of the second system for storage, so as to facilitate subsequent data import. This method uses a message queue to export data, and can export data of multiple groups of target products to be synchronized at the same time, reducing waiting time and improving data synchronization efficiency.

Figure 4 is a schematic flowchart of a cross-environment data synchronization method provided by this application. As shown in Figure 4, the method includes:

S301. The client of the second system sends an export request to the server of the second system.

Correspondingly, the server of the second system receives an export request initiated by the client of the second system, where the export request is used to indicate that the data of the target commodity to be synchronized needs to be exported, and the export request carries export parameters.

S302. The server of the second system generates an export log based on the export parameter.

For description of this step, reference may be made to the aforementioned step S201, which will not be described again here.

S303. The server of the second system generates a message to be processed according to the export log, and sends the message to be processed to a message queue; wherein the message queue includes at least one message to be processed.

For description of this step, reference may be made to the aforementioned step S202, which will not be described again here.

S304. The server of the second system obtains the messages to be processed in the preset message queue; and obtains data from the preset database according to the obtained messages to be processed; wherein the preset database includes data of at least one commodity.

For description of this step, reference may be made to the aforementioned step S203, which will not be described again here.

S305. The server of the second system generates a file to be synchronized based on the acquired data, and sends the file to be synchronized to the client of the second system.

For description of this step, reference may be made to the aforementioned step S204, which will not be described again here.

S306. The client of the first system sends an import request to the server of the first system.

Correspondingly, the server of the first system obtains an import request, where the import request is used to indicate obtaining the file to be synchronized.

S307. The server of the first system obtains the file to be synchronized according to the import request.

For example, as mentioned above, the client of the first system and the client of the second system are deployed on the same electronic device. Therefore, the electronic device where the client of the first system is located stores the to-be-used information. Synchronized files. The client of the above-mentioned first system can receive the files to be synchronized triggered by the user and generate the import request, and the import request includes the files to be synchronized.

S308. The server of the first system determines multiple entities to be imported in the database of the first system based on the file to be synchronized.

Among them, each entity to be imported represents each data; the entity to be imported has attributes and attribute values.

For description of this step, reference may be made to the aforementioned step S102, which will not be described again here.

S309. If the server of the first system determines that the multiple entities to be imported include all entities in the preset first data table, it converts the identifiers of the entities to be imported into the corresponding entities in the first data table. The identifier of the entity is used to obtain the converted entity to be imported.

The first data table includes the designated entity of the database of the first system and the identifier of the designated entity.

For description of this step, reference may be made to the aforementioned step S103, which will not be described again here.

S310. The server of the first system stores the converted entity to be imported in the database of the first system according to the converted identification of the entity to be imported.

For description of this step, reference may be made to the aforementioned step S104, which will not be described again here.

In this embodiment, the server of the second system exports the data of the target commodity to be synchronized in the second system from the database of the second system using the message queue, generates the file to be synchronized, and sends it to The electronic device where the client of the second system is located is stored; the client of the first system, which is located on the same electronic device, responds to the file to be synchronized triggered by the user and sends the file to be synchronized to the server of the first system for processing. The server of the first system converts the data in the file to be synchronized into the identity of the entity in the database of the first system, and stores the data in the file to be synchronized in the database of the first system according to the identity of the entity. middle. Compared with the existing method of using specific templates for data import, this method can not only export multiple sets of data of target commodities to be synchronized from the database of the second system at the same time, but also conveniently import it to the third system. In the database of one system, the efficiency of data synchronization is improved.

Figure 5 is a schematic flowchart of a cross-environment data synchronization method provided by this application. As shown in Figure 5, the method includes:

S401. The server of the second system receives an export request initiated by the client of the second system. The export request is used to indicate that the data of the target commodity to be synchronized needs to be exported. The export request carries export parameters; and based on the Export parameters generate export logs.

The above-mentioned export parameters include the identification of the target product to be synchronized; the above-mentioned export log includes the identification of the export log, the export parameters and the export status; the above-mentioned export status indicates whether the export data is successful.

For example, after the export log is generated, the export status of the export log is set to exporting.

For description of this step, please refer to the aforementioned step S201.

S402. The server of the second system generates the message to be processed based on the export log identifier being the message primary key and the export parameter being the message body.

It should be noted that this application does not limit how to generate the form of the message to be processed. For details, please refer to the existing technology.

S403. The server of the second system sends the message to be processed to a message queue; wherein the message queue includes at least one message to be processed.

For example, the first module of the aforementioned second system may send the message to be processed to the server of the message queue for storage.

S404. The server of the second system obtains the messages to be processed in the preset message queue; and obtains data from the preset database according to the obtained messages to be processed; wherein the above-mentioned preset database includes data of at least one commodity.

For example, it can be the second module of the aforementioned second system that regularly obtains data from the server of the message queue. For description of this step, please refer to the aforementioned step S203.

S405. The server of the second system encrypts the acquired data and obtains encrypted data.

This step can improve the security of your data. For example, encryption algorithms such as Cipher encryption algorithm and asymmetric encryption can be used for encryption, and the application is not limited here. Take the Cipher encryption algorithm as an example. This encryption algorithm requires setting a key and a random number seed. The configuration center of the second system presets the key of the encryption algorithm; the random number can be generated by the SHA1PRNG algorithm, which uses the SHA-1 hash function to hash the seed data and uses the calculation result as the random number generator. seed.

Optionally, if the data is data of multiple target products, the data of the multiple target products are encrypted respectively.

S406. The server of the second system encapsulates the encrypted data to obtain the file to be synchronized.

For example, the server of the second system encapsulates the encrypted data into a file according to a preset file encapsulation interface.

Optionally, if the data is data for multiple target products, encrypt the encrypted data separately to obtain multiple files.

S407. The server of the second system uploads the file to be synchronized to the second intermediate system corresponding to the second system.

It should be noted that this application does not limit the communication method between the server of the second system and the second intermediate system.

S408. The server of the second system receives the storage address of the file to be synchronized returned by the second intermediate system, writes the storage address of the file to be synchronized into the log to be exported, and determines that the export status is export successful.

Among them, the above storage address is used to obtain the file to be synchronized.

S409. The server of the second system downloads the file to be synchronized from the second intermediate system according to the storage address of the file to be synchronized; and sends the file to be synchronized to the client of the second system.

This step can facilitate the asynchronous export of target product data to be synchronized. After exporting the data, you only need to determine the export log and the export status in the export log to determine whether the data was successfully exported and store it based on the file in the export log. Address, download the file to be synchronized from the second intermediate system, without waiting in the export interface, which improves data synchronization efficiency.

S410. The server of the first system obtains an import request, where the import request is used to indicate obtaining the file to be synchronized.

For example, the above import request carries import parameters and files to be synchronized.

S411. The server of the first system uploads the files to be synchronized to the first intermediate system corresponding to the first system.

This step can facilitate subsequent processing to obtain the file to be synchronized. It should be noted that this application does not limit the communication method between the server of the first system and the first intermediate system.

S412. The server of the first system receives the storage address of the file to be synchronized returned by the first intermediate system, and generates an import log according to the import parameters sent by the client of the first system and the storage address of the file to be synchronized. .

For example, the above-mentioned import log may include the identification of the import log, the storage address of the file to be synchronized, and the import parameters.

S413. The server of the first system downloads the file to be synchronized from the first intermediate system corresponding to the first system according to the storage address of the file to be synchronized in the import log.

S414. The server of the first system decrypts the file to be synchronized and obtains each decrypted data.

The above-mentioned files to be synchronized include data of target commodities to be synchronized; wherein, each decrypted data is each entity to be synchronized; the entities to be synchronized are entities of the database of the second system; the entities to be synchronized have attributes. and attribute values.

For example, the decryption algorithm corresponding to the encryption algorithm used in step S405 can be used for decryption. For example, if the Cipher encryption algorithm is used for encryption, the key of the encryption algorithm can be obtained from the configuration center of the first system.

S415. The server of the first system converts the entities to be synchronized into entities to be imported into the database of the first system according to the preset second data table.

The above-mentioned second data table includes a correspondence relationship between entities to be synchronized in the database of the second system and entities to be imported in the database of the first system.

Illustratively, Table 1 is an example of the content of the second data table.

Table 1

S416. The server of the first system filters the entities to be imported in the database of the first system according to the preset third data table.

It should be understood that there may be redundant data in the entities to be imported. The redundant data refers to data that does not need to be stored in the database of the first system. Therefore, in order to improve subsequent storage efficiency, the entities to be imported can be Entities are filtered.

In one example, the above-mentioned third data table includes redundant entities to be imported. Therefore, the entities to be imported can be traversed. If the entities to be imported exist in the third data table, the entities to be imported are Entity deletion; it may also be that the above-mentioned third data table includes the entities required by the database of the above-mentioned first system, and the above-mentioned entities to be imported are traversed. If the entities to be imported do not exist in the third data table, then the entities to be imported are The entities to be imported are deleted.

S417. The server of the first system determines whether the multiple entities to be imported include all entities in the preset first data table.

Wherein, the above-mentioned first data table includes the designated entity of the database of the first system and the identifier of the designated entity.

If it is determined that the multiple entities to be imported include all entities in the preset first data table, it means that the verification of the entities to be imported is correct, then step S418 is executed; if it is determined that the multiple entities to be imported do not include the preset entities. If any entity in the first data table indicates that the entity to be imported has a verification error, step S421 is executed.

S418. The server of the first system converts the identifier of the entity to be imported into the identifier of the corresponding entity in the first data table, and obtains the converted entity to be imported.

Optionally, the above import request carries import parameters; the above import parameters include the import type and the import information corresponding to the import type. The import type can be, for example, new, update, etc. The import information corresponding to the import type, taking the import type as new as an example, the import information can be, for example, the classification information of the target product to be synchronized; if the import type is When updating, the imported information may be, for example, the identification of the target product to be synchronized, or the classification information of the target product to be synchronized.

Illustratively, the client of the first system receives the files to be synchronized, the import type, and the import information corresponding to the import type input by the user. Optionally, the above-mentioned preset first data table may also include other product information in the database of the first system, such as classification information, product names, etc. After the server of the above-mentioned first system receives the above-mentioned import request sent by the client of the above-mentioned first system, after determining that the multiple entities to be imported include all entities in the preset first data table, according to the import To request and match the preset first data table to the data in the database of the above-mentioned first system, the following situations may exist:

The first situation: If the above-mentioned import type is an update type, then according to the preset matching rules and the import information corresponding to the update type, the amount of data in the database of the above-mentioned first system corresponding to the entity to be imported is determined;

(1) When it is determined that the number of data in the database of the first system corresponding to the entity to be imported is one, then the identifier of the entity to be imported is converted into the identifier of the corresponding entity in the first data table, and the conversion is obtained The entities to be imported later.

For example, the above-mentioned preset matching rules may be, for example, matching the identifier of the target product to be synchronized, or may be matching the identifier and name of the target product to be synchronized, which is again not limited in this application. When it is determined that the number of data in the database of the first system corresponding to the entity to be imported is one, it means that the entity to be imported can uniquely match the data in the database of the first system. Therefore, the entity to be imported can be uniquely matched with the data in the database of the first system. The identifier of the imported entity is converted into the identifier of the corresponding entity in the first data table.

(2) When it is determined that the number of data in the database of the first system corresponding to the entity to be imported is greater than one, then output the data in the database of the first system corresponding to the entity to be imported to the client of the first system , and obtain the data in the database of the final corresponding first system selected by the user; use the data in the database of the final corresponding first system to update the files to be synchronized; and repeat the execution to determine the first system based on the files to be synchronized. Steps for multiple entities to be imported from the database.

For example, when it is determined that the number of data in the database of the first system corresponding to multiple entities to be imported is greater than one, it means that the entities to be imported cannot uniquely match the data in the database of the first system. Therefore, , the data to be updated in the database of the first system cannot be determined, and the matched data in the database of the first system corresponding to the entity to be imported needs to be output to the client of the first system, so that the user can pass the above The client of the first system makes a selection, and returns the final corresponding data in the database of the first system determined by the user through the client of the first system, and uses the final corresponding data in the database of the first system to update the data to be synchronized The corresponding data item in the file. For example, according to the above preset matching rules, two different pieces of data are matched, namely data 1 and data 2. Finally, the corresponding data in the database of the first system is data 1, then the above to be synchronized is modified according to data 1. The attribute value of the corresponding entity to be synchronized in the file is the value corresponding to data 1, and returns to execution S415. When this step is performed again, according to the preset matching rules, the updated entity to be imported can be uniquely matched to the data in the database of the first system to obtain the converted entity.

It should be noted that if the file to be synchronized is not stored in the previous steps, you can return to step 13 to download the file to be synchronized from the first intermediate system corresponding to the first system and then update it.

Second case: If it is determined that the multiple entities to be imported include all entities in the preset first data table, and the import type is a new type, then according to the import information corresponding to the new type, the entities to be imported will be The identity of the entity is converted into the identity of the corresponding entity in the first data table, and the converted entity to be imported is obtained.

For example, if the above-mentioned import type is new, it means that there is no historical data of the entity to be imported in the database of the above-mentioned first system. Therefore, the entity to be imported can be added according to the import information corresponding to the new type. The identifier is converted into the identifier of the corresponding entity in the first data table, and the converted identifier of the entity to be imported is obtained. For example, the above-mentioned imported information is classification information. According to the classification information, the identifier of the entity corresponding to the classification information in the above-mentioned first data table can be determined, and the entity to be imported can be converted into the identifier of the entity corresponding to the classification information.

S419. The server of the first system generates multiple data sets based on the preset fourth data table and the converted identifier of the entity to be imported.

Among them, the above-mentioned fourth data table includes a preset data set, the converted identification of the entity to be imported, and the data table of the database of the first system, and the corresponding relationship between the three; the above-mentioned data set includes multiple transformations The entities to be imported later.

For example, the above fourth data table may be as shown in Table 2.

Table 2

Converted entities to be imported data collection data sheet Logo 1 Collection 1 Datasheet 1

S420. The server of the first system stores the multiple converted entities to be imported in the data set into the corresponding data table of the database of the first system based on the thread corresponding to the data set.

For example, the thread corresponding to the data set may be temporarily allocated by the server of the first system to the data set, or may be a preset thread corresponding to the data set. For example, the thread corresponding to the data set may be in the fourth data table. Includes correspondence between data collection threads. This method can achieve parallel storage and improve data synchronization efficiency.

Optionally, if the environment where the first system is deployed is a production environment, that is, the data of the second system in the non-production environment is synchronized to the first system in the production environment, and the data of the first system in the production environment is synchronized. Before success, the status of the products in the synchronized database in the first system of this version is set to the off-shelf status.

S421. The server of the first system returns prompt information to the client of the first system. The above prompt information indicates that the import of data has failed.

For example, the above prompt information may be in the form of text information, or may be sound and light alarm information, etc., which is not limited in this application.

Optionally, the above-mentioned first system and second system can be configured to periodically clear caches so that they can be updated with synchronized data.

In this embodiment, the server of the second system is first used to export the data of the target product to be synchronized in the second system from the database of the second system using the message queue, and then encrypted and encapsulated to generate the data of the target product to be synchronized. The file is sent to the electronic device where the client of the second system is located for storage; and then the client of the first system located on the same electronic device is used to respond to the file to be synchronized triggered by the user and send the file to be synchronized to the first system. The server of the first system performs processing. The server of the first system decrypts, filters, verifies and matches the data in the file to be synchronized and then converts it into an identifier of an entity in the database of the first system. According to the entity's identification, and store the data in the files to be synchronized in the database of the first system in parallel. Compared with the existing method of using a specific template for data import, this method will use the first system and the second system located in different environments to deploy the client of the first system and the client of the second system. The electronic device realizes cross-environment data synchronization. It can not only export multiple sets of target product data to be synchronized from the database of the second system at the same time, but also import it into the database of the first system in parallel, improving the efficiency of data synchronization. At the same time, it can also improve the security of data synchronization.

Figure 6 is a schematic structural diagram of a cross-environment data synchronization device provided by this application. The device is applied to the server of the first system. As shown in Figure 6, the device 50 includes:

The acquisition unit 51 is used to obtain an import request, where the import request is used to instruct the acquisition of files to be synchronized; and to acquire the files to be synchronized according to the import request;

Determining unit 52, configured to determine multiple entities to be imported in the database of the first system according to the files to be synchronized; wherein each entity to be imported represents each data; the entity to be imported has Properties and property values;

The conversion unit 53 is configured to convert the identification of the entity to be imported into the corresponding entity in the first data table when it is determined that the multiple entities to be imported include all entities in the preset first data table. The identification of the converted entity to be imported is obtained; wherein the first data table includes the designated entity of the database of the first system and the identification of the designated entity;

The storage unit 54 is configured to store the converted entity to be imported into the database of the first system according to the identification of the converted entity to be imported.

The cross-environment data synchronization device provided by this application can execute the cross-environment data synchronization method in the above method embodiment. Its implementation principles and technical effects are similar and will not be described again here.

Figure 7 is a schematic structural diagram of a cross-environment data synchronization device provided by this application. The device is applied to the server of the first system. As shown in Figure 7, the device 60 includes:

The acquisition unit 61 is used to obtain an import request, where the import request is used to instruct the acquisition of files to be synchronized; and to acquire the files to be synchronized according to the import request;

Determining unit 62, configured to determine multiple entities to be imported in the database of the first system according to the files to be synchronized; wherein each entity to be imported represents each data; the entity to be imported has Properties and property values;

The conversion unit 63 is configured to convert the identification of the entity to be imported into the corresponding entity in the first data table when it is determined that the multiple entities to be imported include all entities in the preset first data table. The identification of the converted entity to be imported is obtained; wherein the first data table includes the designated entity of the database of the first system and the identification of the designated entity;

The storage unit 64 is configured to store the converted entity to be imported into the database of the first system according to the identification of the converted entity to be imported.

In one example, the above-mentioned import request carries import parameters; the import parameters include the import type and the import information corresponding to the import type; the above-mentioned conversion unit 63 includes:

The determination module 631 is configured to, when it is determined that the multiple entities to be imported include all entities in the preset first data table, and the import type is an update type, according to the preset matching rules and the update type corresponding Import information to determine the amount of data in the database of the first system corresponding to the entity to be imported;

The first conversion module 632 is configured to convert the identification of the entity to be imported into the first system when it is determined that the number of data in the database of the first system corresponding to the entity to be imported is one. The identification of the corresponding entity in the data table is used to obtain the converted entity to be imported; when it is determined that the number of data in the database of the first system corresponding to the entity to be imported is greater than one, the entity to be imported is The data in the database of the first system corresponding to the entity is output to the client of the first system, and the final corresponding data in the database of the first system selected by the user is obtained; using the final corresponding data update the files to be synchronized based on the data in the database of the first system; and repeatedly execute the step of determining multiple entities to be imported into the database of the first system based on the files to be synchronized.

In one example, the above-mentioned determination module 631 is configured to determine that the multiple entities to be imported include all entities in the preset first data table, and the import type is a new type, corresponding to the new type. Import information, convert the identifier of the entity to be imported into the identifier of the corresponding entity in the first data table, and obtain the converted entity to be imported.

In one example, the import request carries import parameters and files to be synchronized; the above-mentioned acquisition unit 61 includes:

The upload module 611 is used to upload the file to be synchronized to the first intermediate system corresponding to the first system;

The receiving module 612 is configured to receive the storage address of the file to be synchronized returned by the first intermediate system, and to receive the storage address of the file to be synchronized according to the import parameters sent by the client of the first system and the storage address of the file to be synchronized. , generate import log;

The download module 613 is configured to download the file to be synchronized from the first intermediate system corresponding to the first system according to the storage address of the file to be synchronized in the import log.

In one example, the file to be synchronized includes data of the target commodity to be synchronized; the above-mentioned determination unit 62 includes,

The decryption module 621 is used to decrypt the file to be synchronized to obtain each decrypted data; wherein each decrypted data is each entity to be synchronized; the entity to be synchronized is the third entity. Entities in the database of the two systems; the entities to be synchronized have attributes and attribute values;

The second conversion module 623 converts entities to be synchronized into entities to be imported into the database of the first system according to the preset second data table; wherein the second data table includes the second Correspondence between entities to be synchronized in the database of the system and entities to be imported in the database of the first system.

In one example, the above device may further include a filtering unit 65 for filtering entities to be imported in the database of the first system according to a preset third data table.

In one example, the determination module 631 in the above-mentioned conversion unit 63 can also be used to, when it is determined that the plurality of entities to be imported does not include any entity in the preset first data table, to the first system. The client returns prompt information, which indicates that the data import has failed.

In one example, the above-mentioned storage unit 64 includes:

The generation module 641 is configured to generate multiple data sets according to the preset fourth data table and the converted identification of entities to be imported; wherein the fourth data table includes the preset data set, the converted The correspondence between the identification of the entity to be imported and the data table of the database of the first system; the data set includes multiple converted entities to be imported;

The storage module 642 is configured to store multiple converted entities to be imported in the data set into the corresponding data table of the database of the first system based on the thread corresponding to the data set.

The cross-environment data synchronization device provided by this application can execute the cross-environment data synchronization method in the above method embodiment. Its implementation principles and technical effects are similar and will not be described again here.

Figure 8 is a schematic structural diagram of a cross-environment data synchronization device provided by this application. This device is applied to the server of the second system. As shown in Figure 8, the device 70 includes:

The receiving unit 71 is configured to receive an export request initiated by the client of the second system, wherein the export request is used to indicate that the data of the target commodity to be synchronized needs to be exported, and the export request carries export parameters; and Generate an export log based on the export parameters;

Generating unit 72, configured to generate a message to be processed according to the export log, and send the message to be processed to a message queue; wherein the message queue includes at least one message to be processed;

The acquisition unit 73 is used to acquire messages to be processed in the preset message queue; and to acquire data from a preset database according to the acquired messages to be processed; wherein the preset database includes data of at least one commodity;

A sending unit 74, configured to generate a file to be synchronized based on the acquired data, and send the file to be synchronized to the client of the second system;

Wherein, the file to be synchronized is the file to be synchronized as described in any of the preceding items.

The cross-environment data synchronization device provided by this application can execute the cross-environment data synchronization method in the above method embodiment. Its implementation principles and technical effects are similar and will not be described again here.

Figure 9 is a schematic structural diagram of a cross-environment data synchronization device provided by this application. This device is applied to the server of the second system. As shown in Figure 9, the device 80 includes:

The receiving unit 81 is configured to receive an export request initiated by the client of the second system, wherein the export request is used to indicate that the data of the target commodity to be synchronized needs to be exported, and the export request carries export parameters; and Generate an export log based on the export parameters;

Generating unit 82, configured to generate a message to be processed according to the export log, and send the message to be processed to a message queue; wherein the message queue includes at least one message to be processed;

The acquisition unit 83 is used to acquire the messages to be processed in the preset message queue; and to acquire data from the preset database according to the acquired messages to be processed; wherein the preset database includes data of at least one commodity;

A sending unit 84, configured to generate a file to be synchronized based on the acquired data, and send the file to be synchronized to the client of the second system;

Wherein, the file to be synchronized is the file to be synchronized as described in any of the preceding items.

In one example, the export parameters include the identification of the target product to be synchronized; the export log includes the identification of the export log, the export parameters, and the export status; the export status indicates whether the export data is successful.

In one example, the generating unit 82 is configured to generate the message to be processed based on the identifier of the export log being the message primary key and the export parameter being the message body.

In one example, the above sending unit 84 includes:

The encryption module 841 is used to encrypt the obtained data to obtain encrypted data;

The encapsulation module 842 is used to encapsulate the encrypted data to obtain the file to be synchronized.

In one example, the above sending unit 84 includes:

Upload module 843, used to upload the file to be synchronized to the second intermediate system corresponding to the second system;

The receiving module 844 is configured to receive the storage address of the file to be synchronized returned by the second intermediate system, and write the storage address of the file to be synchronized into the export log, and determine that the export status is The export is successful; where the storage address is used to obtain the file to be synchronized;

Sending module 845, configured to download the file to be synchronized from the second intermediate system according to the storage address of the file to be synchronized; and send the file to be synchronized to the client of the second system end.

The cross-environment data synchronization device provided by this application can execute the cross-environment data synchronization method in the above method embodiment. Its implementation principles and technical effects are similar and will not be described again here.

Figure 10 is a schematic structural diagram of an electronic device provided by this application. As shown in FIG. 10 , the electronic device may include at least one processor 901 and a memory 902 , and may be, for example, a computer, a tablet, or other electronic device with processing capabilities.

Memory 902 is used to store programs. Specifically, the program may include program code, which includes computer operating instructions. The memory 902 may include high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The processor 901 is configured to execute computer execution instructions stored in the memory 902 to implement the cross-environment data synchronization method described in the foregoing method embodiments. The processor 901 may be a central processing unit (Central Processing Unit, CPU for short), an application specific integrated circuit (ASIC for short), or one or more processors configured to implement the embodiments of the present application. integrated circuit.

The electronic device 900 may also include a communication interface 903 to communicate and interact with external devices through the communication interface 903 . The external device may be, for example, a computer, a tablet, a mobile phone, etc.

In terms of specific implementation, if the communication interface 903, the memory 902 and the processor 901 are implemented independently, the communication interface 903, the memory 902 and the processor 901 can be connected to each other through a bus and complete mutual communication. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc., but it does not mean that there is only one bus or one type of bus.

Optionally, in terms of specific implementation, if the communication interface 903, the memory 902 and the processor 901 are integrated on one chip, the communication interface 903, the memory 902 and the processor 901 can complete communication through the internal interface.

This application also provides a computer-readable storage medium. The computer-readable storage medium may include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory) , magnetic disks, optical disks, and other media that can store program codes. Specifically, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used for the cross-environment data synchronization method in the above embodiment.

The application also provides a computer program product, the computer program product includes execution instructions, and the execution instructions are stored in a readable storage medium. At least one processor of the electronic device 900 can read the execution instruction from the readable storage medium, and the at least one processor executes the execution instruction so that the electronic device 900 implements the cross-environment data synchronization method provided by the various embodiments described above.

This application also provides a chip. A computer program is stored on the chip. When the computer program is executed by the chip, the cross-environment data synchronization method provided by various embodiments is implemented.

It should be noted that for the sake of simple description, the foregoing method embodiments are expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence. Because in accordance with this application, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily necessary for this application.

It should be further noted that although the steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this article, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least some of the steps in the flow chart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but may be executed at different times. The execution of these sub-steps or stages The sequence is not necessarily sequential, but may be performed in turn or alternately with other steps or sub-steps of other steps or at least part of the stages.

It should be understood that the above device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units/modules in the above embodiment is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components may be combined, or may be integrated into another system, or some features may be omitted or not performed.

In addition, unless otherwise specified, each functional unit/module in each embodiment of the present application can be integrated into one unit/module, or each unit/module can exist physically alone, or there can be two or more units/modules. Modules are integrated together. The above integrated units/modules can be implemented in the form of hardware or software program modules.

In the above embodiments, each embodiment is described with its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined in any way. To simplify the description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, all possible combinations should be used. considered to be within the scope of this manual

Other embodiments of the present application will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary technical means in the technical field that are not disclosed in this application. . It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise structures described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (17)

1. A cross-environment data synchronization method, wherein the method is applied to a server side of a first system, and the method comprises:

acquiring an import request, wherein the import request is used for indicating acquisition of a file to be synchronized; acquiring files to be synchronized according to the importing request;

determining a plurality of entities to be imported of the database of the first system according to the files to be synchronized; wherein each entity to be imported characterizes each data; the entity to be imported has an attribute and an attribute value;

if the plurality of entities to be imported comprise all entities in a preset first data table, converting the identification of the entity to be imported into the identification of the corresponding entity in the first data table to obtain the converted entity to be imported; wherein the first data table comprises a designated entity of a database of the first system and an identifier of the designated entity;

And storing the converted entity to be imported into a database of the first system according to the identification of the converted entity to be imported.

2. The method according to claim 1, wherein the import request carries an import parameter; the import parameters comprise an import type and import information corresponding to the import type; if it is determined that the plurality of entities to be imported include all entities in a preset first data table, converting the identifier of the entity to be imported into the identifier of the corresponding entity in the first data table, and obtaining the converted entity to be imported, where the converting includes:

if the plurality of entities to be imported comprise all entities in a preset first data table, and the import type is an update type, determining the quantity of data in a database of the first system corresponding to the entity to be imported according to a preset matching rule and import information corresponding to the update type;

when the number of the data in the database of the first system corresponding to the entity to be imported is determined to be one, converting the identification of the entity to be imported into the identification of the corresponding entity in the first data table to obtain the converted entity to be imported;

When the number of the data in the database of the first system corresponding to the entity to be imported is determined to be more than one, outputting the data in the database of the first system corresponding to the entity to be imported to a client of the first system, and acquiring the data in the database of the first system, which is selected by a user and corresponds to the end; updating the file to be synchronized by utilizing the data in the final corresponding database of the first system; and repeatedly executing the step of determining a plurality of entities to be imported of the database of the first system according to the files to be synchronized.

3. The method according to claim 2, wherein the method further comprises:

if it is determined that all entities in the preset first data table are included in the plurality of entities to be imported, and the import type is a new type, according to import information corresponding to the new type, converting the identification of the entity to be imported into the identification of the corresponding entity in the first data table, and obtaining the converted entity to be imported.

4. The method according to claim 1, wherein the import request carries an import parameter and a file to be synchronized; according to the importing request, acquiring the file to be synchronized, including:

Uploading the file to be synchronized to a first intermediate system corresponding to the first system;

receiving a storage address of the file to be synchronized returned by the first intermediate system, and generating an import log according to an import parameter sent by a client of the first system and the storage address of the file to be synchronized;

and downloading the file to be synchronized from a first intermediate system corresponding to the first system according to the storage address of the file to be synchronized in the import log.

5. The method according to claim 1, wherein the file to be synchronized includes data of the target commodity to be synchronized; according to the file to be synchronized, determining a plurality of entities to be imported of the database of the first system, including:

decrypting the file to be synchronized to obtain each decrypted data; wherein each decrypted data is each entity to be synchronized; the entity to be synchronized is an entity of a database of the second system; the entity to be synchronized has an attribute and an attribute value;

according to a preset second data table, converting the entity to be synchronized into an entity to be imported of the database of the first system; the second data table includes a correspondence between an entity to be synchronized of the database of the second system and an entity to be imported of the database of the first system.

6. The method according to claim 5, wherein after converting the entity to be synchronized into the entity to be imported of the database of the first system according to a preset second data table, the method further comprises:

and filtering the entity to be imported of the database of the first system according to a preset third data table.

7. The method according to any one of claims 1-5, further comprising:

if the fact that any entity in the preset first data table is not included in the plurality of entities to be imported is determined, prompt information is returned to the client of the first system, and the prompt information represents that the importing of the data fails.

8. The method according to any of claims 1-5, wherein storing the converted entity to be imported into the database of the first system according to the identification of the converted entity to be imported comprises:

generating a plurality of data sets according to a preset fourth data table and the converted identity of the entity to be imported; the fourth data table comprises a preset data set, a converted identity of an entity to be imported and a data table of a database of the first system, wherein the corresponding relation among the data set, the converted identity of the entity to be imported and the data table of the database of the first system; the data set comprises a plurality of converted entities to be imported;

And storing a plurality of converted entities to be imported in the data set into a data table of a database of the corresponding first system based on the threads corresponding to the data set.

9. A cross-environment data synchronization method, wherein the method is applied to a server side of a second system, and the method comprises:

receiving an export request initiated by a client of the second system, wherein the export request is used for indicating data of a target commodity to be exported, and export parameters are carried in the export request; and generating an export log based on the export parameters;

generating a message to be processed according to the derived log, and sending the message to be processed to a preset message queue; wherein the message queue comprises at least one message to be processed;

acquiring a message to be processed in the preset message queue; according to the acquired message to be processed, acquiring data from a preset database; wherein the preset database comprises data of at least one commodity;

generating a file to be synchronized according to the acquired data, and sending the file to be synchronized to a client of the second system;

Wherein the file to be synchronized is the file to be synchronized according to any one of claims 1-8.

10. The method of claim 9, wherein the derived parameters include an identification of a target commodity to be synchronized; the export log comprises an identification of the export log, export parameters and export states; the export state characterizes whether the export data was successful.

11. The method of claim 9, wherein generating a message to be processed from the export log comprises:

and generating the message to be processed based on the mark of the derived log as a message primary key and the derived parameter as a message body.

12. The method according to any of claims 9-11, wherein generating a file to be synchronized from the acquired data comprises:

encrypting the acquired data to obtain encrypted data;

and packaging the encrypted data to obtain the file to be synchronized.

13. The method according to any of claims 9-11, wherein sending the file to be synchronized to the client of the second system comprises:

uploading the file to be synchronized to a second intermediate system corresponding to the second system;

Receiving a storage address of the file to be synchronized returned by the second intermediate system, writing the storage address of the file to be synchronized into the export log, and determining that the export state is export success; the storage address is used for acquiring files to be synchronized;

downloading the file to be synchronized from the second intermediate system according to the storage address of the file to be synchronized; and sending the file to be synchronized to the client of the second system.

14. A cross-environment data synchronization device, wherein the device is applied to a server side of a first system, and comprises:

an obtaining unit, configured to obtain an import request, where the import request is used to indicate that a file to be synchronized is obtained; acquiring files to be synchronized according to the importing request;

the determining unit is used for determining a plurality of entities to be imported of the database of the first system according to the files to be synchronized; wherein each entity to be imported characterizes each data; the entity to be imported has an attribute and an attribute value;

the device comprises a conversion unit, a first data table and a second data table, wherein the conversion unit is used for converting the identification of the entity to be imported into the identification of the corresponding entity in the first data table when determining that all the entities in the first data table are included in the plurality of entities to be imported, so as to obtain the converted entity to be imported; wherein the first data table comprises a designated entity of a database of the first system and an identifier of the designated entity;

And the storage unit is used for storing the converted entity to be imported into the database of the first system according to the identification of the converted entity to be imported.

15. A cross-environment data synchronization device, wherein the device is applied to a server side of a second system, and comprises:

the receiving unit is used for receiving a export request initiated by a client of the second system, wherein the export request is used for indicating data of target commodities to be synchronized to be exported, and export parameters are carried in the export request; and generating an export log based on the export parameters;

the generating unit is used for generating a message to be processed according to the export log and sending the message to be processed to a preset message queue; wherein the message queue comprises at least one message to be processed;

the acquisition unit is used for acquiring the message to be processed in the preset message queue; according to the acquired message to be processed, acquiring data from a preset database; wherein the preset database comprises data of at least one commodity;

the sending unit is used for generating a file to be synchronized according to the acquired data and sending the file to be synchronized to a client of the second system;

Wherein the file to be synchronized is the file to be synchronized according to any one of claims 1-8.

16. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1 to 13.

17. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1 to 13.