CN114518908B

CN114518908B - Service orchestration method, medium, device and computing equipment

Info

Publication number: CN114518908B
Application number: CN202210147997.8A
Authority: CN
Inventors: 王永亮; 陈志辉; 黄秋霞; 云娜; 余方正; 刘源; 朱一飞
Original assignee: Hangzhou Netease Cloud Music Technology Co Ltd
Current assignee: Hangzhou Netease Cloud Music Technology Co Ltd
Priority date: 2022-02-17
Filing date: 2022-02-17
Publication date: 2024-03-22
Anticipated expiration: 2042-02-17
Also published as: CN114518908A

Abstract

Embodiments of the present disclosure provide a service orchestration method, medium, apparatus, and computing device. Providing an arrangement interface through terminal equipment, wherein the arrangement interface comprises a node type area, an editing area and a node configuration area, the node type area comprises node controls of different types, and the method comprises the following steps: displaying the plurality of target nodes in the edit area in response to a drag operation from the plurality of target node controls to the edit area; determining attributes of the plurality of target nodes in response to configuration operations for the plurality of target nodes in the node configuration area; determining a connection relationship between a plurality of target nodes in response to a drag operation between the editing area for each target node; and responding to touch operation of a storage control on the arrangement interface, sending a storage request to a server, wherein the storage request is used for indicating the server to generate a DAG arrangement service file according to the attribute and the connection relation of a plurality of target nodes. The complexity of the service orchestration process is reduced.

Description

Service orchestration method, medium, device and computing equipment

Technical Field

Embodiments of the present disclosure relate to the field of computer technology, and more particularly, to a service orchestration method, medium, apparatus, and computing device.

Background

This section is intended to provide a background or context to the embodiments of the disclosure recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

The data service is used as the uppermost layer of unified data middle stage construction, the details of bottom data storage and calculation are not required to be concerned, the data of the data warehouse can be provided for a data user in a service and interface mode, and the data utilization rate is improved.

In data services, it is often involved to invoke a plurality of data services to realize a large data service, and service arrangement is required for various data services. The service arrangement refers to a process of developing each data service, expanding corresponding functional service according to the requirement of business functions, binding with an API interface and providing service outwards in the form of an API.

The current data arrangement service is mainly to edit codes in the background according to the requirements of service functions to combine each data service, so as to realize corresponding services.

Disclosure of Invention

The present disclosure provides a service orchestration method, medium, apparatus, and computing device to reduce the complexity of service orchestration.

In a first aspect of the embodiments of the present disclosure, a service orchestration method is provided, where an orchestration interface is provided by a terminal device, where the orchestration interface includes a node type area, an editing area, and a node configuration area, and the node type area includes node controls of different types, and the method includes:

displaying a plurality of target nodes in the editing area in response to a drag operation from the plurality of target node controls to the editing area;

determining attributes of the plurality of target nodes in response to configuration operations for the plurality of target nodes in the node configuration area;

determining a connection relationship between the plurality of target nodes in response to a drag operation between the editing area for each of the target nodes;

and responding to touch operation of a storage control on the arrangement interface, and sending a storage request to a server, wherein the storage request is used for indicating the server to generate a directed acyclic graph DAG arrangement service file according to the attributes of the plurality of target nodes and the connection relation.

In a second aspect of embodiments of the present disclosure, there is provided a service orchestration method, comprising:

Receiving a save request from a terminal device, wherein the save request comprises attributes of a plurality of target nodes and connection relations among the plurality of target nodes;

and generating DAG orchestration service files according to the attributes of the target nodes and the connection relation.

In a third aspect of the embodiments of the present disclosure, there is provided a service orchestration apparatus that provides an orchestration interface through a terminal device, where the orchestration interface includes a node type area, an edit area, and a node configuration area, the node type area includes node controls of different types, and the apparatus includes:

the display module is used for responding to dragging operation from a plurality of target node controls to the editing area and displaying the plurality of target nodes in the editing area;

a first processing module configured to determine attributes of the plurality of target nodes in response to configuration operations for the plurality of target nodes at the node configuration area;

a second processing module for determining a connection relationship between the plurality of target nodes in response to a drag operation between the editing area for each of the target nodes;

and the receiving and transmitting module is used for responding to the touch operation of the storage control on the arrangement interface and transmitting a storage request to a server, wherein the storage request is used for indicating the server to generate a DAG arrangement service file according to the attributes of the plurality of target nodes and the connection relation.

In a fourth aspect of embodiments of the present disclosure, there is provided a service orchestration device, comprising:

the receiving and transmitting module is used for receiving a preservation request from the terminal equipment, wherein the preservation request comprises attributes of a plurality of target nodes and connection relations among the plurality of target nodes;

and the processing module is used for generating DAG arrangement service files according to the attributes of the target nodes and the connection relation.

In a fifth aspect of embodiments of the present disclosure, there is provided a computing device comprising: at least one processor and memory;

the memory stores computer-executable instructions;

the at least one processor executing computer-executable instructions stored in the memory cause the at least one processor to perform the service orchestration method according to any one of the first aspects, or cause the at least one processor to perform the service orchestration method according to any one of the second aspects.

In a sixth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the service orchestration method according to any one of the first aspects or implement the service orchestration method according to any one of the second aspects.

In a seventh aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program; the computer program when executed implements the service orchestration method according to any one of the first aspects or the service orchestration method according to any one of the second aspects.

The service orchestration method, medium, device and computing equipment provided by the embodiment of the disclosure provide an orchestration interface through terminal equipment, the orchestration interface comprises a node type area, an editing area and a node configuration area, the node type area comprises node controls of different types, a plurality of target nodes are firstly displayed in the editing area in response to dragging operations from the plurality of target node controls to the editing area, then the attribute of the plurality of target nodes is determined in response to configuration operations of the plurality of target nodes in the node configuration area, and the connection relation among the plurality of target nodes is determined in response to dragging operations of the editing area to the target nodes; after the attributes and the connection relations of the plurality of target nodes are determined, a storage request is sent to a server in response to touch operation of a storage control on an arrangement interface, so that the server generates DAG arrangement service files according to the attributes and the connection relations of the plurality of target nodes. According to the scheme of the embodiment of the disclosure, a service arrangement platform is provided, corresponding interface operation is executed on an arrangement interface of the service arrangement platform, then a storage request is sent to a server through a storage control, so that a DAG arrangement service file is generated, service arrangement can be realized, combination of data services is not needed through a background editing code, connection relation between target nodes and attribute configuration of the target nodes are determined through dragging operation, and combination of the data services is realized.

Drawings

The above, as well as additional purposes, features, and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description when read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings, in which:

FIG. 1 is a schematic diagram of a service orchestration;

FIG. 2 is a schematic diagram II of a service orchestration;

fig. 3 is a schematic view of an application scenario provided in an embodiment of the present disclosure;

fig. 4 is a flowchart of a service orchestration method according to an embodiment of the present disclosure;

FIG. 5 is a schematic illustration of an orchestration interface provided by embodiments of the present disclosure;

FIG. 6 is a schematic diagram of a DAG provided by an embodiment of the present disclosure;

fig. 7 is a schematic diagram of node configuration provided in an embodiment of the present disclosure;

fig. 8 is a schematic diagram of target node deletion provided in an embodiment of the present disclosure;

FIG. 9 is a schematic diagram of determining connection relationships provided by embodiments of the present disclosure;

FIG. 10 is a diagram of two DAGs provided by an embodiment of the present disclosure;

FIG. 11 is a schematic diagram of a DAG graph save and execute architecture provided by an embodiment of the present disclosure;

FIG. 12 is a diagram illustrating a retry request according to an embodiment of the present disclosure;

FIG. 13 is a second exemplary retry request provided in an embodiment of the present disclosure;

FIG. 14 is a schematic diagram of a storage medium provided by an embodiment of the present disclosure;

fig. 15 is a schematic structural diagram of a service arrangement device according to an embodiment of the present disclosure;

fig. 16 is a schematic structural diagram of a service arrangement device according to an embodiment of the present disclosure;

fig. 17 is a schematic structural diagram of a computing device provided by an embodiment of the present disclosure.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

Detailed Description

The principles and spirit of the present disclosure will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are presented merely to enable one skilled in the art to better understand and practice the present disclosure and are not intended to limit the scope of the present disclosure in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Those skilled in the art will appreciate that embodiments of the present disclosure may be implemented as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the following forms, namely: complete hardware, complete software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to embodiments of the present disclosure, a service orchestration method, medium, apparatus, and computing device are presented. In this document, it should be understood that any number of elements in the drawings is for illustration and not limitation, and that any naming is used only for distinction and not for any limitation.

The basic concepts to which the present disclosure relates will first be described.

API: application Programming Interface, application programming interface.

DAG: directed Acyclic Graph in graph theory, a directed acyclic graph is one if it cannot go back to any vertex through several edges, starting from that vertex.

Service orchestration: service orchestration is the ability to conduct service development by way of simple drag-and-drop flow orchestration and parameter configuration, and supports the re-composition orchestration of developed services. The user can rapidly develop services and expand richer business functions in a graphical arrangement mode in the service arrangement editor, and can bind with an API interface to provide services in an API mode.

The principles and spirit of the present disclosure are explained in detail below with reference to several representative embodiments thereof.

Summary of The Invention

The data service is used as the uppermost layer of unified data middle stage construction, can shield a plurality of details of bottom data storage and calculation, simplify and strengthen the use of data, provide data warehouse data for a data user in a service and interface mode, avoid chimney type construction, strengthen the development and delivery efficiency of data API, and improve the data utilization rate.

When providing data services externally, it is generally necessary to arrange a plurality of data services according to service functions to develop the data services, and bind the developed data services with an API interface, so as to provide the data services in the form of the API interface.

An implementation of two service orchestration in the related art is described below in connection with fig. 1 and 2.

Fig. 1 is a schematic diagram of a service orchestration. Referring to fig. 1, service orchestration is implemented by a workflow composed of a plurality of service nodes, such as an API service node-1, an API service node-2, an API service node-3 and a conversion node in fig. 1, where the API service node is used for performing data processing, the conversion node is used for performing branch condition judgment, and each service node forms a complete workflow through a scheduling engine. When the data service is invoked, the scheduling engine sequentially executes each service node according to the setting, transmits parameters output by the service node, and automatically manages state transition of each service node.

Fig. 2 is a schematic diagram of a service orchestration. Referring to fig. 2, the exemplary service orchestration is performed by a gateway that processes and converts data. When a request arrives at the gateway, the gateway invokes a plurality of back-end services (such as the services provided by the API service node-1, the API service node-2, the API service node-3, etc. as illustrated in fig. 2), processes the returned data of each service (including filtering, moving, renaming, packaging, unpacking, etc.) on the gateway, and finally the gateway integrates the data and returns the integrated data to the front-end.

The inventor finds that in the service arrangement scheme illustrated in fig. 1, after each service node is scheduled by the scheduling engine to form a complete workflow, the service nodes can only be executed downwards in sequence, and the service arrangement scheme is a serial arrangement scheme, and for a certain service node, retry and anomaly detection cannot be performed, so that when the data service is abnormal, problem positioning is difficult to accurately perform. Meanwhile, the conversion node in the service arrangement scheme illustrated in fig. 1 can only perform the judgment of simpler branch conditions, and cannot meet the requirement of more complex condition judgment. The service orchestration scheme illustrated in fig. 2 is implemented by the gateway, the logic operations among the API service nodes are all processed by the gateway, the dependency on the gateway is strong, the service orchestration scheme belongs to a service aggregation operation with high coupling, and the service orchestration availability and flexibility are low. Furthermore, the service arrangement schemes illustrated in fig. 1 and fig. 2 also need to implement the combination of data services by editing codes in the background according to the service functions, and the service arrangement process is complex.

Having described the basic principles of the present disclosure, various non-limiting embodiments of the present disclosure are specifically described below.

Application scene overview

A suitable application scenario for embodiments of the present disclosure will first be described with reference to fig. 3.

Fig. 3 is a schematic view of an application scenario provided by an embodiment of the present disclosure, as shown in fig. 3, including a terminal device 31 and a server 32, where the terminal device 31 is used as a front end to provide an orchestration interface for building a DAG graph, and performing drag configuration on service orchestration.

An ngix cluster and an API gateway cluster may be further included between the terminal device 31 and the server 32, where the ngix cluster may be regarded as a part of the front end and is mainly used to perform operations of accepting a request, distributing a request, responding to a request, and the like; the API gateway cluster is mainly used for executing some authority verification operations, taking an e-commerce platform as an example, if the data service is order information searching and the entering parameter of the data service is order number, after the order number and the searching request reach the API gateway cluster, the API gateway cluster needs to verify the currently logged-in user account number, password and the like, and after meeting the requirements, the searching request is sent to the server for processing.

The data source is used for storing relevant information of the data service, the cache service is used for caching some information which is queried historically, when some information needs to be queried, the information can be searched from the cache service first, and if the information does not exist in the cache service, the information is further searched from the data source and cached in the cache service. The information which is searched in history is cached through the caching service, so that the response speed of the information can be improved. The time sequence database is mainly used for storing time of some historical operations or historical information, and is arranged according to time sequence, and the API configuration management service is mainly used for configuring other management services, and the like.

In the embodiment of fig. 3, two schemes for providing data services are illustrated, wherein each resource group in the data service API provides a different service, and the services provided by each resource group are not service orchestrated. The API orchestration service performs service orchestration, and finally the resource group A provides an API interface outwards, and the data service can call services of other resource groups according to the service orchestration, for example, the services of the resource group A, the resource group B and the resource group N are called in FIG. 3.

Exemplary method

A service orchestration method according to an exemplary embodiment of the present disclosure is described below with reference to fig. 4 in conjunction with the application scenario of fig. 3. It should be noted that the above application scenario is only shown for the convenience of understanding the spirit and principles of the present disclosure, and the embodiments of the present disclosure are not limited in any way in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.

Fig. 4 is a flow chart of a service orchestration method provided by an embodiment of the present disclosure, where an orchestration interface is provided by a terminal device, where the orchestration interface includes a node type area, an editing area, and a node configuration area, and the node type area includes different types of node controls, as shown in fig. 4, and the method may include:

And S41, displaying the plurality of target nodes in the editing area in response to drag operation from the plurality of target node controls to the editing area.

The execution body of the embodiment of the disclosure is a terminal device, and the terminal device may be, for example, a mobile phone, a computer, a tablet, etc., and an arrangement interface for performing service arrangement is displayed on the terminal device.

Fig. 5 is a schematic view of an orchestration interface provided by an embodiment of the present disclosure, and as shown in fig. 5, the orchestration interface 50 includes a node type area 51, an edit area 52, and a node configuration area 53. Among other things, node type area 51 includes different types of node controls, and the node types may include, for example, a start node, a condition node, an API node, and so on. In fig. 5, an API node control 511 and a conditional node control 512 are illustrated in the node type area 51.

Since the service orchestration is made up of multiple service nodes, multiple target nodes can be set as service nodes according to the needs of the traffic function. Specifically, a drag operation from the plurality of target node controls to the editing area 52 may be performed such that the plurality of target nodes are displayed in the editing area 52.

Taking the API node in fig. 5 as an example, the cursor of the terminal device may be moved to the API node control 511, and then after clicking on the API node control 511 and dragging to the editing area 52, the editing area 52 displays an API node, which is one of the multiple target nodes.

For any target node, a drag operation from the target node control to the editing area 52 can be performed according to the target node control corresponding to the target node, so that the corresponding target node is displayed in the editing area.

S42, determining attributes of the plurality of target nodes in response to configuration operations of the plurality of target nodes in the node configuration area.

Different types of target nodes have different properties, e.g. the properties of the start node comprise the entry and the properties of the API node comprise the data processing information. The attributes of the target nodes of the same type may also be different, for example, a condition node, and if two condition nodes are included in the plurality of target nodes, the two condition nodes may include different judging conditions, and the different judging conditions are different attributes of the two condition nodes.

For any one target node, the attribute of the target node may be configured in the node configuration area 53. The attribute items that may be configured by different types of target nodes in the node configuration area 53 may be different, for example, for a starting node, only input needs to be performed in the node configuration area 53, for a condition node, a determination condition of the condition node may need to be input in the node configuration area 53, and a branch executed according to a determination result, and so on.

S43, in response to the drag operation between the editing area and each target node, determining the connection relation between the plurality of target nodes.

After dragging the plurality of target node controls to the editing area, the plurality of target nodes are displayed in the editing area, and the plurality of target nodes are in scattered states, so that dragging operations for the plurality of target nodes need to be performed in the editing area 52 to determine connection relations among the plurality of target nodes, so that the target nodes are coherent to form a whole.

It should be noted that, the execution among S41, S42, and S43 is not limited to a strict sequence, for a plurality of target nodes, S41 may be executed first, after the plurality of target nodes are displayed in the editing area 52, then configuration operation is sequentially performed on each target node, an attribute of each target node is determined, and after the attribute configuration is completed, S43 is executed, and a connection relationship is determined; after displaying a certain target node in the editing area, the configuration operation of the target node may be performed first, and then the next target node may be displayed in the editing area 52 through the drag operation; the configuration operation of one target node may also be performed after the other target node is displayed in the edit area 52, and so on.

That is, the drag operation of the target node control to the editing area 52, the configuration operation of the target node, and the drag operation between the target nodes may be interspersed as long as it is satisfied that the target node is displayed in the editing area 52 when the attribute configuration is performed on the target node, and that the target node for which the drag operation is performed is displayed in the editing area 52 when the drag operation is performed between the target nodes.

S44, a storage request is sent to the server in response to touch operation of a storage control on the arrangement interface, wherein the storage request is used for indicating the server to generate DAG arrangement service files according to the attribute and the connection relation of the plurality of target nodes.

The steps S41 to S43 executed on the terminal device are all front-end execution steps, after the service arrangement is completed, the terminal device may click on a save control on the arrangement interface 50, and send a save request to the server in response to a touch operation for the save control, where the save request includes attributes and connection relationships of multiple target nodes, where the attributes of multiple nodes are attributes configured for each target node through configuration operation in S42, and the connection relationships between multiple target nodes are connection relationships determined according to drag operations for each target node in S43.

After receiving the storage request, the server can acquire the attributes of the plurality of target nodes and the connection relation among the plurality of target nodes, and then generates a DAG arrangement service file according to the attributes of the plurality of target nodes and the connection relation among the plurality of target nodes, wherein the DAG arrangement service file can be used for providing data services to the outside. For example, after inputting the input parameters, the input parameters are processed according to the attribute of the target node recorded in the DAG editing service file, and then the parameters output by the target node are transferred to the next target node according to the connection relation between the target nodes until the processing result of the input parameters is finally output.

By means of the embodiment shown in fig. 4, the terminal device implements service orchestration, and determines the attributes and connection relationships of multiple target nodes. The process by which the server generates DAG orchestration service files is described below.

After determining the attributes of the plurality of target nodes and the connection relations among the plurality of target nodes, the terminal equipment responds to the touch operation aiming at the storage control and sends a storage request to the server, wherein the storage request comprises the attributes of the plurality of target nodes and the connection relations among the plurality of target nodes.

The storage request is used for triggering the server to generate the DAG arrangement service file, and the server can acquire the attributes of the plurality of target nodes and the connection relation among the plurality of target nodes after receiving the storage request from the terminal equipment, and then generates the DAG arrangement service file according to the attributes and the connection relation of the plurality of target nodes.

The DAG orchestration service file is used for recording the orchestration result of the terminal device, and the DAG orchestration service file may include basic information of service orchestration, and further includes the recorded attribute of the target node and the connection relationship between the plurality of target nodes. The DAG editing service file can provide data service to the outside, and after the input of the input parameters, the DAG editing service file can process the input parameters according to the recorded attribute of the target nodes and the connection relation between the target nodes, and finally, the processing result of the DAG editing service file on the input parameters is output.

The DAG orchestration service file represents a plurality of target nodes and connection relations among the target nodes to form a DAG graph, fig. 6 is a DAG schematic diagram provided by an embodiment of the disclosure, as shown in fig. 6, from a start node to a condition node, then to an API node 1 and/or an API node 2 to a script node 3, finally to an end node, where the DAG graph is formed among the target nodes, and after clicking and storing, the DAG graph illustrated in fig. 6 may trigger a server to generate the DAG orchestration service file according to the attribute and the connection relation of each target node. If, in the target node illustrated in fig. 6, the target node is switched from the start node to the condition node, then to the API node 1 and/or the API node 2, then the API node 1 and/or the API node 2 is switched to the script node 3, and the script node 3 is switched to the start node, the DAG graph is not formed, so that it is not satisfactory, and the DAG orchestration service file cannot be generated according to the attribute and the connection relationship of the target node.

According to the service arrangement method provided by the embodiment of the disclosure, an arrangement interface is provided through a terminal device, the arrangement interface comprises a node type area, an editing area and a node configuration area, the node type area comprises node controls of different types, a plurality of target nodes are displayed in the editing area firstly in response to dragging operations from the plurality of target node controls to the editing area, then the attribute of the plurality of target nodes is determined in response to configuration operations of the plurality of target nodes in the node configuration area, and the connection relation among the plurality of target nodes is determined in response to dragging operations of the editing area to the plurality of target nodes; after the attributes and the connection relations of the plurality of target nodes are determined, a storage request is sent to a server in response to touch operation of a storage control on an arrangement interface, so that the server generates DAG arrangement service files according to the attributes and the connection relations of the plurality of target nodes. According to the scheme of the embodiment of the disclosure, a service arrangement platform is provided, corresponding interface operation is executed on an arrangement interface of the service arrangement platform, then a storage request is sent to a server through a storage control, so that a DAG arrangement service file is generated, service arrangement can be realized, combination of data services is not needed through a background editing code, connection relation between target nodes and attribute configuration of the target nodes are determined through dragging operation, and combination of the data services is realized.

On the basis of any one of the above embodiments, the service orchestration process will be described in detail with reference to the following embodiments.

The attribute configuration process of the target node will be described first with reference to fig. 7. Fig. 7 is a schematic view of node configuration provided in an embodiment of the present disclosure, as shown in fig. 7, on an editing interface 70, for any one target node displayed in an editing area, the target node may be clicked, and a terminal device displays an editing control of the target node in response to a touch operation for the target node.

In fig. 7, an editing process for the start node 71 is illustrated, and after clicking on the start node 71, an editing control 72 of the start node 71 is displayed on the editing area, and the editing control 72 is used to trigger an editing step for the start node 71. The edit control 72 includes a test node sub-control 73, the test node sub-control 73 is used for triggering an attribute configuration step of the start node 71, the test node sub-control 73 can be clicked, and the terminal device responds to the touch operation for the test node sub-control 73 to display an attribute setting interface corresponding to the target node in a node configuration area, such as an attribute setting interface 74 of the start node 71 shown in fig. 7. The attribute setting interface is a sub-interface of the editing interface.

The attribute of the target node can be configured on the attribute setting interface, and after the configuration is completed, the terminal equipment responds to the configuration operation aiming at the attribute setting interface to determine the attribute of the target node. The target node mainly comprises a starting node, a task node, a condition node and an ending node, wherein the task node comprises an API node and a script node. The same attribute configuration item, e.g., node name, may be included for different types of target nodes, and each target node may also include a respective different attribute configuration item. The description of the respective different attribute configuration items will be made below for the different types of nodes.

The starting node is a node existing in the DAG graph arranged for each service, and the starting node only receives the entry and does not execute business logic, so that the attribute configuration of the starting node mainly comprises the configuration of the entry. Specifically, on the attribute setting interface of the start node, a parameter entering input box may be included, a corresponding parameter entering may be input in the parameter entering input box, and the terminal device determines the parameter entering of the start node according to the input data in response to the input operation in the parameter entering input box.

As illustrated in fig. 7 for the property settings interface 74 of the start node, the entry box may further include at least one of a parameter name, a parameter type, an input value, a default value, and may add or delete certain property configuration items as needed, etc. Taking the e-commerce platform to query order information as an example, the entering parameters can be the order numbers, the order numbers can be input into the entering parameter input box according to the orders to be queried, the parameter names can be the order numbers, the parameter types can be integer types, and the like.

The API node is a node for data processing, the attribute configuration item of the API node comprises data processing information, the attribute setting interface of the API node comprises an API input box, a corresponding script can be input in the API input box, and the terminal equipment responds to the input operation of the API input box of the attribute setting interface and determines the data processing information corresponding to the API node according to the input script.

The script node is a node for processing data, the attribute configuration item of the script node comprises data processing information, the attribute setting interface of the script node comprises a script input box, a corresponding script can be input in the script input box, and the terminal equipment responds to the input operation of the script input box of the attribute setting interface and determines the data processing information corresponding to the script node according to the input script.

The condition node is a node for performing a circulation condition judgment, is associated with an edge of a connected target node, and is used for judging whether a downstream target node needs to be executed. The attribute setting interface of the condition node comprises a condition input box, a judging condition can be input in the condition input box, and the terminal equipment responds to the input operation of the condition input box of the attribute setting interface and determines the condition information of the condition node according to the input judging condition. The input judgment condition may be a rule expression or a scripting language such as Python, groovy, and if the judgment condition is a scripting language, an open-source executor may be required to be introduced for executing the script.

The end node is also a node existing in the DAG graph arranged for each service, and the end node is used for summarizing and outputting the processing result of the task node, and the attribute configuration item of the end node can comprise summarizing information, for example. The attribute setting interface of the end node may include a summary information input box, in which summary information may be input, the summary information being used to indicate how to aggregate the processing results of the task node, thereby outputting the results.

In the above embodiments, the procedure of adding a target node and configuring the attribute of the target node by a drag operation from the target node control to the edit area has been described, and when there are redundant target nodes in the edit area, the target node may be deleted.

Fig. 8 is a schematic diagram of target node deletion provided in an embodiment of the present disclosure, as shown in fig. 8, for a start node 71, after clicking on the start node 71, an editing control 72 is displayed in an editing area, where the editing control 72 may further include a delete sub-control 80 in addition to a test node sub-control 73, and the delete sub-control 80 is used to trigger deletion of the start node 71.

For any target node, clicking a deletion sub-control corresponding to the target node, and stopping displaying the target node in the editing area by the terminal equipment in response to the touch operation of the deletion sub-control. As in fig. 8, after clicking the delete child control 80, the start node 71 is deleted and is no longer displayed in the edit area.

The process of attribute configuration of the target nodes is described in the above-described embodiment, and the process of determining the connection relationship between the target nodes will be described below with reference to fig. 9. In the embodiment of the disclosure, the terminal equipment determines the connection relation between the target nodes through the directional connection lines between the target nodes. Specifically, for a first target node and a second target node in the plurality of target nodes, the terminal device may drag from the first target node to the second target node, and display a directional connection line from the first target node to the second target node in response to a drag operation from the first target node to the second target node.

Fig. 9 is a schematic diagram of determining connection relationships according to an embodiment of the present disclosure, and as shown in fig. 9, a plurality of target nodes including a start node, a condition node, two API nodes, a script node, and an end node are displayed in the editing area 52.

When the first target node and the second target node in the plurality of target nodes are connected, a cursor of the terminal equipment can be moved to the first target node, and then the cursor is clicked and dragged to the second target node, so that the directional connecting line between the first target node and the second target node is completed. The left example of fig. 9 is a plurality of target nodes that are free, and the right example is a plurality of target nodes that are connected by directional connection lines.

The target nodes are not arbitrarily connected, but certain preset rules are required to be met, and the preset rules construct constraints for the DAG. Only when the preset rule is satisfied, the directional connection line from the first target node to the second target node can be displayed in the edit area. The preset rules will be described in connection with examples.

The preset rules in the embodiment of the present disclosure mainly include the following six items:

when the first item-the first target node is the start node, the second target node is the non-end node.

The first rule indicates that the upstream of the end node cannot be the start node, i.e. that a direct connection between the start node and the end node is not possible. Since the start node is used for receiving the incoming parameters and the end node is used for summarizing the processing results of the task nodes, if the downstream of the start node is directly connected with the end node, the incoming parameters directly reach the end node, no task node processes the incoming parameters, and the service arrangement is meaningless.

When the second item-the second target node is an API node, the first target node is a non-API node.

The second rule indicates that the upstream of the API node can no longer be an API node, i.e. a direct connection between two API nodes is not possible. The API node is for data processing, and the script node is for data processing. For example, a certain API node is configured to determine the gender of the user according to the a data, where the output result of the API node after processing the a data is 1 or 2, and the gender of the user cannot be directly obtained according to 1 or 2, and at this time, the script node is required to process the data on the output result of the API node. For example, 1 is processed as "male", 2 is processed as "female", and so on.

In summary, the output result of the API node cannot be directly used, and the output result of the API node needs to be processed by the script node to output data for processing by the next API node. Thus, two API nodes cannot be directly connected.

The third item-when the first target node is a conditional node, the second target node is an unconditional node.

The third rule indicates that the upstream of the conditional node can no longer be a conditional node. The condition information of the condition node in the embodiment of the present disclosure may include a single rule expression or may include an arrangement combination of different rule expressions, so if there are multiple judgment conditions, the condition information of the multiple judgment conditions may be set in the attribute of one condition node, and two directly connected condition nodes need not be set.

The fourth item-when the last node of the first target node is an API node and the first target node is a conditional node, the second target node is a non-API node.

The fourth rule indicates that if the upstream of the API node is a conditional node, the upstream of the conditional node may not be the API node any more. The upstream of the condition node can only be a starting node, and the condition node can not process business logic and data, and if the upstream of the condition node is an API node, the data condition node output by the API node can not process and can not perform condition judgment and flow circulation.

The fifth item-if the first target node or the second target node is a condition node, the number of directional connection lines pointing to the condition node is 1.

The fifth rule indicates that there can be only one node upstream of the conditional node. If two or more nodes are arranged on the upstream of the condition node, namely, the number of directional connecting lines pointing to the condition node is greater than 1, the condition node does not know which node on the upstream should be subjected to condition judgment according to the data of which node on the upstream, and the flow of the flow cannot be carried out, so that only one node can be arranged on the upstream of the condition node.

The sixth term, the directed connection lines between each target node and each target node, forms the DAG graph.

The sixth rule indicates that the service orchestration results in a DAG graph, i.e. no self-ring is allowed to send. If it is not a DAG graph, i.e. the directed connection lines between the target nodes form a self-loop, the output of the self-loop becomes again the input of the next target node, making the service orchestration meaningless.

Optionally, in the editing area, if there is a free node, that is, the node does not generate a directional connection with any node, the free node needs to be deleted or a directional connection is performed with other nodes, so as to ensure that the whole service arrangement forms a DAG graph.

Fig. 10 is two DAG graphs provided in the embodiments of the present disclosure, as shown in fig. 10, where the left example is a DAG long-chain path graph, including a start node and a condition node, where the condition node connects API node 1 and API node 2, API node 1 connects script node 1, API node 3, and script node 3 in sequence, API node 2 connects script node 2, API node 4, and script node 3 in sequence, and script node 3 connects end node. The right example is a DAG short-link diagram, which includes a start node and a condition node, the condition node connects API node 1 and API node 2, both API node 1 and API node 2 connect script node 3, and script node 3 connects end node.

After the service is arranged, a storage control on an arrangement interface can be clicked, the terminal equipment sends a storage request to a server, and the server executes storage on the arranged DAG graph according to the storage request. Fig. 11 is a schematic diagram of a DAG graph saving and executing architecture provided in an embodiment of the present disclosure, where, as shown in fig. 11, the DAG graph saving and executing architecture includes a kong gateway, a server, and a scheduler, and functions of the kong gateway are similar to functions of the API gateway in the embodiment of fig. 3, and are not repeated herein. The server is mainly used for generating DAG orchestration service files according to the DAG graph. Capability references is a portal that can provide orchestrated data and buffering to the kong gateway. The scheduler may schedule execution of a single target node or may execute the entire DAG graph.

After receiving the save request sent by the terminal device, the server may generate a DAG orchestration service file according to the save request. Specifically, the server converts the arrangement result (i.e., the DAG graph) of the editing area into data according to the attributes of the plurality of target nodes and the connection relation between the plurality of target nodes, and stores the data into three relational database tables, wherein the three relational database tables are respectively an arrangement table, an arrangement node table and a node association table.

Table 1 is an exemplary orchestration table, as shown in Table 1, which is primarily used to record basic information of DAG orchestration services, and may include, for example, API identifications, DAG identifications, API names, and the like.

TABLE 1

API identification

DAG identification

API name

API type

API protocol

Creator person

Creation time

1

Combination test

Inside part

HTTP

Zhang San

2021-12-12

Table 2 is an exemplary orchestration node table, as shown in table 2, which is primarily used to record the content of the DAG orchestration service, and may include, for example, DAG identities, DAG attributes, DAG content, scheduling rules, scheduling times, etc., where the DAG content includes attributes of each target node in the DAG graph, etc., and the scheduling rules may, for example, indicate the time or frequency at which the DAG graph is scheduled to be executed, etc.

TABLE 2

DAG identification	DAG attributes	DAG content	Scheduling rules	Scheduling time
					1	Parallel arrangement	{“”；””,””,””,”}	0 0 0 1 1	2021-12-12

Table 3 is an exemplary node association table, as shown in table 3, which is mainly used to record the attribute and connection relationship of each target node of the DAG orchestration service. As shown in Table 3, the node type indicates the node type of each target node in the DAG graph, the node value indicates the attribute and connection relationship of each target node, and the node association table may further include a node identifier, a DAG identifier, a node name, the number of retries, a retry threshold, and the like.

TABLE 3 Table 3

Node identification	DAG identification	Node name	Node type	Node value	Number of retries	Retry threshold
							1	1	Start node	Start node	0
2	1	Conditional node	Conditional node		0
							3	1	API-1	API node	1
4	1	API-2	API node		1
							5	1	Script node	Script node	1
6	1	End node	End node		0

After the server generates the DAG orchestration service file according to the save request, the terminal device may also trigger the operation of the DAG orchestration service file. The programming interface also comprises an operation control, the operation control can be clicked, and the terminal equipment responds to touch operation aiming at the operation control and sends an operation request to the server.

After receiving the operation request, the server processes the input parameters of the starting node according to the operation request and the DAG arrangement service file because the DAG arrangement service file records the attribute and the connection relation of each target node, so that an output result of the input parameters can be obtained, and then the server returns the output result of the input parameters to the terminal equipment.

In addition to being able to run on the entire DAG graph, the target nodes of a partial DAG graph may also be debugged. Specifically, at least one target node of the plurality of target nodes may be selected, and the terminal device sends a debug request to the server in response to the selected operation for the at least one target node. After receiving the debug request, the server needs to determine whether to perform a single target recall or to perform the entire link. If the execution of the single target node is performed, the API node or the script node is directly called without using a scheduler, and if the execution of the whole link is performed, the scheduler is required to pull the connection relation of the related nodes to perform the execution.

Specifically, the attribute of the at least one target node may be obtained according to the debug request and the DAG orchestration service file, if the number of the selected target nodes is multiple, the connection relationship of the selected target node may also be obtained according to the DAG orchestration service file, and then the output result corresponding to the at least one target node is obtained according to the attribute of the at least one target node and/or the connection relationship of the at least one target node, so as to complete the debugging of the at least one target node.

The terminal device may also send a retry request to the server in response to a retry operation for a third target node, which may be any one of the plurality of target nodes. After receiving the retry request, the server may obtain a first DAG orchestration service file for the third target node according to the retry request and the DAG orchestration service file, and obtain an output result corresponding to the third target node according to the first DAG orchestration service file, thereby returning the output result to the terminal device.

Specifically, after receiving the retry request, the server first determines whether to execute the upstream or downstream of the third target node.

Fig. 12 is a schematic diagram of a retry request provided by an embodiment of the present disclosure, as shown in fig. 12, if a retry operation for a third target node (i.e., API node 1 in fig. 12) on the editing interface 120 is a first retry operation, the terminal device displays a virtual end node and a directional connection line from the third target node to the virtual end node in the editing area in response to the first retry operation, and then sends the retry request to the server according to the third target node, the virtual end node, and the directional connection line from the third target node to the virtual end node.

After receiving the retry request, the server obtains the attribute of the third target node according to the DAG orchestration service file, and then generates a first DAG orchestration service file according to the attribute of the third target node, the attribute of the virtual ending node, and the directional connection line between the third target node and the virtual ending node, where the DAG graph corresponding to the first DAG orchestration service file is illustrated by a dashed box in fig. 12. And then, according to the first DAG orchestration service file, obtaining an output result corresponding to the third target node, and returning the output result to the terminal equipment.

Fig. 13 is a schematic diagram of a retry request provided by an embodiment of the present disclosure, as shown in fig. 13, if the retry operation of the editing interface 130 with respect to the third target node (i.e., the API node 1 in fig. 13) is a second retry operation, the terminal device displays a virtual start node and a directional connection line between the virtual start node and the third target node in the editing area in response to the second retry operation, and then sends a retry request to the server according to the virtual start node, the third target node, the directional connection line between the virtual start node and the third target node, each node between the third target node and the end node, and each directional connection line.

And after receiving the retry request, the server acquires the attribute of the third target node, the attribute of each node between the third target node and the end node and each directional connecting line according to the DAG arrangement service file. And then, generating a first DAG orchestration service file according to the attribute of the virtual starting node, the attribute of the third target node, the attribute of each node between the third target node and the ending node, the directional connecting line between the virtual starting node and the third target node, each node between the third target node and the ending node and each directional connecting line. The DAG map corresponding to the first DAG orchestration service file is illustrated as a dashed box in fig. 13. And then, according to the first DAG orchestration service file, obtaining an output result corresponding to the third target node, and returning the output result to the terminal equipment.

According to the scheme of the embodiment of the disclosure, service arrangement is performed in a dragging and visual mode, serial, parallel and branch call of a plurality of services can be completed without additionally writing codes, and development cost of API services is greatly reduced. Because the calling of a plurality of data services is completed in the same resource group, the environment of each resource group is isolated, and the data is isolated, compared with the self-writing and building of workflow services, the scheme of the embodiment of the disclosure can effectively reduce the network overhead of service calling and remarkably improve the service calling performance. Furthermore, as the front-end terminal equipment and the rear-end server can be realized in a cluster mode, the service arrangement process and the calling process can be based on the native containerization of the cloud, and dynamic expansion and contraction can be realized, so that a developer does not need to pay attention to the bottom-layer operation environment, and the complexity of service arrangement is reduced.

Exemplary Medium

Having described the method of the exemplary embodiments of the present disclosure, next, a storage medium of the exemplary embodiments of the present disclosure will be described with reference to fig. 14.

Referring to fig. 14, a storage medium 140, in which a program product for implementing the above-described method according to an embodiment of the present disclosure is stored, may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device such as a personal computer. However, the program product of the present disclosure is not limited thereto.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. The readable signal medium may also be any readable medium other than a readable storage medium.

Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the context of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN).

Exemplary apparatus

Having described the medium of the exemplary embodiments of the present disclosure, the service orchestration device of the exemplary embodiments of the present disclosure is described with reference to fig. 15 and 16, so as to implement the method in any of the foregoing method embodiments, where implementation principles and technical effects are similar, and are not repeated herein.

Fig. 15 is a schematic structural diagram of a service orchestration device according to an embodiment of the present disclosure, where an orchestration interface is provided by a terminal device, where the orchestration interface includes a node type area, an edit area, and a node configuration area, and the node type area includes different types of node controls, as shown in fig. 15, and the service orchestration device 150 includes:

a display module 151 for displaying a plurality of target nodes in the editing area in response to a drag operation from the plurality of target node controls to the editing area;

a first processing module 152 configured to determine attributes of the plurality of target nodes in response to configuration operations for the plurality of target nodes in the node configuration area;

a second processing module 153 for determining a connection relationship between the plurality of target nodes in response to a drag operation between the editing area for each of the target nodes;

and the transceiver module 154 is configured to send a save request to a server in response to a touch operation for a save control on the orchestration interface, where the save request is used to instruct the server to generate a DAG orchestration service file according to the attributes of the plurality of target nodes and the connection relationship.

In one possible implementation, the first processing module 152 is specifically configured to:

for any target node, responding to touch operation for the target node, and displaying an editing control of the target node, wherein the editing control comprises a test node child control;

responding to touch operation for the test node sub-control, and displaying an attribute setting interface corresponding to the target node in the node configuration area, wherein the attribute setting interface is a sub-interface of the arrangement interface;

and determining the attribute of the target node in response to a configuration operation of the attribute setting interface.

In one possible implementation, the target node is a conditional node; the first processing module 152 is specifically configured to:

and responding to the input operation of a condition input box of the attribute setting interface, and determining the condition information of the condition node according to the input judging condition.

In one possible implementation, the target node is an API node; the first processing module 152 is specifically configured to:

and responding to the input operation of an API input box of the attribute setting interface, and determining the data processing information corresponding to the API node according to the input script.

In one possible implementation, the target node is a script node; the first processing module 152 is specifically configured to:

and responding to the input operation of a script input box of the attribute setting interface, and determining the data processing information corresponding to the script node according to the input script.

In one possible implementation, the target node is a start node; the first processing module 152 is specifically configured to:

and responding to the input operation of the entry input box of the attribute setting interface, and determining the entry of the starting node according to the input data.

In a possible implementation manner, the editing control further includes a delete sub-control, and the first processing module 152 is further configured to:

and responding to the touch operation for deleting the child control, and stopping displaying the target node in the editing area.

In one possible implementation, the second processing module 153 is specifically configured to:

for a first target node and a second target node in the plurality of target nodes, responding to a dragging operation from the first target node to the second target node, and displaying a directional connecting line from the first target node to the second target node when a preset rule is met;

And determining the connection relation between the target nodes according to the directional connection lines between the target nodes.

In a possible implementation manner, the preset rule includes at least one of the following:

when the first target node is a starting node, the second target node is a non-ending node;

when the second target node is an API node, the first target node is a non-API node;

when the first target node is a conditional node, the second target node is an unconditional node;

when the last node of the first target node is an API node and the first target node is a conditional node, the second target node is a non-API node;

if the first target node or the second target node is a condition node, the number of directional connecting lines pointing to the condition node is 1;

the directed connection lines between each of the target nodes and each of the target nodes form a DAG graph.

In a possible implementation manner, the programming interface further includes a running control, and the transceiver module 154 is further configured to:

responding to the touch operation for the operation control, and sending an operation request to a server;

and receiving an output result of the DAG orchestration service file on the entry processing of the starting node from the server.

In one possible implementation, the transceiver module 154 is further configured to:

transmitting a debug request to a server in response to a selected operation for at least one of the target nodes;

and receiving an output result corresponding to the at least one target node from the server.

transmitting a retry request to the server in response to a retry operation for a third target node of the target nodes;

and receiving an output result corresponding to the third target node from the server.

In one possible implementation, the transceiver module 154 is specifically further configured to:

in response to a first retry operation for the third target node, displaying a virtual ending node in the edit area, and a directed connection line from the third target node to the virtual ending node;

and sending the retry request to the server according to the third target node, the virtual ending node and a directional connecting line from the third target node to the virtual ending node.

Displaying a virtual start node in the edit area in response to a second retry operation for the third target node, and a directed connection line from the virtual start node to the third target node;

and sending the retry request to the server according to the virtual starting node, the third target node, the directed connecting line between the virtual starting node and the third target node, each node between the third target node and the ending node and each directed connecting line.

The service arrangement device provided in the embodiments of the present disclosure may be used to implement the technical solutions of the embodiments of the methods, and its implementation principle and technical effects are similar, and are not described herein again.

Fig. 16 is a schematic structural diagram of a service orchestration device according to an embodiment of the present disclosure, and as shown in fig. 16, the service orchestration device 160 includes:

a transceiver module 161, configured to receive a save request from a terminal device, where the save request includes attributes of a plurality of target nodes and connection relationships between the plurality of target nodes;

and the processing module 162 is configured to generate a DAG orchestration service file according to the attributes of the plurality of target nodes and the connection relationships.

In one possible implementation, the processing module 162 is specifically configured to:

generating an arrangement table, an arrangement node table and a node association table according to the attributes of the plurality of target nodes and the connection relation;

the arrangement table comprises basic information of DAG arrangement service;

the arrangement node table comprises the content of the DAG arrangement service;

the node association table comprises the attribute and the connection relation of each target node of the DAG arrangement service.

In a possible implementation manner, the transceiver module 161 is further configured to:

receiving an operation request from the terminal equipment;

obtaining an output result of the parameter entering processing according to the operation request and the parameter entering processing of the DAG arrangement service file to the starting node;

and sending the output result of the parameter entering processing to the terminal equipment.

receiving a debug request for at least one of the plurality of target nodes from the terminal device;

acquiring the attribute of the at least one target node and/or the connection relation between the at least one target node according to the debugging request and the DAG orchestration service file;

Obtaining an output result corresponding to the at least one target node according to the attribute of the at least one target node and/or the connection relation of the at least one target node;

and sending an output result corresponding to the at least one target node to the terminal equipment.

receiving a retry request from the terminal device for a third target node of the target nodes;

obtaining a first DAG orchestration service file aiming at the third target node according to the retry request and the DAG orchestration service file;

obtaining an output result corresponding to the third target node according to the first DAG arrangement service file;

and sending an output result corresponding to the third target node to the terminal equipment.

In a possible implementation manner, the retry request includes an attribute of a virtual ending node and a directional connection line between the third target node and the virtual ending node; the transceiver module 161 is specifically further configured to:

acquiring the attribute of the third target node according to the DAG arrangement service file;

and generating the first DAG orchestration service file according to the attribute of the third target node, the attribute of the virtual ending node and a directional connecting line from the third target node to the virtual ending node.

In a possible implementation manner, the retry request includes an attribute of a virtual start node and a directional connection line between the virtual start node and the third target node; the transceiver module 161 is specifically further configured to:

acquiring the attribute of the third target node, the attribute of each node between the third target node and the ending node and each directional connecting line according to the DAG orchestration service file;

and generating the first DAG orchestration service file according to the attribute of the virtual starting node, the attribute of the third target node, the attribute of each node between the third target node and the ending node, the directional connecting line between the virtual starting node and the third target node, each node between the third target node and the ending node and each directional connecting line.

Exemplary computing device

Having described the methods, media, and apparatus of exemplary embodiments of the present disclosure, a computing device of exemplary embodiments of the present disclosure is next described with reference to fig. 17.

The computing device 170 shown in fig. 17 is merely an example and should not be taken as limiting the functionality and scope of use of embodiments of the present disclosure.

As shown in fig. 17, the computing device 170 is in the form of a general purpose computing device. Components of computing device 170 may include, but are not limited to: the at least one processing unit 171, the at least one storage unit 172, and a bus 173 connecting different system components (including the processing unit 171 and the storage unit 172).

Bus 173 includes a data bus, a control bus, and an address bus.

The storage unit 172 may include readable media in the form of volatile memory, such as Random Access Memory (RAM) 1721 and/or cache memory 1722, and may further include readable media in the form of nonvolatile memory, such as Read Only Memory (ROM) 1723.

The storage unit 172 may also include a program/utility 1725 having a set (at least one) of program modules 1724, such program modules 1724 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

The computing device 170 may also communicate with one or more external devices 174 (e.g., keyboard, pointing device, etc.). Such communication may occur through an input/output (I/O) interface 175. Moreover, the computing device 170 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 176. As shown in fig. 17, the network adapter 176 communicates with other modules of the computing device 170 over the bus 173. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with computing device 170, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

It should be noted that although in the above detailed description several units/modules or sub-units/modules of a service orchestration device are mentioned, such a division is only exemplary and not mandatory. Indeed, the features and functionality of two or more units/modules described above may be embodied in one unit/module in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit/module described above may be further divided into ones that are embodied by a plurality of units/modules.

Furthermore, although the operations of the methods of the present disclosure are depicted in the drawings in a particular order, this is not required to or suggested that these operations must be performed in this particular order or that all of the illustrated operations must be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.

While the spirit and principles of the present disclosure have been described with reference to several particular embodiments, it is to be understood that this disclosure is not limited to the particular embodiments disclosed nor does it imply that features in these aspects are not to be combined to benefit from this division, which is done for convenience of description only. The disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A service orchestration method, providing an orchestration interface through a terminal device, wherein the orchestration interface comprises a node type area, an editing area and a node configuration area, the node type area comprises node controls of different types, and the method comprises:

determining the connection relation between the target nodes according to the directional connection lines between the target nodes;

the preset rule comprises at least one of the following:

the directed connection lines between each target node and each target node form a DAG graph;

responding to touch operation of a storage control on the arrangement interface, and sending a storage request to a server, wherein the storage request is used for indicating the server to generate a directed acyclic graph DAG arrangement service file according to the attribute of the plurality of target nodes and the connection relation;

the method further comprises the steps of:

receiving an output result corresponding to the third target node from the server;

in response to a retry operation for a third target node of the target nodes, sending a retry request to the server, comprising:

2. The method of claim 1, determining attributes of the plurality of target nodes in response to configuration operations for the plurality of target nodes at the node configuration area, comprising:

3. The method of claim 2, the target node being a conditional node; determining the attribute of the target node in response to a configuration operation of the attribute setting interface, including:

4. The method of claim 2, the target node being an application programming interface, API, node; determining the attribute of the target node in response to a configuration operation of the attribute setting interface, including:

5. The method of claim 2, the target node being a script node; determining the attribute of the target node in response to a configuration operation of the attribute setting interface, including:

6. The method of claim 2, the target node being a start node; determining the attribute of the target node in response to a configuration operation of the attribute setting interface, including:

7. The method of any of claims 2-6, further comprising a delete child control in the edit control, the method further comprising:

8. The method of any of claims 2-6, further comprising running controls on the orchestration interface, the method further comprising:

9. The method of any one of claims 2-6, further comprising:

10. The method of claim 1, responsive to a retry operation for a third target node of the target nodes, sending a retry request to a server, comprising:

11. A service orchestration method, comprising:

receiving a storage request sent by a terminal device in response to touch operation for a storage control on an arrangement interface from the terminal device, wherein the arrangement interface is provided by the terminal device and comprises a node type area, an editing area and a node configuration area, and the node type area comprises node controls of different types;

the storage request comprises attributes of a plurality of target nodes and connection relations among the plurality of target nodes; the attribute of the plurality of target nodes is determined by the terminal equipment in response to drag operation from a plurality of target node controls to the editing area, the plurality of target nodes are displayed in the editing area, and in response to configuration operation of the plurality of target nodes in the node configuration area; the connection relation is determined by the terminal equipment aiming at a first target node and a second target node in the plurality of target nodes, responding to dragging operation from the first target node to the second target node, and displaying a directional connection line from the first target node to the second target node when a preset rule is met according to the directional connection line between the target nodes;

Wherein the preset rule comprises at least one of the following:

generating DAG arranging service files according to the attributes of the target nodes and the connection relation;

the method further comprises the steps of:

Sending an output result corresponding to the third target node to the terminal equipment;

the retry request comprises the attribute of a virtual ending node and a directional connecting line between the third target node and the virtual ending node; obtaining a first DAG orchestration service file for the third target node according to the retry request and the DAG orchestration service file, including:

12. The method of claim 11, generating a DAG orchestration service file from attributes of the plurality of target nodes and the connection relationship, comprising:

the arrangement table comprises basic information of DAG arrangement service;

13. The method of claim 11 or 12, the method further comprising:

receiving an operation request from the terminal equipment;

14. The method of claim 11 or 12, the method further comprising:

15. The method of claim 11, the retry request including an attribute of a virtual start node and a directional connection line between the virtual start node to the third target node; obtaining a first DAG orchestration service file for the third target node according to the retry request and the DAG orchestration service file, including:

16. A service orchestration apparatus that provides an orchestration interface through a terminal device, the orchestration interface including a node type area, an edit area, and a node configuration area, the node type area including different types of node controls, the apparatus comprising:

The second processing module is used for responding to the dragging operation from the first target node to the second target node aiming at the first target node and the second target node in the plurality of target nodes, and displaying a directional connecting line from the first target node to the second target node when a preset rule is met; determining the connection relation between the target nodes according to the directional connection lines between the target nodes;

the preset rule comprises at least one of the following:

The receiving and transmitting module is used for responding to the touch operation of the storage control on the arrangement interface and sending a storage request to a server, wherein the storage request is used for indicating the server to generate a DAG arrangement service file according to the attribute of the plurality of target nodes and the connection relation;

the transceiver module is further configured to:

the transceiver module is specifically further configured to:

17. The apparatus of claim 16, the first processing module being specifically configured to:

18. The apparatus of claim 17, the target node being a conditional node; the first processing module is specifically configured to:

19. The apparatus of claim 17, the target node being an API node; the first processing module is specifically configured to:

20. The apparatus of claim 17, the target node being a script node; the first processing module is specifically configured to:

21. The apparatus of claim 17, the target node being a start node; the first processing module is specifically configured to:

22. The apparatus of any of claims 17-21, the edit control further comprising a delete sub-control, the first processing module further configured to:

23. The apparatus of any of claims 17-21, further comprising a run control on the orchestration interface, the transceiver module further to:

24. The apparatus of any of claims 17-21, the transceiver module further to:

25. The apparatus of claim 16, the transceiver module being further specifically configured to:

26. A service orchestration device, comprising:

the system comprises a receiving and transmitting module, a storage module and a storage module, wherein the receiving and transmitting module is used for receiving a storage request sent by a terminal device in response to touch operation for a storage control on an arrangement interface, the arrangement interface is provided by the terminal device, the arrangement interface comprises a node type area, an editing area and a node configuration area, and the node type area comprises node controls of different types;

Wherein the preset rule comprises at least one of the following:

the processing module is used for generating a DAG arrangement service file according to the attributes of the plurality of target nodes and the connection relation;

the transceiver module is further configured to:

the retry request comprises the attribute of a virtual ending node and a directional connecting line between the third target node and the virtual ending node; the transceiver module is specifically further configured to:

27. The apparatus of claim 26, the processing module being specifically configured to:

the arrangement table comprises basic information of DAG arrangement service;

28. The apparatus of claim 26 or 27, the transceiver module further to:

receiving an operation request from the terminal equipment;

29. The apparatus of claim 26 or 27, the transceiver module further to:

30. The apparatus of claim 26, the retry request including an attribute of a virtual start node and a directional connection line between the virtual start node to the third target node; the transceiver module is specifically further configured to:

31. A computing device, comprising: at least one processor and memory;

the memory stores computer-executable instructions;

the at least one processor executing computer-executable instructions stored in the memory cause the at least one processor to perform the service orchestration method according to any one of claims 1-10, or cause the at least one processor to perform the service orchestration method according to any one of claims 11-15.

32. A computer readable storage medium having stored therein computer executable instructions which, when executed by a processor, implement the service orchestration method according to any one of claims 1-10, or the service orchestration method according to any one of claims 11-15.