Low-code data format conversion system and low-code data format conversion method

Abstract

Embodiments of the present disclosure disclose a low-code data format conversion system and a low-code data format conversion method. A specific embodiment of the system includes a first system, a second system, a connector, a logic processor, and a pusher, wherein: the connector is configured to acquire data source information of the first system and data format information of the second system in real time or at a timing; the connector is configured to send the data source information and the data format information to the logic processor; the logic processor is configured to perform data format conversion on the data source information according to the data format information to obtain converted data; the logic processor is configured to send the converted data to the pusher; and the pusher is configured to push the converted data to the second system. This embodiment can use a set of general data conversion systems to perform data format conversion between any systems, thereby reducing the workload of developers and the difficulty of later operation and maintenance.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to the technical field of data format conversion, in particular to a low-code data format conversion system and a low-code data format conversion method. BACKGROUND

[0002] Low code is a technology for developing application programs by using visualization, parameter configuration and model-driven concepts. At present, data interaction and synchronization usually exist between systems, and system integration can be used to meet business requirements. Data interaction between systems is generally transmitted in a fixed format, and developers develop corresponding application programs according to the fixed format.

[0003] However, when the above method is used, the following technical problems often exist:

[0004] First, when the integrated systems are too many, the developer needs to customize the development of the system according to the data format of different systems, which increases the workload of the developer, and too many integrated systems make it difficult to uniformly manage data in different formats, which increases the difficulty of later operation and maintenance.

[0005] Second, to complete the data format conversion between different types of systems, the developer needs to write a large amount of code to realize the conversion of the data format, which increases the difficulty of data format conversion, and the efficiency of data format conversion is low. SUMMARY

[0006] The summary part of the present disclosure is used to introduce the concepts in a brief form, which will be described in detail in the specific embodiments part. The summary part of the present disclosure is not intended to identify the key features or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0007] Some embodiments of the present disclosure propose a low-code data format conversion system to solve one or more of the technical problems mentioned in the background part.

[0008] In a first aspect, some embodiments of the present disclosure provide a low-code data format conversion system, comprising a first system, a second system, a connector, a logic processor, and a pusher, wherein: the connector is communicatively connected to the first system and the second system, and is configured to acquire data source information of the first system and data format information of the second system in real time or at a timing; the connector is communicatively connected to the logic processor, and is configured to send the data source information and the data format information to the logic processor; the logic processor is configured to perform data format conversion on the data source information according to the data format information to obtain converted data; the logic processor is communicatively connected to the pusher, and is configured to send the converted data to the pusher; and the pusher is communicatively connected to the second system, and is configured to push the converted data to the second system.

[0009] In some embodiments, the data source information comprises at least one of the following: a hypertext data source, a file data source, a database, a web service data source, and a message queue data source.

[0010] In some embodiments, the connector is configured to be parameterized in a visual manner, and comprises at least one of the following: a file connector, a hypertext connector, and a message queue connector.

[0011] In some embodiments, when the connector is a file connector, connection information is configured in a visual manner; when the connector is a hypertext connector, the hypertext connector calls an authentication center to acquire hypertext interface information for authentication, obtains an authentication result, and in response to determining that the authentication result satisfies a first preset condition, acquires response parameters of the hypertext data source through a template; and when the connector is a message queue connector, to-be-acquired message queue information and topic information are configured in a visual manner.

[0012] In some embodiments, the logic processor comprises an inspector, a filter, a splitter, a selector, a templatizer, and a converter, wherein: the inspector is configured to check whether the data source information satisfies a second preset condition; the filter is configured to eliminate data source information that does not satisfy a third preset condition; the splitter is configured to split the data source information according to a fourth preset condition; the selector is configured to determine a flow direction of the data source information according to a fifth preset condition; the templatizer is configured to perform data conversion through a template; and the converter is configured to perform data conversion using function calculation.

[0013] In some embodiments, the low-code data format conversion system further comprises a container communicatively connected with the converter, wherein the container is configured to: obtain function information and function call entry information, wherein the function information is function information stored in a code repository or function information generated by a function generator, and the function information stored in the code repository is function information customized in a preset software framework; publish the function information to obtain a publishing result, wherein the publishing result includes publishing success and publishing failure; when the publishing result is publishing success, generate callback address information; and perform function calculation according to the function call entry information and the callback address information.

[0014] In some embodiments, the connector is further configured to: obtain configuration information of a user; and send the data source information to the checker, the filter, the splitter, the selector, the templatizer, or the converter randomly according to the configuration information of the user.

[0015] In some embodiments, the low-code data format conversion system further comprises a log management module, wherein the log management module is communicatively connected with the connector, the logic processor, and the pusher, and the log management module is configured to record information generated when the data source information passes through the connector, the logic processor, and the pusher.

[0016] In the second aspect, some embodiments of the present disclosure provide a low-code data format conversion method, which comprises: a connector obtaining data source information of a first system and data format information of a second system in real time or at a timing, wherein the data source information includes at least one of the following: a hypertext data source, a file data source, a database, a web service data source, and a message queue data source, the connector is configured by a visual method, and the connector includes at least one of the following: a file connector, a hypertext connector, and a message queue connector; a logic processor performing data format conversion on the data source information according to the data format information to obtain converted data; and a pusher pushing the converted data to the second system.

[0017] The above various embodiments of the present disclosure have the following beneficial effects: by the low-code data format conversion system of some embodiments of the present disclosure, the data format is converted, the workload of the developer is reduced, and the difficulty of later operation and maintenance is reduced. Specifically, the reason for the increase in the workload of the developer and the increase in the difficulty of later operation and maintenance is that when the integrated systems are too many, the developer needs to customize the development of the system according to the data format of different systems, resulting in an increase in the workload of the developer, and too many integrated systems make it difficult to uniformly manage data in different formats. Based on this, the low-code data format conversion system of some embodiments of the present disclosure. First, the connector can obtain the data source information of the first system and the data format information of the second system in real time or at a fixed time. The first system and the second system can be any system. The number of the first system and the second system is also arbitrary. Thus, the data source information obtained can be determined to be converted into a data format, realizing data conversion between any systems. Then, the connector can send the data source information and the data format information to the logic processor. The logic processor is configured to convert the data format of the data source information according to the data format information to obtain converted data. The logic processor is used to perform a series of logical processing on the data source to convert it into the data format that needs to be converted. Thus, the logic processor can convert the data source information into the data format required by the second system, so that the systems that need to interact with each other do not need to be developed according to the fixed format, reducing the workload of the developer. Then, the logic processor can send the converted data to the pusher, and the pusher can push the converted data to the second system. Thus, the developer does not need to customize the development of the system according to the data format of different systems, but uses the universal data conversion system to convert data, reducing the workload of the developer. The universal data conversion system facilitates the uniform management of data in different formats, reducing the difficulty of later operation and maintenance. BRIEF DESCRIPTION OF DRAWINGS

[0018] The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings in which:

[0019] Figure 1 is an architecture diagram of an exemplary system in which some embodiments of the present disclosure can be configured;

[0020] Figure 2 is a structural schematic diagram of one embodiment of a low-code data format conversion system according to some embodiments of the present disclosure;

[0021] Figure 3 is a structural schematic diagram of yet another embodiment of a low-code data format conversion system according to some embodiments of the present disclosure;

[0022] Figure 4 is a table structure design of a file connector according to some embodiments of the present disclosure;

[0023] Figure 5 is a table structure design of a hypertext connector according to some embodiments of the present disclosure;

[0024] Figure 6 is a schematic diagram of data flow conversion between systems according to some embodiments of the present disclosure;

[0025] Figure 7 is a table structure design of a message queue connector according to some embodiments of the present disclosure;

[0026] Figure 8 is a structural composition diagram of a logical processor according to some embodiments of the present disclosure;

[0027] Figure 9 is a table structure design of function calculation according to some embodiments of the present disclosure;

[0028] Figure 10 is a table structure design of a converter according to some embodiments of the present disclosure;

[0029] Figure 11 is a data processing flowchart of a logical processor according to some embodiments of the present disclosure;

[0030] Figure 12 is a flowchart of some embodiments of a low-code data format conversion method of a low-code data format conversion system according to the present disclosure. DETAILED DESCRIPTION

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

[0032] In addition, it should be noted that only parts related to the invention are shown in the drawings for ease of description. The embodiments and features in the present disclosure can be combined with each other without conflict.

[0033] It should be noted that the terms "first", "second", and the like in the present disclosure are merely intended to distinguish different devices, modules or units, and do not imply the sequence of execution of the functions of these devices, modules or units or the mutual dependency of these devices, modules or units.

[0034] It should be noted that the terms "one", "multiple" in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that "one" or "multiple" should be understood as "one or more" unless otherwise explicitly indicated in the context.

[0035] The names of the messages or information exchanged between the devices in the embodiments of the present disclosure are only for illustrative purposes, and are not intended to limit the scope of the messages or information.

[0036] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0037] Figure 1 An exemplary system architecture 100 of a low-code data format conversion system to which some embodiments of the present disclosure can be applied is shown.

[0038] As shown in Figure 1 The system architecture 100 can include a first system 101, a second system 102, a connector 103, a logic processor 104, a pusher 105, a container 106, a log management module 107, a network 108, a network 109, a network 110, a network 111 and a network 112. The network 108 is a medium for providing a communication link between the first system 101 and the connector 103. The network 109 is a medium for providing a communication link between the connector 103 and the second system 102. The network 110 is a medium for providing a communication link between the connector 103 and the logic processor 104. The network 110 is a medium for providing a communication link between the logic processor 104 and the pusher 105. The network 110 is a medium for providing a communication link between the log management module 107 and the connector 103, the logic processor 104 and the pusher 105. The network 111 is a medium for providing a communication link between the pusher 105 and the second system 102. The network 112 is a medium for providing a communication link between the logic processor 104 and the container 106. The network 108, the network 109, the network 110, the network 111 and the network 112 can include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0039] The connector 103 can interact with the first system 101 through the network 108 to obtain the data source information of the first system in real time or at a timing.

[0040] The connector 103 can interact with the second system 102 through the network 109 to obtain the data format information of the second system in real time or at a timing.

[0041] The connector 103 can interact with the logic processor 104 through the network 110 to send the above-mentioned data source information and the above-mentioned data format information to the above-mentioned logic processor.

[0042] The logic processor 104 can interact with the pusher 105 through the network 110 to send the above-mentioned converted data to the above-mentioned pusher.

[0043] The pusher 105 can interact with the second system 102 through the network 111 to push the above-mentioned converted data to the above-mentioned second system.

[0044] It should be understood that Figure 1 The number of the first system, the second system, the connector, the logic processor, the pusher, the container, the log management module and the network in

[0045] With reference to Figure 2 , a structural schematic diagram of one embodiment of the low-code data format conversion system provided by the present disclosure is shown. As Figure 2 shown, the low-code data format conversion system of the present embodiment can include a first system 1, a second system 2, a connector 3, a logic processor 4 and a pusher 5.

[0046] In some embodiments, the above-mentioned first system 1 and the above-mentioned second system 2 can be any subsystem involved in the low-code data format conversion system. The above-mentioned first system 1 and the above-mentioned second system 2 can include but not limited to an order management system, a logistics management system or a user information management system, etc. Here, in order to convert the data format, the above-mentioned first system and the above-mentioned second system can be systems with different data formats. Here, the number of the above-mentioned first system and the above-mentioned second system is not limited. That is, the above-mentioned first system can be one or more. The above-mentioned second system can be one or more. Thus, the conversion of data format between multiple systems can be achieved.

[0047] In some embodiments, the connector 3 can be a device with information acquisition and transmission functions. The connector 3 can include, but is not limited to, a D-shaped connector, a rectangular connector, a USB connector, and the like. Here, the connector is in communication connection with the first system and the second system. The connector is configured to acquire data source information of the first system and data format information of the second system in real time or at a timing. The data source information can be at least one record in a database relational table. The data source information can include basic information and business information. The basic information can be information related to personnel. The business information can be information related to business. The data format information can include data format conversion information and data transmission requirement information. The data format conversion information can be field requirement information of the record in the second system. The data transmission requirement information can be interface information of the second system receiving information.

[0048] As an example, a record in the relational table can be: {number: 010, name: Zhang San, gender: male, order frequency: 5 times, purchase item category: home textiles, logistics status: normal}. The basic information can be number, name, gender, and the like. The business information can be order frequency, purchase item category, logistics status, and the like. The field requirement information of the record in the second system can be {number, name, logistics status}. Therefore, the data source information {number: 010, name: Zhang San, gender: male, order frequency: 5 times, purchase item category: home textiles, logistics status: normal} needs to be converted to {number: 010, name: Zhang San, logistics status: normal}. The interface of the second system receiving information can have a hypertext transfer interface and a secure file transfer interface. Therefore, the first system can transmit information to the second system through any one of the hypertext transfer interface and the secure file transfer interface. For data required by the system internally, the connector can acquire at a timing. For real-time data generated by the business system and needed to be pushed to the user, the connector can acquire in real time.

[0049] In some embodiments, the logic processor 4 can be a device that converts data sources through a series of logical processes into target data formats. The logic processor 4 can include, but is not limited to, a single-chip microcomputer, a microcomputer, a chip, and the like. For example, a four-core processor, an eight-core processor, and the like. Here, the logic processor is configured to perform data format conversion on the data source information according to the data format information, to obtain conversion data. Here, the logic processor can compare the data format information with the data source information, extract the consistent information, and recombine to obtain the conversion data.

[0050] As an example, the data comparison can be a comparison of fields (number, name, gender, order frequency, purchased item category, logistics status). The consistent comparison (number, name, logistics status) can be extracted, and the specific information of each field is combined. Thus, the data source information {number: 010, name: Zhang San, gender: male, order frequency: 5 times, purchased item category: home textiles, logistics status: normal} can be converted to {number: 010, name: Zhang San, logistics status: normal}.

[0051] In some embodiments, the pusher 5 described above can be a device with information receiving and information sending functions. The pusher 5 described above can include, but is not limited to, a mobile phone, a computer, a tablet computer, and the like. Here, the logical processor is in communication connection with the pusher. The logical processor is configured to send the converted data to the pusher. The pusher is in communication connection with the second system. The pusher is configured to push the converted data to the second system.

[0052] The above various embodiments of the present disclosure have the following beneficial effects: the low-code data format conversion system of some embodiments of the present disclosure converts the data format, thereby reducing the workload of the developer, and at the same time, reducing the difficulty of later operation and maintenance. Specifically, the reason for the increase in the workload of the developer and the increase in the difficulty of later operation and maintenance is that when the integrated systems are too many, the developer needs to customize the development of the system according to the data format of different systems, resulting in an increase in the workload of the developer, and too many integrated systems make it difficult to uniformly manage data of different formats. Based on this, the low-code data format conversion system of some embodiments of the present disclosure. First, the connector can acquire the data source information of the first system and the data format information of the second system in real time or at a fixed time. The first system and the second system can be any system. The number of the first system and the second system is also arbitrary. Thus, the data source information acquired can be determined to be converted into a data format, realizing data conversion between any systems. Then, the connector can send the data source information and the data format information to the logic processor. The logic processor is configured to convert the data format of the data source information according to the data format information, and obtain converted data. The logic processor is used to perform a series of logical processing on the data source, and convert it into a data format that needs to be converted. Thus, the logic processor can convert the data source information into the data format required by the second system, so that the systems that need to interact with each other do not need to be developed according to a fixed format, thereby reducing the workload of the developer. Then, the logic processor can send the converted data to the pusher, and the pusher can push the converted data to the second system. Thus, the developer does not need to customize the development of the system according to the data format of different systems, but uses the universal data conversion system to convert data, thereby reducing the workload of the developer. The universal data conversion system facilitates the uniform management of data of different formats, thereby reducing the difficulty of later operation and maintenance.

[0053] Further reference is made to Figure 3 which shows a structural schematic diagram of one embodiment of the low-code data format conversion system provided by the present disclosure. As Figure 2 the low-code data format conversion system in the embodiment, the low-code data format conversion system in the present embodiment can also include a first system 1, a second system 2, a connector 3, a logic processor 4 and a pusher 5. For specific structural relationship, please refer to Figure 2 the related description in the embodiment, which will not be repeated here.

[0054] As Figure 2The low-code data format conversion system in the embodiment is different from the prior art in that the data source information in the embodiment can include, but is not limited to, the following: a hypertext data source, a file data source, a database, a web service data source, and a message queue data source. The hypertext data source can be a data source that communicates through the hypertext transfer protocol (HTTP). The file data source can be a data source that communicates through the secure file transfer protocol (SFTP). The database can be a data source saved in the local memory. The web service data source can be a data source that communicates through the web service (Web Service). The message queue data source can be a data source that communicates through the message queue (MQ).

[0055] In some embodiments, the connector is configured in a visual manner, and the system can build a basic connection module. Thus, the underlying technical details are shielded from the user as much as possible, the technical complexity is reduced, a simple and easy-to-use development experience is provided for the user, and an out-of-the-box effect is achieved. Figure 2 In some embodiments, the connector is configured in a visual manner, and the system can build a basic connection module. Thus, the underlying technical details are shielded from the user as much as possible, the technical complexity is reduced, a simple and easy-to-use development experience is provided for the user, and an out-of-the-box effect is achieved.

[0056] In some embodiments, the connector is configured in a visual manner, and the system can build a basic connection module. Thus, the underlying technical details are shielded from the user as much as possible, the technical complexity is reduced, a simple and easy-to-use development experience is provided for the user, and an out-of-the-box effect is achieved.

[0057] In some embodiments, the connector is configured in a visual manner, and the system can build a basic connection module. Thus, the underlying technical details are shielded from the user as much as possible, the technical complexity is reduced, a simple and easy-to-use development experience is provided for the user, and an out-of-the-box effect is achieved. Figure 2 In some embodiments, the connector is configured in a visual manner, and the system can build a basic connection module. Thus, the underlying technical details are shielded from the user as much as possible, the technical complexity is reduced, a simple and easy-to-use development experience is provided for the user, and an out-of-the-box effect is achieved. Figure 4 In some embodiments, when the connector is a file connector, the connection information can be configured in a visual manner. The connection information can include a connection address, a port, a username, a password, a login method that can use a password or a key, a specified data source file, a file path, and a file name. However, the file name can change at any time, so the file name can be configured through a custom function. The table structure design of the file connector is as shown in

[0058] In some embodiments, when the connector is a hypertext connector, the hypertext connector can call an authentication center to obtain hypertext interface information for authentication and obtain an authentication result. In response to determining that the authentication result satisfies a first preset condition, a response parameter of the hypertext data source is obtained through a template. The authentication result can include an authentication pass and an authentication fail. The first preset condition can be that the authentication result is an authentication pass.

[0059] As an example, when the hypertext connector described above obtains a hypertext data source, a response template can be configured. The purpose of the response template is to return the response result according to the interface format, which can be implemented using a template language (Freemarker). Hypertext interfaces are used to transmit data communicated using the Hypertext Transfer Protocol. Calling a hypertext interface involves authentication. Therefore, before calling the hypertext interface, a separately configured authentication center is first called to obtain the hypertext interface's message headers, enabling authentication or signature verification. The table structure design of the hypertext connector is as follows: Figure 5 As shown.

[0060] As yet another example, Figure 6 This is a schematic diagram illustrating data flow between systems according to some embodiments of this disclosure. For example... Figure 6 As shown, when the price in system A changes, it needs to call a hypertext interface to notify system B. After system B processes the data, it must return data according to the interface format of system A. Here, system B does not need to modify its application; it only needs to configure the response module using a template language. The aforementioned response module can return response parameters.

[0061] In this embodiment, when the connector is a message queue connector, the message queue information and topic information to be acquired can be configured visually. The message queue information to be acquired can be the name of the message queue. The topic information can be the transmission intermediary between message publishers and subscribers. Message sending and receiving can be achieved through topic information, thereby realizing communication. The table structure design of the message queue connector is as follows: Figure 7 As shown.

[0062] and Figure 2 Unlike the low-code data format conversion system in this embodiment, the logic processor in this embodiment includes a checker, a filter, a splitter, a selector, a templater, and a converter. The checker is configured to check whether the data source information meets a second preset condition; the filter is configured to remove data source information that does not meet a third preset condition; the splitter is configured to split the data source information according to a fourth preset condition; the selector is configured to determine the flow direction of the data source information according to a fifth preset condition; the templater is configured to perform data conversion using a template; and the converter is configured to perform data conversion using function computation. Optionally, each component of the logic processor can be deployed as multiple nodes, providing services independently, thereby improving the system's data processing efficiency. The structure of the logic processor is as follows: Figure 8 As shown.

[0063] The second preset condition can be that basic information in the data source information meets user demand. The condition set by the user according to actual demand can be that a field value is not empty, or data cannot exceed a specified enumeration range, and the like. For example, the value of a gender field (sex) can be 1 and 2, and the data source information is checked by using a language expression. If the value of the gender field included in the data source information is 3, the second preset condition is not met, and the record is deleted or an exception is thrown.

[0064] The third preset condition can be that business information in the data source information meets user demand. For example, the business information that meets user demand can be that a logistics state is normal, and the data source information is checked by using a language expression. If the logistics state included in the data source information is abnormal, the third preset condition is not met, and the record is deleted or an exception is thrown. The user can configure a routing rule by using Camel. Camel is a powerful rule-based routing and media engine.

[0065] The fourth preset condition can be information about requirements of data formats of various systems. Information about requirements of data formats of various systems can be set by using a language expression. The language expression can use an object navigation graph language (OGNL) or a Groovy syntax. Groovy is an agile development language based on a Java virtual machine. For example, an order in an online-to-offline mode needs to be synchronized to an order center and a performance center. Therefore, the order can be split into two different pieces of data according to the type of the order. The two different pieces of data can be {name: Zhang San, order placing frequency: 5 times, purchased article category: home textiles, logistics state: normal} and {number: 010, name: Zhang San, gender: male, order placing frequency: 5 times, logistics state: normal}.

[0066] The fifth preset condition can be information about interface requirements of various systems for received data. Information about interface requirements of various systems for received data can be set by using a language expression. The language expression can use an object navigation graph language (OGNL) or a Groovy syntax.

[0067] The template generator can perform data conversion by using a template. The template can be a script language written by using Freemarker, Velocity, or Beetl to implement data conversion. Freemarker is a general tool for generating output text based on a template and data that needs to be changed. Velocity is a template engine based on Java. Beetl is a powerful and high-performance template engine.

[0068] The converter is configured to perform data conversion using function calculation. Function calculation is an event-driven hosting computing service, which allows users to upload function code and run it in a highly reliable environment without the need to purchase and manage infrastructure such as servers. Function calculation can include function management and function invocation. Function management can be uploading or online generating a function, publishing the function to a container, and generating a publishing result. Function invocation can be obtaining a callback address from the publishing result and performing function calculation according to a configured function entry.

[0069] The logical processor is one of the application points of the embodiments of the present disclosure, and solves the second technical problem mentioned in the background. Different types of data format conversion between different systems need to be developed by the developer to write a large amount of code to implement the data format conversion, which increases the difficulty of data format conversion, and the efficiency of data format conversion is low. The reason why the difficulty of data format conversion is increased and the efficiency of data format conversion is low is often as follows: to complete different types of data format conversion between different systems, the developer needs to write a large amount of code to implement the data format conversion. If the above reasons are solved, the effect of reducing the difficulty of data format conversion and improving the efficiency of data format conversion can be achieved. In order to achieve this effect, the logical processor includes a plurality of components to implement different types of data format conversion. The logical processor includes an inspector, a filter, a splitter, a selector, a templater, and a converter. Each component can complete the data format conversion through a template language and a small amount of user-written language expressions. In addition, the user can combine any component in the logical processor and any component therebetween according to the demand to implement the data format conversion. Thus, when completing different types of data format conversion between different systems, the developer does not need to write a large amount of code to implement the data format conversion, and the developer can complete most of the data format conversion by using the template language and the language expression. Thus, the difficulty of data format conversion is reduced, and the efficiency of data format conversion is improved.

[0070] With Figure 2The low-code data format conversion system in the embodiment is different from the prior art in that the device in the embodiment further comprises a container 6, which is in communication connection with the converter. The container is configured to obtain function information and function call entry information. The function information is function information saved in a code repository or function information generated by a function generator. The function information saved in the code repository is function information defined in a preset software framework. The function information is published to obtain a publishing result. The publishing result includes publishing success and publishing failure. When the publishing result is publishing success, callback address information is generated. The function calculation is performed according to the function call entry information and the callback address information. The function call entry information can be function call website information. The callback address information can be authorized address information. The table structure design of the function calculation is as shown in Figure 9 .

[0071] In some embodiments, the container can execute the function call entry information, and then execute the user-defined function information, so as to realize the function calculation. For example, the user-defined function information can be to count order information, determine the order frequency and order probability of a user, and the like. The container is a smaller dimension relative to the server dimension. A plurality of containers can be arranged in a physical server. An application system can run in the container. That is, there can be a container in the server. There can be an application system in the container. The table structure design of the converter is as shown in Figure 10 .

[0072] With Figure 2 The low-code data format conversion system in the embodiment is different from the prior art in that the connector in the embodiment is further configured to obtain user configuration information. According to the user configuration information, the data source information is randomly sent to the checker, the filter, the splitter, the selector, the template, or the converter. The user configuration information can be user-configured data source information that needs to be converted by which components in the logic processor. The checker, the filter, the splitter, the selector, the template, and the converter in the logic processor can be simultaneously serially and concurrently run. The data processing flow of the logic processor is as shown in Figure 11 .

[0073] With Figure 2 The low-code data format conversion system in the embodiment is different from the prior art in that the system in the embodiment further comprises a log management module 7, wherein the log management module is in communication connection with the connector, the logic processor, and the pusher. The log management module is configured to record information generated when the data source information passes through the connector, the logic processor, and the pusher.

[0074] The above various embodiments of the present disclosure have the following beneficial effects: the above logical processor includes various components to implement different types of data format conversion. The above logical processor includes an inspector, a filter, a splitter, a selector, a templater, and a converter. Each component can complete data format conversion through a template language and a small amount of user-written language expressions. In addition, the user can combine any component in the above logical processor and between any components according to needs to implement data format conversion. Thus, when completing different types of data format conversion between different systems, the developer does not need to write a large amount of code to implement data format conversion, and the developer can complete most of the data format conversion by using the template language and the language expression. Thus, the difficulty of data format conversion is reduced, and the efficiency of data format conversion is improved.

[0075] With continued reference to Figure 12 , a flow 400 of some embodiments of a low-code data format conversion method of a low-code data format conversion system according to the present disclosure is shown. The low-code data format conversion method of the low-code data format conversion system includes the following steps:

[0076] At step 401, the connector acquires data source information of a first system and data format information of a second system in real time or at a timing.

[0077] In some embodiments, for data required within a system, the connector can acquire at a timing. For real-time data generated by a business system and required to be pushed to a user, the connector can acquire in real time. The data source information can be at least one record in a database relational table. The data source information can include basic information and business information. The basic information can be information related to personnel. The business information can be information related to business. The data format information can include data format conversion information and data transmission requirement information. The data format conversion information can be field requirement information of the record by the second system. The data transmission requirement information can be interface information of the second system receiving information.

[0078] As an example, the first system 1 and the second system 2 can be any subsystem involved in a low-code data format conversion system. The first system 1 and the second system 2 can include, but are not limited to, an order management system, a logistics management system, or a user information management system, and the like. A record in the relationship table can be: {number: 010, name: Zhang San, gender: male, order number: 5 times, purchase item category: home textiles, logistics status: normal}. The basic information can be number, name, gender, and the like. The business information can be order number, purchase item category, logistics status, and the like. The field requirement information in the record in the second system can be {number, name, logistics status}. The interface through which the second system receives information can be a hypertext transfer interface and a secure file transfer interface. Therefore, the first system can transmit information to the second system through any one of the hypertext transfer interface and the secure file transfer interface.

[0079] At step 402, the logic processor converts the data source information according to the data format information to obtain conversion data.

[0080] In some embodiments, the logic processor can compare the data format information with the data source information, extract the consistent information, and recombine to obtain the conversion data.

[0081] As an example, the data comparison can be a comparison of the fields (number, name, gender, order number, purchase item category, and logistics status). The consistent (number, name, and logistics status) can be extracted, and the specific information of each field can be combined. Thus, the data source information {number: 010, name: Zhang San, gender: male, order number: 5 times, purchase item category: home textiles, logistics status: normal} can be converted to {number: 010, name: Zhang San, logistics status: normal}.

[0082] At step 403, the pusher pushes the conversion data to the second system.

[0083] In some embodiments, the pusher can push the conversion data to the second system.

[0084] Optionally, the container obtains function information and function call entry information.

[0085] In some embodiments, the container can obtain function information and function call entry information. The function information can be function information saved in a code repository or function information generated by a function generator. The function information saved in the code repository can be function information defined in a preset software framework. The function call entry information can be function call website information.

[0086] Optionally, the container publishes the function information, and obtains a publishing result. The publishing result can include publishing success and publishing failure.

[0087] Optionally, when the publishing result is publishing success, the container generates callback address information. The callback address information can be authorized address information.

[0088] Optionally, the container executes function calculation according to the function call entry information and the callback address information.

[0089] In some embodiments, the container can execute the function call entry information, and then execute the user-defined function information, so as to implement function calculation. For example, the user-defined function information can be statistics on order information, determination of user order frequency, order probability, etc.

[0090] Optionally, the connector obtains user configuration information. The user configuration information can be configuration of the user on which components in the logical processor the data source information needs to pass through for data conversion.

[0091] Optionally, the connector sends the data source information to the inspector, the filter, the splitter, the selector, the templatizer or the converter according to the user configuration information.

[0092] In some embodiments, the inspector, the filter, the splitter, the selector, the templatizer and the converter in the logical processor can be run in series and in parallel at the same time. The user can configure the components according to actual needs.

[0093] Optionally, the log management module records information generated when the data source information passes through the connector, the logical processor and the pusher.

[0094] It can be understood that each step described in the method 400 corresponds to each step in the system described with reference to Figure 2 The operations, features and advantages described above for the system also apply to the method 400, and will not be repeated here.

[0095] The above description is only some of the preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the application involved in the embodiments of the present disclosure is not limited to the technical solutions formed by the specific combinations of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or equivalent features without departing from the above inventive concept. For example, the above features and technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) are replaced with each other to form a technical solution.

Claims

1. A low-code data format conversion system, comprising: The first system, the second system, the connector, the logic processor and the pusher, wherein: The connector is in communication connection with the first system and the second system, wherein the connector is configured to acquire the data source information of the first system and the data format information of the second system in real time or at a timing; The connector is in communication connection with the logic processor, wherein the connector is configured to send the data source information and the data format information to the logic processor; The logic processor is configured to perform data format conversion on the data source information according to the data format information to obtain converted data; The logic processor is in communication connection with the pusher, wherein the logic processor is configured to send the converted data to the pusher; The pusher is in communication connection with the second system, wherein the pusher is configured to push the converted data to the second system; The system further comprises a container, which is in communication connection with a converter included in the logic processor, and the converter is configured to perform data conversion by using function calculation, wherein the container is configured to: acquire function information and function call entry information, wherein the function information is function information saved in a code repository or function information generated by using a function generator, and the function information saved in the code repository is function information customized in a preset software framework; publish the function information to obtain a publishing result, wherein the publishing result includes publishing success and publishing failure; when the publishing result is publishing success, generate callback address information; perform function calculation according to the function call entry information and the callback address information.

2. The system of claim 1, wherein, The data source information includes at least one of the following: a hypertext data source, a file data source, a database, a web service data source and a message queue data source.

3. The system of claim 2, wherein, The connector performs parameter configuration in a visual manner, wherein the connector includes at least one of the following: a file connector, a hypertext connector and a message queue connector.

4. The system of claim 3, wherein, When the connector is a file connector, connection information is configured in a visual manner; when the connector is a hypertext connector, the hypertext connector calls an authentication center to acquire hypertext interface information for authentication to obtain an authentication result, and in response to determining that the authentication result satisfies a first preset condition, a template is used to acquire response parameters of the hypertext data source; when the connector is a message queue connector, to-be-acquired message queue information and topic information are configured in a visual manner.

5. The system of claim 4, wherein, The system further comprises a log management module, and the logic processor further comprises an inspector, a filter, a splitter, a selector and a templatizer, wherein the inspector is configured to check whether the data source information satisfies a second preset condition, the filter is configured to eliminate data source information that does not satisfy a third preset condition, the splitter is configured to split the data source information according to a fourth preset condition, the selector is configured to determine a flow direction of the data source information according to a fifth preset condition, and the templatizer is configured to perform data conversion by using a template.

6. The system of claim 5, wherein, The connector is further configured to: obtain configuration information of a user; send the data source information randomly to the inspector, the filter, the splitter, the selector, the templatizer, or the converter according to the configuration information of the user.

7. The system of claim 6, wherein: The log management module is respectively connected with the connector, the logic processor and the pusher, wherein the log management module is configured to record information generated when the data source information passes through the connector, the logic processor and the pusher.

8. A low-code data format conversion method for the low-code data format conversion system of claim 5, comprising: The connector obtains data source information of the first system and data format information of the second system in real time or at a timing, wherein the data source information includes at least one of the following: a hypertext data source, a file data source, a database, a web service data source, and a message queue data source, the connector is configured by a visual method, and the connector includes at least one of the following: a file connector, a hypertext connector, and a message queue connector; The logic processor converts the data source information into converted data according to the data format information; The pusher pushes the converted data to the second system.

9. The method of claim 8, wherein, The method further comprises: The container obtains function information and function call entry information, wherein the function information is function information saved in a code repository or function information generated by a function generator, and the function information saved in the code repository is function information customized in a preset software framework; The container publishes the function information to obtain a publishing result, wherein the publishing result includes publishing success and publishing failure; When the publishing result is publishing success, the container generates callback address information; The container performs function calculation according to the function call entry information and the callback address information; The connector obtains configuration information of a user; The connector sends the data source information randomly to the inspector, the filter, the splitter, the selector, the templatizer, or the converter according to the configuration information of the user; The log management module records information generated when the data source information passes through the connector, the logic processor and the pusher.

Images