Service orchestration method and device for low-code platform, equipment and storage medium
By decomposing the target business into multiple fine-grained service nodes on a low-code platform and defining and optimizing their service information, the shortcomings of service orchestration in the existing technology are solved, and efficient and flexible service orchestration and development efficiency are achieved.
Patent Information
- Application Number
- CN202510128933.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-05
- Publication Date
- 2025-05-27
AI Technical Summary
The existing low-code platforms have problems such as insufficient fine-grained service decomposition, insufficient service information definition, insufficient configuration flexibility, and difficulty in data flow and execution tracking in terms of service orchestration.
By decomposing the target business into multiple fine-grained service nodes according to the business scenario, each service node defines its service information, and optimizes the service information based on the business scenario and service type to generate configuration information, so that it can be published and seamlessly connected, realizing data flow and execution tracking.
It realizes efficient, comprehensive and flexible service orchestration of low-code platforms, reduces manual coding workload, improves development efficiency, and adapts to the needs of different business scenarios.
Smart Images

Figure CN120045222A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of software development, and particularly to a service orchestration method, apparatus, device, and storage medium for a low-code platform. Background Art
[0002] With the acceleration of enterprise digital transformation, more and more enterprises hope to improve business efficiency and competitiveness through customized applications. Traditional software development methods usually require a large amount of coding work, a long development cycle, and high costs, making it difficult to quickly respond to market changes and business requirements. Therefore, as an emerging development model, the low-code platform has received extensive attention. The low-code platform enables developers to quickly create and deploy application programs through a visual interface and pre-built components, greatly improving development efficiency.
[0003] In existing low-code platforms, service orchestration is a core function that allows users to combine different services and functional modules to achieve complex business logics and application integrations. However, the current service orchestration methods mainly have the following deficiencies:
[0004] 1. Lack of fine-grained service decomposition: Usually unable to effectively decompose the target business into multiple fine-grained service nodes, resulting in complex business logics being difficult to clearly express;
[0005] 2. Insufficient service information definition: For each service node, there is a lack of a comprehensive service information definition mechanism, and the functions and service types of each service node cannot be accurately described.
[0006] 3. Lack of configuration flexibility: When configuring service nodes, it often relies on fixed templates or processes and is difficult to be flexibly configured according to specific business requirements.
[0007] 4. Difficulty in data flow and execution tracking: When dealing with multi-step business processes, it is difficult to effectively collect and transfer the execution data of each service node, resulting in difficulties in subsequent analysis and optimization. Summary of the Invention
[0008] In view of this, the present invention provides a service orchestration method, apparatus, device, and storage medium for a low-code platform to achieve efficient, comprehensive, and flexible service orchestration on the low-code platform.
[0009] In a first aspect, the present invention provides a service orchestration method for a low-code platform, and the method includes:
[0010] Based on the business scenario of the target business, decompose the target business into multiple service nodes, and any service node provides a service of the target business;
[0011] For each service node, define the service information of each service node, where the service information is used to indicate the service execution process of the service node;
[0012] Based on the business scenario of the target business and the service type to which each service node belongs, optimize the service information of each service node to obtain the configuration information of each service node, and set the service node with the configuration completed to the publishable state;
[0013] Configure the first service node for the target user, and collect the execution data of the target user during the process of the target user executing the first service node;
[0014] Transfer the execution data of the first service node to the next service node, and repeat the process of configuring the service node for the target user and collecting the execution data of the target user during the process of the target user executing the service node until all service nodes of the target business are completed.
[0015] The service orchestration method of the low-code platform provided by the embodiments of the present invention divides the complex target business into multiple independent service nodes according to the business scenario. Each node completes a specific service task. Define the service information for each service node to ensure that it provides corresponding services for the target user. Based on the business scenario and service type, improve the service information of each service node, and set the optimized service node to the publishable state so that it can be called and executed. Configure the first service node for the target user, collect the execution data of the target user, and transfer the execution data to the next service node and repeat the configuration and collection process until all service nodes are completed, ensuring seamless connection between each service node to form a complete business process. Implement service orchestration through the low-code platform, reduce the workload of manual coding, improve the development efficiency, and adapt to the needs of different business scenarios, with high flexibility. Through detailed definition, optimized configuration, and data transfer, ensure the stable operation of each service node, and achieve efficient, comprehensive, and flexible service orchestration.
[0016] In an alternative embodiment, for each service node, defining the service information of each service node includes:
[0017] Use a recommendation algorithm to determine whether the service node has a service reuse node;
[0018] When the service node has a service reuse node, reuse the service information of the service reuse node as the service information of the service node; or,
[0019] When the service node does not have a service reuse node, define the service information of the service node based on the business scenario of the target business.
[0020] The service orchestration method of the low-code platform provided by the embodiments of the present invention determines whether there is a service reuse node similar to the function of the service node through a recommendation algorithm. If there is a reusable service node, its service information is directly referenced without redefinition. If no suitable service reuse node is found, according to the current business requirements, the service information of the service node is defined from scratch to ensure that it meets specific business requirements. By judging whether existing service nodes can be reused, the workload of repeated definition is reduced, and the service orchestration efficiency is improved.
[0021] In an alternative embodiment, based on the business scenario of the target business and the service type to which each service node belongs, the service information of each service node is optimized to obtain the configuration information of each service node, including:
[0022] For any service node, when the service node has a service reuse node, based on the business scenario of the target business, the service information of the service reuse node is optimized as the configuration information of the service node;
[0023] When the service node does not have a service reuse node, based on the business scenario of the target business and the service type to which the service node belongs, a service model conversion tool is called to optimize the service information of the service node to obtain the configuration information.
[0024] The service orchestration method of the low-code platform provided by the embodiments of the present invention evaluates the role and requirements of each service node in the overall business process according to specific target business requirements, combines the service type to which the service node belongs and its defined service information, conducts comprehensive analysis, optimizes the service information of the reuse node, or uses a service model conversion tool to optimize the service information to generate the final configuration information, ensuring that each service node can operate efficiently and stably and be seamlessly integrated with the entire business process, improving the flexibility and comprehensiveness of service orchestration.
[0025] In an alternative embodiment, when the service node does not have a service reuse node, based on the business scenario of the target business and the service type to which each service node belongs, a service model conversion tool is called to optimize the service information of the service node to obtain the configuration information, including:
[0026] Based on the service type to which the service node belongs, determine the configuration fields and service execution methods in the service information;
[0027] Based on the business scenario of the target business and the preset configuration information corresponding to the service type, fill in the configuration fields;
[0028] Take the filled service information and service execution methods as the configuration information of the service node.
[0029] The service orchestration method of the low-code platform provided by the embodiments of the present invention determines which key configuration fields and service execution methods a service node should have according to the service type to which the service node belongs. Based on the target business requirements and the preset configuration information corresponding to the service type, these configuration fields are filled, and the filled configuration fields and service execution methods are integrated into complete configuration information, ensuring that the service node can operate according to the expected function and performance requirements, adapting to multiple business scenarios, and improving the flexibility and comprehensiveness of service orchestration.
[0030] In an alternative embodiment, the method further includes:
[0031] Optimizing the recommendation algorithm based on the correspondence between the target business and multiple service nodes and the configuration information of each service node.
[0032] The service orchestration method of the low-code platform provided by the embodiments of the present invention optimizes the recommendation algorithm based on the results obtained from the current service orchestration, which helps to improve the accuracy of subsequent judgments on the possibility of reuse.
[0033] In an alternative embodiment, the method further includes:
[0034] Encapsulating the execution data obtained by the target user for each service node.
[0035] The service orchestration method of the low-code platform provided by the embodiments of the present invention encapsulates the execution data of the target user, which helps to discover potential problems and improvement points in the service orchestration process based on the execution data, thereby continuously optimizing the service quality and user experience.
[0036] In a second aspect, the present invention provides a service orchestration device for a low-code platform, the device includes:
[0037] A decomposition module, configured to decompose the target business into multiple service nodes, and any service node provides a service for the target business;
[0038] A definition module, configured to define, for each service node, the service information of each service node, and the service information is used to indicate the service execution process of the service node;
[0039] A configuration module, configured to optimize the service information of the service node based on the target business, the service type to which each service node belongs, and the service information, obtain the configuration information of each service node, and set the configured service node to a publishable state;
[0040] An execution module, configured to configure the first service node for the target user and collect the execution data of the target user during the process of the target user executing the first service node;
[0041] An orchestration module is used to transfer the execution data of the first service node to the next service node, repeatedly configure service nodes for the target user, and collect the execution data of the target user during the process of the target user executing the service node until all service nodes of the target service are completed.
[0042] In a third aspect, the present invention provides a computer device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to perform the service orchestration method of the low-code platform according to the first aspect or any corresponding embodiment thereof.
[0043] In a fourth aspect, the present invention provides a computer-readable storage medium, on which computer instructions are stored. The computer instructions are used to cause a computer to perform the service orchestration method of the low-code platform according to the first aspect or any corresponding embodiment thereof.
[0044] In a fifth aspect, the present invention provides a computer program product, including computer instructions, which are used to cause a computer to perform the service orchestration method of the low-code platform according to the first aspect or any corresponding embodiment thereof. Description of the Drawings
[0045] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required for use in the description of the specific embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.
[0046] Figure 1 is a flowchart of the service orchestration method of the low-code platform according to an embodiment of the present invention;
[0047] Figure 2 is a flowchart of another service orchestration method of the low-code platform according to an embodiment of the present invention;
[0048] Figure 3 is a structural block diagram of the service orchestration device of the low-code platform according to an embodiment of the present invention;
[0049] Figure 4 is a schematic hardware structure diagram of the computer device according to an embodiment of the present invention. Detailed Embodiments
[0050] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.
[0051] In a low-code platform, service orchestration is a core function that allows users to combine different services and functional modules to achieve complex business logics and application integrations. The service orchestration method of the low-code platform provided by the embodiments of the present invention ensures the stable operation of each service node and realizes efficient, comprehensive, and flexible service orchestration by defining, optimizing the configuration, and data flow of the service orchestration process in detail.
[0052] According to the embodiments of the present invention, an embodiment of a service orchestration method for a low-code platform is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.
[0053] In this embodiment, a service orchestration method for a low-code platform is provided, which can be used in terminals such as computers. Figure 1 It is a flowchart of the service orchestration method for the low-code platform according to the embodiments of the present invention. As Figure 1 shown, the process includes the following steps:
[0054] Step S101, based on the business scenario of the target business, decompose the target business into multiple service nodes, and any service node provides one service of the target business.
[0055] Specifically, according to the actual business scenario corresponding to the target business, decompose it into multiple service nodes. For example, if the target business is the meeting notification function of an OA (Office Automation) system, and it is determined whether to send a text message reminder according to the meeting level, the above target business can be decomposed into multiple service nodes: meeting form building, meeting information data saving, meeting information pushing, meeting level judgment, message token obtaining, message pushing, and meeting notification result storing in the log table. By decomposing the target business, the complex target business can be refined into multiple service nodes that only provide a single service, so as to perform the service orchestration of individual service nodes, which helps to adapt to complex business environments and improve the service orchestration efficiency.
[0056] Step S102: For each service node, define the service information of each service node, where the service information is used to indicate the service execution process of the service node.
[0057] Specifically, the service information includes the functional type of the service node, the request data type when calling the service node, the result data type returned after the service node ends, the service node execution order, etc. By defining the service information for each service node, it is ensured that the service is executed according to the requirements of the service information, providing the corresponding service for the target user.
[0058] Step S103: Based on the business scenario of the target business and the service type to which each service node belongs, optimize the service information of each service node to obtain the configuration information of each service node, and set the configured service node to the publishable state.
[0059] Specifically, based on the business scenario of the target business and the service type of each service node obtained by decomposition, optimize the service information of each service node respectively to make its configuration more in line with the actual scenario requirements, and set it to the publishable state after configuration so that it can be called and executed.
[0060] Step S104: Configure the first service node for the target user and collect the execution data of the target user during the execution of the first service node by the target user.
[0061] Specifically, since the target business is usually decomposed in the order of business execution when decomposing, that is, the earlier ones among the multiple decomposed service nodes are executed first. Therefore, the configured first service node is assigned to the target user to provide the corresponding service for the target user. At the same time, during the execution of the first service node by the target user, the execution data of the target user is collected in real time. Among them, the execution data may include the input information, operation time, execution result, etc. For example, assume that the service node is for saving meeting information data. When the target user opens the meeting information menu, fills in the meeting-related information, and clicks "Save", collect the meeting details input by the target user and use it as the execution data of this service node.
[0062] Step S105: Transfer the execution data of the first service node to the next service node, and repeat the process of configuring the service node for the target user and collecting the execution data of the target user during the execution of the service node by the target user until all service nodes of the target business are completed.
[0063] Specifically, the execution data of the first service node will automatically flow to the next service node. During the flow process, the data follows the principle of only increasing and not decreasing to ensure the continuous transmission of all data of the target business. Subsequently, the subsequent service nodes are configured for the target user in sequence, and the execution data of the target user is continuously collected during the execution of each service node until all service nodes of the entire target business are completed. For example, in the meeting notification scenario, the execution data of the first service node (meeting information saving) will be transmitted to the next service node (meeting level judgment), and according to the judgment result, it will be transmitted to the message token acquisition node until the execution of all nodes is finally completed. Through the automatic data flow, it is ensured that the business process can be executed automatically, reducing manual intervention.
[0064] The service orchestration method of the low-code platform provided by the embodiments of the present invention divides a complex target business into multiple independent service nodes according to the business scenario. Each node completes a specific service task, defines its service information for each service node to ensure that it provides corresponding services for the target user, improves the service information of each service node based on the business scenario and service type, sets the optimized service node to a publishable state so that it can be called and executed, configures the first service node for the target user, collects the execution data of the target user, and transfers the execution data to the next service node and repeats the configuration and collection process until all service nodes are completed, ensuring seamless connection between each service node to form a complete business process. Through the low-code platform to achieve service orchestration, it reduces the workload of manual coding, improves the development efficiency, and adapts to the needs of different business scenarios, with high flexibility. Through detailed definition, optimized configuration, and data flow, it ensures the stable operation of each service node, realizing efficient, comprehensive, and flexible service orchestration.
[0065] In this embodiment, a service orchestration method of a low-code platform is provided, which can be used for the above-mentioned terminal. Figure 2 It is a flowchart of another service orchestration method of a low-code platform according to an embodiment of the present invention, as Figure 2 shown, and this process includes the following steps:
[0066] Step S201: Based on the business scenario of the target business, decompose the target business into multiple service nodes, and any service node provides one service of the target business. For details, please refer to Figure 1 Step S101 of the embodiment shown, which will not be elaborated here.
[0067] Step S202: For each service node, define the service information of each service node, and the service information is used to indicate the service execution process of the service node.
[0068] Specifically, the above step S202 includes:
[0069] In step S2021, a recommendation algorithm is used to determine whether the service node has a service reuse node.
[0070] Specifically, assume that the recommendation algorithm is the Apriori algorithm. Each sample service is decomposed to obtain the corresponding sample service nodes. Each sample service and its corresponding sample service nodes are combined into an item set. For example, if sample service B1 is decomposed into service nodes S1, S2, and S3, then the corresponding item set is {B1: [S1, S2, S3]}. Then, all sample service nodes are statistically analyzed, and each unique sample service node constitutes a single-item item set. For example, there are sample service nodes S1, S2, and S3, then the generated item sets are {S1}, {S2}, and {S3}. Then, the support degree of each item set is calculated, that is, the number of times it appears in all item sets is counted and then divided by the total number of item sets to obtain the support degree of this item set. The item sets with a support degree greater than or equal to a preset minimum support degree are filtered out. Repeat the above steps to change the item sets into multi-items, such as 2-items, {S1, S2}, {S1, S3}, {S2, S3}, etc., until no item sets that meet the minimum support degree can be filtered out. Calculate the association relationship between item sets, that is, confidence. For example, the probability that item set Y appears simultaneously when item set X is obtained. Use the minimum confidence as the filtering condition. When there is a new service, positively recommend the service nodes associated with it as service reuse nodes. When there is a new service, incorporate it and the service nodes decomposed from it into the dataset composed of the sample services used in the above training process, repeat the above process, and update the recommendation results periodically. Based on the Apriori algorithm obtained from the above training, determine whether any service node of the target service has a service reuse node. This service reuse node provides the same or similar services as this service node.
[0071] In some alternative embodiments, after using the recommendation algorithm to determine whether the service node has a service reuse node each time, multiple metrics in the algorithm will be updated to provide data support for service personnel to perform software development. Optionally, the multiple metrics include service-node reuse frequency of business, business reuse frequency, service-node call frequency, service-node execution time, and service-node execution status, etc.
[0072] In step S2022, when the service node has a service reuse node, reuse the service information of the service reuse node as the service information of the service node.
[0073] Specifically, since the service reuse node provides the same or similar services as its corresponding service node, and the service information is used to indicate how the service node provides services, the service information of the service reuse node can be directly used as the service information of the service node, reducing the workload of repeated definition and improving the service orchestration efficiency.
[0074] Alternatively, in step S2023, when the service node does not have a service reuse node, define the service information of the service node based on the business scenario of the target service.
[0075] Specifically, if the service node does not have a service reuse node, it is necessary to determine the specific information required for the service provided by the service node in this business scenario according to the business scenario of the target service.
[0076] Step S203, optimize the service information of each service node based on the business scenario of the target service and the service type to which each service node belongs, obtain the configuration information of each service node, and set the configured service node to the publishable state.
[0077] Specifically, the above step S203 optimizes the service information of each service node based on the business scenario of the target service and the service type to which each service node belongs, and obtains the configuration information of each service node, including:
[0078] Step S2031, for any service node, when the service node has a service reuse node, optimize the service information of the service reuse node as the configuration information of the service node based on the business scenario of the target service.
[0079] Specifically, considering that the business scenarios of the service reuse node and the service node may be different, and the specific execution details of the service may also be different, service personnel can fine-tune the service information of the service reuse node based on the business scenario of the target service to obtain the configuration information to adapt to the current business scenario.
[0080] Step S2032, when the service node does not have a service reuse node, call a service model conversion tool to optimize the service information of the service node based on the business scenario of the target service and the service type to which the service node belongs, and obtain the configuration information.
[0081] In some alternative embodiments, the above step S3032 includes:
[0082] Step a1, determine the configuration fields and service execution methods in the service information based on the service type to which the service node belongs.
[0083] Specifically, the service model conversion tool is a mechanism for mapping input parameters to specific method calls, usually determining which implementation class method should be called dynamically through configuration items. This approach can improve the flexibility and scalability of the system, allowing the system behavior to be adjusted through configuration without modifying the code. In the embodiments of the present invention, the service type is used as an input parameter, and the service model conversion tool maps the service type to a specific service execution method according to the service type and its corresponding configuration fields. Service nodes can be divided into multiple service types due to the different services they provide, and different service types have corresponding configuration fields and service execution methods. For example, for the service type of interface class service, its corresponding configuration fields are header verification and interface request parameters, etc.; for the service type of form class service, its corresponding configuration fields are field name, type, encoding, length verification, etc. Optionally, the service types of service nodes are illustrated by taking the following six categories as examples, and each service type is labeled with text:
[0084] (1) Judgment class service: Multiple service nodes are default to be executed in a preset order. When there are different processes based on the results returned by the service nodes, it supports multiple conditions to generate multiple results, and at the same time satisfies the combination of results according to the OR or AND rules, and different service nodes are directed according to different results, so as to meet the basic judgment function and realize the logical control of branches, loops, and sub-services of multiple services;
[0085] (2) Form class service: The form service management implemented based on the open-source AMIS framework can generate default forms and list pages according to field information;
[0086] (3) Mapping class service: Supports remapping the result data of other service nodes and supports EL expression rules;
[0087] (4) Interface class service: Supports calling rest interface requests and can set the header parameters and body parameters of the interface;
[0088] (5) Table data processing class service: Supports querying and processing operations on business tables;
[0089] (6) Javascript script class service: Processes data by enhancing the code.
[0090] Step a2, fill in the configuration fields based on the business scenario of the target business and the preset configuration information corresponding to the service type.
[0091] Specifically, different service types correspond to different preset configuration information. For example, if a certain service type can only be invoked through a specific interface and the standard format of the result return parameter flag, then this interface and the standard format belong to the preset configuration information of this service type. At the same time, considering the preset configuration information corresponding to the service type and the current business scenario, fill in the specific information in the configuration fields.
[0092] Step a3, use the filled service information and service execution method as the configuration information of the service node.
[0093] Specifically, use the filled service information and service execution method together as the configuration information of the service node to obtain accurate configuration information, so as to more accurately instruct the service node to provide services and improve the accuracy of service orchestration.
[0094] Step S204, configure the first service node to the target user and collect the execution data of the target user during the execution of the first service node by the target user. For details, please refer to Figure 1 Step S104 of the illustrated embodiment, which will not be elaborated here.
[0095] Step S205, transfer the execution data of the first service node to the next service node, and repeat the process of configuring the service node to the target user and collecting the execution data of the target user during the execution of the service node by the target user until all service nodes of the target business are completed. For details, please refer to Figure 1 Step S105 of the illustrated embodiment, which will not be elaborated here.
[0096] Step S206, encapsulate the execution data obtained by the target user for each service node.
[0097] Specifically, when the target user finishes executing each service node, encapsulate the obtained execution data, so that after all service nodes of the target business are executed, a complete business processing record between the target user and the target business can be obtained, which helps to discover potential problems and improvement points in the service orchestration process based on the execution data, thereby continuously optimizing the service quality and user experience.
[0098] Step S207, optimize the recommendation algorithm based on the correspondence between the target business and multiple service nodes and the configuration information of each service node.
[0099] Specifically, after all service nodes of the target business are executed, retrain the recommendation algorithm based on the result obtained from this service orchestration. The training process refers to the above-mentioned step S2021, which helps to improve the accuracy of judging the reuse possibility when executing other businesses.
[0100] The service orchestration method of the low-code platform provided by the embodiments of the present invention divides complex target services into multiple independent service nodes according to the business scenario. Each node completes a specific service task. The service information of each service node is defined to ensure that it provides corresponding services for target users. Based on the business scenario and service type, the service information of each service node is improved, and the optimized service nodes are set to the publishable state so that they can be called and executed. The first service node is configured for the target user, and the execution data of the target user is collected. The execution data is transferred to the next service node and the configuration and collection process is repeated until all service nodes are completed, ensuring seamless connection between service nodes and forming a complete business process. Through the low-code platform, service orchestration is realized, reducing the workload of manual coding, improving development efficiency, adapting to the requirements of different business scenarios, and having high flexibility. Through detailed definition, optimized configuration, and data transfer, the stable operation of each service node is ensured, realizing efficient, comprehensive, and flexible service orchestration.
[0101] In this embodiment, a service orchestration device for a low-code platform is also provided. This device is used to implement the above embodiments and preferred implementation manners, and those that have been described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that realizes a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.
[0102] This embodiment provides a service orchestration device for a low-code platform, as Figure 3 shown, including:
[0103] A decomposition module 301, configured to decompose a target service into multiple service nodes, and any one of the service nodes provides one service of the target service.
[0104] A definition module 302, configured to define, for each service node, the service information of each service node, and the service information is used to indicate the service execution process of the service node.
[0105] A configuration module 303, configured to optimize the service information of the service nodes based on the target service, the service type to which each service node belongs, and the service information, obtain the configuration information of each service node, and set the configured service nodes to the publishable state.
[0106] An execution module 304, configured to configure the first service node for the target user and collect the execution data of the target user during the process of the target user executing the first service node.
[0107] An arrangement module 305, configured to transfer the execution data of the first service node to the next service node, repeatedly configure service nodes for a target user, and collect the execution data of the target user during the execution of the service nodes by the target user until all service nodes of the target service are completed.
[0108] In some alternative embodiments, the definition module 302 includes:
[0109] A judgment unit, configured to use a recommendation algorithm to judge whether a service node has a service reuse node.
[0110] A reuse unit, configured to, when a service node has a service reuse node, reuse the service information of the service reuse node as the service information of the service node.
[0111] Alternatively, a definition unit, configured to, when a service node does not have a service reuse node, define the service information of the service node based on the business scenario of the target service.
[0112] In some alternative embodiments, the configuration module 303 includes:
[0113] A first configuration unit, configured to, for any service node, when the service node has a service reuse node, optimize the service information of the service reuse node as the configuration information of the service node based on the business scenario of the target service.
[0114] A second configuration unit, configured to, when a service node does not have a service reuse node, call a service model conversion tool based on the business scenario of the target service and the service type to which the service node belongs, optimize the service information of the service node, and obtain configuration information.
[0115] In some alternative embodiments, the second configuration unit includes:
[0116] A first determination unit, configured to determine the configuration fields and service execution methods in the service information based on the service type to which the service node belongs.
[0117] A filling unit, configured to fill the configuration fields based on the business scenario of the target service and the preset configuration information corresponding to the service type.
[0118] A second determination unit, configured to use the filled service information and service execution methods as the configuration information of the service node.
[0119] In some alternative embodiments, the apparatus further includes:
[0120] An optimization module, configured to optimize the recommendation algorithm based on the correspondence between the target service and multiple service nodes and the configuration information of each service node.
[0121] In some alternative embodiments, the apparatus further includes:
[0122] An encapsulation module, configured to encapsulate the execution data obtained by the target user for each service node.
[0123] The further function descriptions of the above-mentioned various modules and units are the same as those in the corresponding embodiments above, and will not be elaborated here.
[0124] The service orchestration apparatus of the low-code platform in this embodiment is presented in the form of functional units. Here, the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and a memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.
[0125] An embodiment of the present invention further provides a computer device having the above-mentioned Figure 3 service orchestration apparatus of the low-code platform as shown.
[0126] Please refer to Figure 4 , Figure 4 which is a schematic structural diagram of a computer device provided by an alternative embodiment of the present invention. As shown in Figure 4 , the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including a high-speed interface and a low-speed interface. Each component communicates with each other using different buses and can be installed on a common motherboard or installed in other ways as needed. The processor can process instructions executed within the computer device, including instructions stored in the memory or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some alternative embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a set of blade servers, or a multi-processor system). Figure 4 In
[0127] Processor 10 can be a central processing unit, a network processor, or a combination thereof. Among them, processor 10 can further include a hardware chip. The above-mentioned hardware chip can be an application specific integrated circuit, a programmable logic device, or a combination thereof. The above-mentioned programmable logic device can be a complex programmable logic device, a field programmable gate array, a general array logic, or any combination thereof.
[0128] Among them, the memory 20 stores instructions that can be executed by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiments.
[0129] The memory 20 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some alternative embodiments, the memory 20 may optionally include a memory remotely provided relative to the processor 10, and these remote memories can be connected to the computer device through a network. Examples of the above networks include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.
[0130] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk, or a solid-state drive; the memory 20 may also include a combination of the above types of memories.
[0131] The computer device further includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30, and the output device 40 may be connected through a bus or other means. Figure 4 Taking the connection through the bus as an example.
[0132] The input device 30 can receive input digital or character information, and generate key signal inputs related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a trackpad, a touchpad, a pointing stick, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (such as an LED), and a tactile feedback device (such as a vibration motor), etc. The above display device includes, but is not limited to, a liquid crystal display, a light-emitting diode, a display, and a plasma display. In some alternative embodiments, the display device may be a touch screen.
[0133] Embodiments of the present invention also provide a computer-readable storage medium. The methods according to the embodiments of the present invention can be implemented in hardware, firmware, or be implemented as computer code that can be recorded on a storage medium, or be implemented as computer code that is originally stored in a remote storage medium or a non-transitory machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, so that the methods described herein can be processed by such software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by the computer, the processor, or the hardware, the methods shown in the above embodiments are implemented.
[0134] A part of the present invention can be applied as a computer program product, such as computer program instructions. When executed by a computer, through the operation of the computer, the methods and / or technical solutions according to the present invention can be called or provided. Those skilled in the art should be able to understand that the forms of existence of computer program instructions in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Herein, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.
[0135] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations all fall within the scope defined by the appended claims.
Claims
1. A service orchestration method for a low-code platform, characterized in that: The method comprises: Based on the service scenario of the target service, the target service is decomposed into multiple service nodes, and any service node provides a service of the target service; For each service node, define service information of each service node, where the service information is used to indicate a service execution process of the service node; Based on the business scenario of the target business and the service type of each service node, optimize the service information of each service node, obtain the configuration information of each service node, and set the configured service node to a publishable state; configuring the first service node to the target user, and collecting execution data of the target user during the process of the target user executing the first service node; The execution data of the first service node is transferred to the next service node, and the process of configuring the service node to the target user and collecting the execution data of the target user during the target user's execution of the service node is repeated until all service nodes of the target business are completed.
2. The method according to claim 1, characterized in that For each service node, the service information of each service node is defined, including: Using a recommendation algorithm, determining whether the service node has a service reuse node; In the case where the service node has a service multiplexing node, multiplexing the service information of the service multiplexing node as the service information of the service node; or, In the case that the service node does not have a service reuse node, the service information of the service node is defined based on the service scenario of the target service.
3. The method according to claim 2, characterized in that The optimizing the service information of each service node based on the service scenario of the target service and the service type of each service node to obtain the configuration information of each service node includes: For any service node, if the service node has a service reuse node, based on the service scenario of the target service, optimizing the service information of the service reuse node as the configuration information of the service node; In the case that the service node does not have a service reuse node, based on the business scenario of the target business and the service type to which the service node belongs, a service model conversion tool is called to optimize the service information of the service node to obtain the configuration information.
4. The method according to claim 3, characterized in that In the case where the service node does not have a service reuse node, based on the business scenario of the target business and the service type to which the service node belongs, calling a service model conversion tool to optimize the service information of the service node to obtain the configuration information includes: Determine the configuration fields and service execution methods in the service information based on the service type to which the service node belongs; Filling the configuration field based on the business scenario of the target business and the preset configuration information corresponding to the service type; The filled service information and the service execution method are used as the configuration information of the service node.
5. The method according to claim 2, characterized in that: The method further comprises: Based on the correspondence between the target business and the multiple service nodes and the configuration information of each service node, a recommendation algorithm is optimized.
6. The method according to claim 1, characterized in that The method further comprises: The execution data obtained by the target user executing each service node is encapsulated.
7. A service orchestration device for a low-code platform, characterized in that: The device comprises: A decomposition module, used to decompose the target business into multiple service nodes, any service node provides a service of the target business; A definition module, used for defining service information of each service node for each service node, wherein the service information is used for indicating a service execution process of the service node; A configuration module, configured to optimize the service information of the service node based on the target business, the service type and service information of each service node, obtain the configuration information of each service node, and set the configured service node to a publishable state; An execution module, configured to configure the first service node to a target user, and collect execution data of the target user during the process of the target user executing the first service node; The orchestration module is used to transfer the execution data flow of the first service node to the next service node, repeatedly configure the service node to the target user, and collect the execution data of the target user during the process of the target user executing the service node, until all service nodes of the target business are completed.
8. A computer device, characterized in that: include: A memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the service orchestration method of the low-code platform described in any one of claims 1 to 6 by executing the computer instructions.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, which are used to enable a computer to execute the service orchestration method for a low-code platform according to any one of claims 1 to 6.
10. A computer program product, characterized in that It includes computer instructions, which are used to enable a computer to execute the service orchestration method of the low-code platform described in any one of claims 1 to 6.