A low-code developed application replication method and device, equipment and medium

Abstract

The embodiment of the specification discloses a low-code development application replication method and device, equipment and medium, comprising: constructing context information of specified application replication during low-code development; collecting metadata and configuration data in the specified application, and determining the original identifier of the metadata; replicating the metadata to obtain replicated metadata, and determining the new identifier of the replicated metadata; determining the mapping relationship between the original identifier and the new identifier, and recording the mapping relationship to the context information; replicating the configuration data according to the pre-set configuration node rule to obtain replicated configuration data; determining the transformation attribute between the configuration data and the replicated configuration data, and recording the transformation attribute to the context information; storing the replicated metadata to the database according to the mapping relationship in the context information, and storing the replicated configuration data to the database according to the transformation attribute in the context information.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a method, device, equipment, and medium for copying applications developed with low code. Background Art

[0002] When developing with zero or low code, you need to create an application. An application is the smallest unit that can be deployed and run independently. Applications contain metadata (metamodels), configuration data, and other content. There are over 20 types of metadata and over ten types of configuration data, and different teams are responsible for their development.

[0003] In actual development, you often need to copy an application within the same application or between different applications. Due to the large variety of metadata and configuration data, simply copying may cause the copied application to not function properly. Summary of the Invention

[0004] One or more embodiments of this specification provide an application replication method, apparatus, device, and medium to solve the technical problems raised in the background art.

[0005] One or more embodiments of this specification adopt the following technical solutions:

[0006] One or more embodiments of this specification provide a method for replicating an application developed with low code, including:

[0007] During low-code development, construct contextual information for specific application replication;

[0008] Collecting metadata and configuration data within the specified application and determining the original identifier of the metadata;

[0009] Copying the metadata to obtain copied metadata, and determining a new identifier of the copied metadata;

[0010] Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information;

[0011] The configuration data is copied according to a preset configuration node rule to obtain copied configuration data;

[0012] determining a transformation attribute between the configuration data and the copied configuration data, and recording the transformation attribute in the context information;

[0013] The replication metadata is stored in a database according to the mapping relationship in the context information, and the replication configuration data is stored in a database according to the transformation attribute in the context information.

[0014] One or more embodiments of this specification provide a low-code development application replication device, the device comprising:

[0015] Construction unit, during low-code development, constructs the context information copied by the specified application;

[0016] a collecting unit, which collects metadata and configuration data within the specified application and determines an original identifier of the metadata;

[0017] a metadata copying unit, which copies the metadata to obtain copied metadata and determines a new identifier of the copied metadata;

[0018] a mapping relationship determining unit, which determines a mapping relationship between the original identifier and the new identifier, and records the mapping relationship in the context information;

[0019] A configuration data replication unit, which replicates the configuration data according to a preset configuration node rule to obtain replicated configuration data;

[0020] a transformation attribute determining unit, configured to determine a transformation attribute between the configuration data and the copied configuration data, and record the transformation attribute in the context information;

[0021] A storage unit stores the replication metadata in a database according to the mapping relationship in the context information, and stores the replication configuration data in a database according to the transformation attribute in the context information.

[0022] One or more embodiments of this specification provide a low-code application replication device, including:

[0023] at least one processor; and,

[0024] a memory communicatively connected to the at least one processor; wherein,

[0025] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0026] During low-code development, construct contextual information for specific application replication;

[0027] Collecting metadata and configuration data within the specified application and determining the original identifier of the metadata;

[0028] Copying the metadata to obtain copied metadata, and determining a new identifier of the copied metadata;

[0029] Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information;

[0030] The configuration data is copied according to a preset configuration node rule to obtain copied configuration data;

[0031] determining a transformation attribute between the configuration data and the copied configuration data, and recording the transformation attribute in the context information;

[0032] The replication metadata is stored in a database according to the mapping relationship in the context information, and the replication configuration data is stored in a database according to the transformation attribute in the context information.

[0033] One or more embodiments of this specification provide a non-volatile computer storage medium storing computer-executable instructions. When executed by a computer, the computer-executable instructions can achieve:

[0034] During low-code development, construct contextual information for specific application replication;

[0035] Collecting metadata and configuration data within the specified application and determining the original identifier of the metadata;

[0036] Copying the metadata to obtain copied metadata, and determining a new identifier of the copied metadata;

[0037] Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information;

[0038] The configuration data is copied according to a preset configuration node rule to obtain copied configuration data;

[0039] determining a transformation attribute between the configuration data and the copied configuration data, and recording the transformation attribute in the context information;

[0040] The replication metadata is stored in a database according to the mapping relationship in the context information, and the replication configuration data is stored in a database according to the transformation attribute in the context information.

[0041] At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:

[0042] The embodiments of this specification achieve automatic application replication by constructing context information, collecting metadata and configuration data, replicating the metadata and configuration data, and saving the metadata and configuration data. This significantly improves development efficiency and reduces development errors. During the replication process, the dependencies between the metadata and configuration data are processed to ensure that the dependencies of the replicated application are intact, avoiding the dependency corruption issues that may occur with simple replication. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are only some of the embodiments described in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0044] Figure 1 A flowchart of a low-code development application replication method provided in one or more embodiments of this specification;

[0045] Figure 2 A flowchart of a method for metadata model replication provided in one or more embodiments of this specification;

[0046] Figure 3 A schematic diagram of the structure of an application replication device developed with low code provided in one or more embodiments of this specification;

[0047] Figure 4 A structural diagram of a low-code developed application replication device provided for one or more embodiments of this specification. DETAILED DESCRIPTION

[0048] The embodiments of this specification provide a method, apparatus, device, and medium for replicating applications developed with low code.

[0049] Zero-code / low-code development platforms have been widely used in recent years. They can simplify the development process, improve development efficiency, reduce development difficulty, and even enable non-programmers to develop programs. However, zero-code / low-code development platforms also have some problems, one of which is to achieve application replication and automatically handle complex dependencies between data and configurations.

[0050] In traditional development models, developers often need to manually manage dependencies between data and configurations, which not only consumes a lot of time and effort but is also prone to errors. This is especially true when copying models or applications, as manual handling is nearly impossible due to the large number of elements that need to be copied and the complex dependencies.

[0051] Therefore, automatically handling the dependencies between data and configuration when copying models or applications has become an important issue that zero / low-code development platforms need to solve.

[0052] To help those skilled in the art better understand the technical solutions in this specification, the following will provide a clear and complete description of the technical solutions in the embodiments of this specification, in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative work should fall within the scope of protection of this specification.

[0053] Figure 1 This is a flowchart of a low-code application replication method provided in one or more embodiments of this specification. This process can be executed by a low-code application replication system. Certain input parameters or intermediate results in the process can be manually adjusted to help improve accuracy.

[0054] The method steps of the embodiment of this specification are as follows:

[0055] S102, during low-code development, construct context information for specifying application replication.

[0056] In the embodiments of this specification, in low-code development, constructing context information for replicating a specific application may refer to creating a specific environment that contains all relevant information about the application, such as the data model, user interface, business logic, etc. This environment can be replicated to another location, allowing the same application to run in a different environment. Specifically, constructing context information for replicating a specific application may be accomplished through the following steps.

[0057] It should be noted that, by constructing contextual information for specifying application replication, the embodiments of this specification can rapidly replicate and deploy applications in different environments, improving development efficiency and project delivery. Furthermore, these replicated environments can be used to test, develop, and deploy multiple versions of applications, enabling more flexible application management and maintenance.

[0058] S104: Collect metadata and configuration data within the specified application, and determine the original identifier of the metadata.

[0059] In the embodiments of this specification, when collecting metadata and configuration data within a specified application, it is first necessary to identify and determine the required metadata and configuration information. Metadata can include database fields, data models, tables, columns, relationships, indexes, views, etc. used by the application. Configuration data includes application settings, parameters, options, etc. The specific steps can be as follows:

[0060] Determine the scope of metadata and configuration data: Clarify the scope of metadata and configuration data that need to be collected, which can be determined based on the functions and requirements of the application.

[0061] Traverse the application's source code and configuration files: Check the application's source code and configuration files one by one to find the parts related to metadata and configuration data. This may involve looking at database scripts, ORM mapping files, configuration files (such as XML, JSON, etc.), comments, etc.

[0062] Extract metadata and configuration data: Extract the required metadata and configuration data from the source code and configuration files. This can be achieved by parsing the source code and configuration files, or using specific tools and techniques to assist in the extraction.

[0063] Identify metadata's origin: When metadata is collected, a unique origin is assigned to each piece of metadata. This helps with subsequent metadata processing and management, such as ensuring data consistency when copying or migrating applications.

[0064] By collecting metadata and configuration data within a specific application and determining the metadata's original identifier, we can better understand the application's structure and configuration, providing foundational information for subsequent development, testing, and deployment. This can reduce errors and conflicts and improve understanding and management of applications.

[0065] S106: Duplicate the metadata to obtain duplicate metadata, and determine a new identifier for the duplicate metadata.

[0066] In the embodiment of this specification, when copying metadata, a copy of the original metadata can be obtained first, and a new identifier can be assigned to the copy to uniquely identify the copied metadata in the system. The specific steps can be as follows:

[0067] Copy the original metadata: For each piece of original metadata, create a corresponding copy and copy the definition or configuration information of the original metadata to the copy. This can be achieved programmatically or using a specific tool.

[0068] Assign a new identifier: Assign a new identifier to each copied metadata to ensure that the copied metadata is uniquely identified in the system. This new identifier can be an automatically generated unique identifier or an identifier generated according to certain rules.

[0069] Update relationships: If there are relationships between the replicated metadata, these relationships need to be updated to ensure they are consistent with the replicated metadata. This may involve updating foreign key relationships, reference relationships, etc.

[0070] By replicating metadata and assigning a new identity to the replicated metadata, you can create a copy that is similar but independent of the original metadata. This allows for development, testing, demonstrations, and other operations without affecting the original system, and allows you to independently manage and maintain the replicated metadata as needed.

[0071] In the embodiment of this specification, when the metadata is copied to obtain the copied metadata, the dependency relationship between the metadata can be determined; based on the dependency relationship, the metadata is copied to obtain the copied metadata.

[0072] It should be noted that, after determining the dependencies between metadata, the embodiments of this specification can replicate the metadata based on these dependencies, thereby obtaining replicated metadata. This ensures that the integrity and consistency of the dependencies can be maintained during the replication process. The specific steps can be as follows:

[0073] Analyze the dependencies between metadata: Carefully analyze the dependencies between each metadata, which can include association relationships, reference relationships, dependency relationships, etc. This can be determined by reviewing metadata definitions, configuration files, database scripts, etc.

[0074] Determine replication order: Determine the replication order based on the dependencies between metadata. Ensure that before replicating a metadata item, the metadata it depends on has been replicated and is available. This can be done by building a dependency graph to help determine the replication order.

[0075] Replicate metadata: Replicate metadata one by one in the specified replication order. This may involve replicating definitions of database tables, views, stored procedures, or metadata configuration information in configuration files.

[0076] Track and update dependencies: During the replication process, metadata dependencies are updated promptly. For example, references and foreign key relationships in the replication metadata are updated to maintain dependency consistency.

[0077] By identifying dependencies between metadata and replicating based on these dependencies, the integrity and consistency of the dependencies between replicated metadata can be guaranteed. This helps to correctly use and manage these metadata in the replicated environment and ensures that the system works properly after replication.

[0078] Furthermore, in the embodiment of this specification, when copying the metadata according to the dependency relationship, the lowest leaf node that has no other metadata dependencies can be determined according to the dependency relationship; starting from the lowest leaf node, each metadata is copied to the target location according to the dependency relationship to obtain copied metadata.

[0079] The embodiments of this specification can analyze the dependencies between metadata. This includes checking the association relationships, reference relationships, dependencies, etc. between metadata, and then determining the lowest-level leaf nodes. The lowest-level leaf nodes are leaf nodes that have no other metadata dependencies. These leaf nodes have no other metadata dependencies, so they can be copied first. Starting from the determined lowest-level leaf nodes, the metadata is copied step by step according to the dependencies. This means that metadata that depends on other metadata will be copied after the metadata it depends on. Then, based on the determined dependencies, each metadata is copied to the target location in sequence. This may involve copying definitions such as database tables, views, stored procedures, or copying metadata configuration information in configuration files.

[0080] It should be noted that this approach maintains the integrity of dependencies, ensuring that when metadata is copied, the metadata it depends on already exists. This prevents missing or incorrect dependencies from occurring during the copy process, ensuring the correctness and consistency of the copied metadata.

[0081] In an embodiment of the present specification, before copying the metadata, a pre-copy event may be triggered, the pre-copy event being used to perform pre-processing operations, and obtaining and processing information related to the metadata before copying through a metadata listener; after obtaining the copied metadata, a post-copy event may be triggered, the post-copy event being used to perform post-processing operations, and obtaining and processing information related to the copied metadata after copying through the metadata listener; by triggering the pre-copy event and the post-copy event, monitoring of the metadata and the copied metadata is achieved.

[0082] It should be noted that the pre-copy event in the embodiments of this specification can be an event triggered before metadata is copied. This event can be used to perform pre-processing operations. Pre-processing operations may include verifying metadata integrity to ensure that all required fields and information are present; checking dependencies between metadata to ensure that dependent metadata is ready; and backing up the original data to facilitate rollback or recovery during the copy process.

[0083] It should be noted that the post-replication event in the embodiments of this specification can be an event triggered after metadata is replicated. This event can be used to perform post-processing operations. Post-processing operations can include updating relevant indexes to ensure the accuracy and performance of the replicated metadata during query and retrieval; notifying other systems or modules to synchronize data to maintain data consistency; and triggering other business logic, such as generating reports and triggering workflows.

[0084] By triggering pre-replication and post-replication events and obtaining and processing related information through metadata listeners, metadata and replication metadata can be monitored. This monitoring mechanism can be used to perform additional logic and actions, such as logging, triggering other events, and updating other systems. This provides the ability to extend and customize the metadata replication process to meet specific needs and business processes.

[0085] In the embodiment of the present specification, the consistency between the replication metadata and the metadata can be verified by triggering the pre-replication event and the post-replication event.

[0086] It should be noted that before data replication, the system triggers a pre-replication event to perform some preparatory work, such as backing up the original data and recording metadata information. The pre-replication event ensures that the original data is protected during the replication process so that it can be verified after replication.

[0087] After data replication is complete, the system triggers a post-replication event, which verifies the consistency of the replicated metadata with the original data. By comparing the replicated metadata with the original data, the system can determine the accuracy and completeness of the data replication.

[0088] By triggering pre-replication events and post-replication events and verifying the consistency of the replication metadata with the original data, it can be ensured that no data loss, data corruption or other errors occur during the data replication process, thereby ensuring data reliability and consistency.

[0089] S108: Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information.

[0090] In some cases, in the embodiments of this specification, it is necessary to change the identification of data or objects. This may occur in scenarios such as data migration, system upgrades, or data consolidation. When changing identification, it is necessary to ensure that the mapping relationship between the original identification and the new identification can be recorded and tracked.

[0091] To achieve this goal, we first need to determine the mapping between the original and new identities. This can be accomplished using specific algorithms or rules to ensure accurate, one-to-one mappings. These mappings are then recorded in context information. Context information refers to data structures or objects used to store and communicate relevant information during data processing. By recording these mappings in context information, they can be easily retrieved and used in subsequent operations.

[0092] The benefit of recording mappings in context information is that it facilitates identity conversion and association operations. When a new identity is needed, it can be converted to the corresponding original identity by looking up the mapping in the context information. Similarly, when the original identity needs to be used, it can also be converted to the corresponding new identity using the mapping in the context information.

[0093] By determining the mapping relationship and recording it in the context information, changes in identification can be effectively managed and tracked, improving the accuracy and reliability of data processing.

[0094] S110 , copying the configuration data according to a preset configuration node rule to obtain copied configuration data.

[0095] In the embodiment of this specification, the replication order of the configuration data may be determined according to the configuration node rule; and then the configuration data may be replicated according to the replication order to obtain the replicated configuration data.

[0096] It should be noted that the configuration node rules in the embodiments of this specification may define the processing strategy of configuration data according to certain preset rules, such as which configuration data is pre-processed, which is post-processed, the processing order of the configuration data, the priority, etc. The configuration rule engine reads the configuration node rules and performs corresponding processing according to the rules.

[0097] It should be noted that the configuration node rules in the embodiments of this specification can be pre-set rules that define configuration data processing strategies. These rules can specify how different configuration data are processed, including pre-processing and post-processing, as well as the order and priority of configuration data processing. To process according to the configuration node rules, the configuration rule engine reads and parses the configuration node rules. Based on the rule definitions, the configuration rule engine determines the order in which the configuration data is replicated.

[0098] Based on the replication order you've determined, the configuration rules engine replicates the configuration data in the specified order. This means that configuration data that undergoes pre-processing will be replicated first, followed by configuration data that undergoes post-processing. By replicating according to the rules, you can ensure that the processing order and priority of configuration data are maintained.

[0099] Finally, by executing the copy operation, the copied configuration data is obtained. The copied configuration data is the result of copying in the order and manner defined by the configuration node rules.

[0100] By configuring node rules and configuring the rule engine, you can achieve flexible management and customized processing of configuration data. This ensures that configuration data is replicated according to preset rules and meets specific processing requirements.

[0101] S112: Determine a transformation attribute between the configuration data and the replicated configuration data, and record the transformation attribute in the context information.

[0102] In the embodiments of this specification, configuration data usually needs to undergo some transformation or conversion operations when being copied or processed to meet specific needs or requirements. These transformation attributes include but are not limited to data format conversion, data field mapping, data content filtering or modification, etc.

[0103] Determining the transformation attributes between the configuration data and the replicated configuration data ensures that the replicated configuration data meets specific processing requirements or constraints. By determining the transformation attributes, the configuration data can be flexibly transformed during the replication process to meet the needs of the target system or environment.

[0104] The benefit of recording these transformation attributes in context information is that it facilitates tracking and management of data transformations. Context information is a data structure or object that stores and transmits related information. By recording transformation attributes in context information, these transformation attributes can be easily found and used in subsequent operations.

[0105] Recording transformation attributes in context information helps facilitate understanding the transformation history and related attributes of data when subsequent processing or management of replication configuration data is required. This improves the traceability and maintainability of data transformations and ensures data accuracy and consistency.

[0106] By determining the transformation attributes and recording them in the context information, the transformation process of the configuration data can be effectively managed and tracked to meet the processing requirements and constraints of the copied data.

[0107] S114 , storing the replication metadata in a database according to the mapping relationship in the context information, and storing the replication configuration data in a database according to the transformation attribute in the context information.

[0108] In the embodiments of this specification, after performing a data copy operation, the copied metadata can be stored in a database based on the mapping relationship recorded in the context information. The mapping relationship records the correspondence between the original identifier and the new identifier. By searching the mapping relationship, the copied metadata can be associated with the corresponding original data and stored in the database.

[0109] Furthermore, based on the transformation attributes recorded in the context information, the copied configuration data can be transformed accordingly and stored in the database. Transformation attributes record the processing rules for the configuration data, which may include data format conversion, field mapping, content filtering, etc. The copied configuration data is processed according to these rules before being stored in the database.

[0110] By storing the replicated metadata and configuration data in a database, data persistence and further management can be achieved. This facilitates subsequent query, analysis, and use while also ensuring data security and reliability.

[0111] Storing metadata and configuration data based on mapping relationships within contextual information, and transforming attributes, can improve the accuracy and consistency of data storage. Furthermore, combined with database functionality, replicated data can be better managed and utilized to meet specific business needs.

[0112] It should be noted that Figure 2 The following is a flowchart of a method for replicating metadata models provided in an embodiment of this specification. The detailed description of each step is as follows:

[0113] 1. Context initialization process.

[0114] Construct the application replication context information as the thread-level shared area for the entire replication process. This step provides the replication process with context information that is shared and used during the replication process.

[0115] 2. Collection process.

[0116] Collect metadata and configuration data within the application, and provide extension points for metadata and configuration data collection, allowing for the expansion and implementation of various metadata and configuration data. This step provides replication resource information for the replication process.

[0117] 3. Copy the process.

[0118] The replication process includes metadata replication and configuration data replication.

[0119] To handle the complex dependencies between metadata and configuration data, the replication process is divided into the configuration data pre-replication process, the metadata replication process, and the configuration data post-replication process.

[0120] Among them, the dependence of configuration data on metadata is mainly dependence on metadata ID.

[0121] (1) First, the mapping relationship between the original ID of all metadata and the copied new ID is recorded in the context.

[0122] (2) Then, according to the configuration node rules, the pre-configuration data and post-configuration data are copied, and configuration data copy extension points are provided for various configuration data extension implementations. Before and after the copy, the attributes that need to be changed will be recorded in the context for use when other data is copied.

[0123] (3) Metadata replication involves constructing a metadata interdependence graph, replicating metadata starting from the lowest leaf node in the dependency order, and providing metadata replication extension points for various metadata extension implementations. Metadata pre-replication and post-replication events are used by various metadata monitoring methods.

[0124] 4. Save the process.

[0125] Save metadata and configuration data. Based on context information, persist metadata and configuration data to a database or file. Metadata pre-save and post-save events are used by various metadata listeners.

[0126] The embodiments of this specification implement automatic application replication through the four steps described above, resolving the complex dependencies between data and configuration in zero-code / low-code development, significantly improving development efficiency and reducing development errors. Furthermore, the pre- and post-replication event monitoring and replication extension points provided by this invention enhance the versatility and adaptability of the method, allowing for the expansion and implementation of various metadata and configuration data based on individual needs.

[0127] In general, the embodiments of this specification provide a method based on metadata model replication, which is simple to operate, highly efficient, and reliable, and is suitable for application replication in zero / low-code development platforms.

[0128] Table 1 shows the interface design, listing the interface definitions such as key extension points and events in the overall process.

[0129]

[0130]

[0131] Table 1 Interface design

[0132] It should be noted that the embodiments of this specification relate to the field of zero-code / low-code development technology, and more specifically, to a method based on metadata model replication. This method is primarily applied to zero-code / low-code development platforms, which adopt the design concepts of domain-driven design (DDD) and model-driven architecture (MDA), propose a unified business modeling language (UBML) for specific domains, and have built-in visual development modeling tools for more than 40 development models.

[0133] The embodiments of this specification propose a method based on metadata model replication, which can automatically handle the dependency between metadata and configuration data, and can replicate the entire application to achieve rapid development of replicas of the same type.

[0134] The greatest advantage of the embodiments of this specification is that, by constructing a replication context, collecting metadata and configuration data, replicating metadata and configuration data, and saving metadata and configuration data, automatic replication of applications is achieved, which greatly improves development efficiency and reduces development errors.

[0135] Especially during the copying process, the embodiments of this specification process the dependency relationship between metadata and configuration data in detail, which can ensure the complete dependency relationship of the copied model or application and avoid the dependency destruction problem caused by simple copying.

[0136] In addition, the embodiments of this specification also provide pre-copy and post-copy event monitoring of metadata and configuration data, as well as replication extension points, so that various metadata and configuration data can be expanded and implemented according to their own needs, enhancing the versatility and adaptability of the method.

[0137] Figure 3 A structural diagram of a low-code developed application replication device provided for one or more embodiments of this specification, wherein the device includes: a construction unit 302, a collection unit 304, a metadata replication unit 306, a mapping relationship determination unit 308, a configuration data replication unit 310, a transformation attribute determination unit 312 and a storage unit 314.

[0138] A construction unit 302 constructs context information for specifying application replication during low-code development;

[0139] The collecting unit 304 collects metadata and configuration data within the specified application and determines the original identifier of the metadata;

[0140] The metadata copying unit 306 copies the metadata to obtain copied metadata and determines a new identifier of the copied metadata;

[0141] A mapping relationship determining unit 308 determines a mapping relationship between the original identifier and the new identifier, and records the mapping relationship in the context information;

[0142] The configuration data replication unit 310 replicates the configuration data according to a preset configuration node rule to obtain replicated configuration data;

[0143] a transformation attribute determining unit 312, which determines a transformation attribute between the configuration data and the replicated configuration data, and records the transformation attribute in the context information;

[0144] The storage unit 314 stores the replication metadata in a database according to the mapping relationship in the context information, and stores the replication configuration data in a database according to the transformation attribute in the context information.

[0145] Figure 4 A schematic diagram of a low-code application replication device provided for one or more embodiments of this specification includes:

[0146] at least one processor and a bus; and,

[0147] a memory communicatively connected to the at least one processor; wherein,

[0148] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0149] During low-code development, construct contextual information for specific application replication;

[0150] Collecting metadata and configuration data within the specified application and determining the original identifier of the metadata;

[0151] Copying the metadata to obtain copied metadata, and determining a new identifier of the copied metadata;

[0152] Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information;

[0153] The configuration data is copied according to a preset configuration node rule to obtain copied configuration data;

[0154] determining a transformation attribute between the configuration data and the copied configuration data, and recording the transformation attribute in the context information;

[0155] The replication metadata is stored in a database according to the mapping relationship in the context information, and the replication configuration data is stored in a database according to the transformation attribute in the context information.

[0156] One or more embodiments of this specification provide a non-volatile computer storage medium storing computer-executable instructions. When executed by a computer, the computer-executable instructions can achieve:

[0157] During low-code development, construct contextual information for specific application replication;

[0158] Collecting metadata and configuration data within the specified application and determining the original identifier of the metadata;

[0159] Copying the metadata to obtain copied metadata, and determining a new identifier of the copied metadata;

[0160] Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information;

[0161] The configuration data is copied according to a preset configuration node rule to obtain copied configuration data;

[0162] determining a transformation attribute between the configuration data and the copied configuration data, and recording the transformation attribute in the context information;

[0163] The replication metadata is stored in a database according to the mapping relationship in the context information, and the replication configuration data is stored in a database according to the transformation attribute in the context information.

[0164] The various embodiments in this specification are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the device, apparatus, and non-volatile computer storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simplified. For relevant details, refer to the descriptions of the method embodiments.

[0165] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0166] The foregoing description is merely one or more embodiments of this specification and is not intended to limit this specification. It will be apparent to those skilled in the art that various modifications and variations may be made to one or more embodiments of this specification. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of one or more embodiments of this specification are intended to be within the scope of the claims of this specification.

Claims

1. A low-code application replication method, characterized in that: The method comprises: During low-code development, construct contextual information for specific application replication; Collecting metadata and configuration data within the specified application and determining the original identifier of the metadata; Copying the metadata to obtain copied metadata, and determining a new identifier of the copied metadata; Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information; The configuration data is copied according to a preset configuration node rule to obtain copied configuration data; determining a transformation attribute between the configuration data and the copied configuration data, and recording the transformation attribute in the context information; Storing the replication metadata in a database according to the mapping relationship in the context information, and storing the replication configuration data in a database according to the transformation attribute in the context information; The step of copying the metadata to obtain the copied metadata includes: Determining dependencies between the metadata; The metadata is copied according to the dependency relationship to obtain copied metadata.

2. The method according to claim 1, characterized in that The copying of the metadata according to the dependency relationship includes: Based on the dependency relationship, determine the lowest leaf node that has no other metadata dependencies; Starting from the bottom-level leaf node, each metadata is copied to a target location according to the dependency relationship to obtain copied metadata.

3. The method according to claim 1, characterized in that Before copying the metadata, the method further includes: Triggering a pre-copy event, the pre-copy event is used to perform a pre-processing operation, and obtain and process the metadata-related information through the metadata listener before copying; After obtaining the replication metadata, the method further includes: Triggering a post-copy event, wherein the post-copy event is used to perform a post-processing operation, and obtain and process information related to the copy metadata after copying through the metadata listener; The monitoring of the metadata and the replicated metadata is achieved by triggering the pre-replication event and the post-replication event.

4. The method according to claim 3, characterized in that The pre-processing operations include: verifying the integrity of metadata, checking dependencies, and backing up original data; the post-processing operations include: updating related indexes, notifying other systems or modules to synchronize data, and triggering other business logic.

5. The method according to claim 3, characterized in that The triggering of the pre-copy event and the post-copy event to monitor the metadata and the copy metadata includes: The consistency between the replication metadata and the metadata is verified by triggering the pre-replication event and the post-replication event.

6. The method according to claim 1, characterized in that The configuration data is copied according to a preset configuration node rule to obtain copied configuration data, including: Determining a replication order of the configuration data according to the configuration node rule; The configuration data is copied according to the copy order to obtain the copied configuration data.

7. A low-code developed application replication device, characterized in that: The device comprises: The construction unit constructs the context information copied by the specified application during low-code development; a collecting unit, which collects metadata and configuration data within the specified application and determines an original identifier of the metadata; a metadata copying unit, which copies the metadata to obtain copied metadata and determines a new identifier of the copied metadata; a mapping relationship determining unit, which determines a mapping relationship between the original identifier and the new identifier, and records the mapping relationship in the context information; A configuration data replication unit, which replicates the configuration data according to a preset configuration node rule to obtain replicated configuration data; a transformation attribute determining unit, configured to determine a transformation attribute between the configuration data and the replicated configuration data, and record the transformation attribute in the context information; a storage unit, configured to store the replication metadata in a database according to the mapping relationship in the context information, and to store the replication configuration data in a database according to the transformation attribute in the context information; The step of copying the metadata to obtain the copied metadata includes: Determining dependencies between the metadata; The metadata is copied according to the dependency relationship to obtain copied metadata.

8. A low-code developed application replication device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: During low-code development, construct contextual information for specific application replication; Collecting metadata and configuration data within the specified application and determining the original identifier of the metadata; Copying the metadata to obtain copied metadata, and determining a new identifier of the copied metadata; Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information; The configuration data is copied according to a preset configuration node rule to obtain copied configuration data; determining a transformation attribute between the configuration data and the copied configuration data, and recording the transformation attribute in the context information; Storing the replication metadata in a database according to the mapping relationship in the context information, and storing the replication configuration data in a database according to the transformation attribute in the context information; The step of copying the metadata to obtain the copied metadata includes: Determining dependencies between the metadata; The metadata is copied according to the dependency relationship to obtain copied metadata.

9. A non-volatile computer storage medium, characterized in that The computer-executable instructions are stored, and when the computer-executable instructions are executed by a computer, they can achieve: During low-code development, construct contextual information for specific application replication; Collecting metadata and configuration data within the specified application and determining the original identifier of the metadata; Copying the metadata to obtain copied metadata, and determining a new identifier of the copied metadata; Determine a mapping relationship between the original identifier and the new identifier, and record the mapping relationship in the context information; The configuration data is copied according to a preset configuration node rule to obtain copied configuration data; determining a transformation attribute between the configuration data and the copied configuration data, and recording the transformation attribute in the context information; Storing the replication metadata in a database according to the mapping relationship in the context information, and storing the replication configuration data in a database according to the transformation attribute in the context information; The step of copying the metadata to obtain the copied metadata includes: Determining dependencies between the metadata; The metadata is copied according to the dependency relationship to obtain copied metadata.

Images