CN114518908A

CN114518908A - Service arranging method, medium, device and computing equipment

Info

Publication number: CN114518908A
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: 2022-05-20
Anticipated expiration: 2042-02-17
Also published as: CN114518908B

Abstract

The embodiment of the disclosure provides a service arranging method, medium, device and computing equipment. Providing an arrangement interface through terminal equipment, wherein the arrangement interface comprises a node type area, an editing area and a node configuration area, and the node type area comprises different types of node controls, and the method comprises the following steps: displaying a plurality of target nodes in the editing area in response to the dragging operation from the plurality of target node controls to the editing area; determining attributes of the plurality of target nodes in response to a configuration operation for the plurality of target nodes in the node configuration area; in response to the dragging operation between the target nodes in the editing area, determining the connection relation among the target nodes; and responding to touch operation aiming at the saving control on the arrangement interface, sending a saving request to the server, wherein the saving request is used for indicating the server to generate a DAG arrangement service file according to the attributes and the connection relation of the target nodes. The complexity of the service orchestration process is reduced.

Description

Service arranging method, medium, device and computing equipment

Technical Field

Embodiments of the present disclosure relate to the field of computer technologies, and in particular, 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 that are 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 the platform construction in the unified data, the details of the storage and calculation of the bottom layer data do not need 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 usually involved to invoke a plurality of data services to realize a large data service, and in this case, service arrangement needs to be performed on various data services. The service arrangement refers to a process of developing each data service, expanding corresponding functional services according to the requirements of business functions, binding with an API interface, and providing services externally in the form of API.

The current data arrangement service mainly edits codes at the background according to the requirements of business functions to combine various data services to realize corresponding services, and the process of realizing service arrangement by the scheme is complex.

Disclosure of Invention

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

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

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

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

in response to the dragging operation between the editing area and each target node, determining the connection relation among the target nodes;

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

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

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

and generating a DAG arrangement service file according to the attributes of the target nodes and the connection relation.

In a third aspect of the disclosed embodiments, there is provided a service orchestration apparatus, where an orchestration interface is provided by a terminal device, where the orchestration interface includes a node type region, an editing region, and a node configuration region, and the node type region includes different types of node controls, 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 target nodes in the editing area;

a first processing module for determining attributes of the plurality of target nodes in response to a configuration operation for the plurality of target nodes at the node configuration area;

the second processing module is used for responding to the dragging operation between the editing area and each target node and determining the connection relation among the target nodes;

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

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

the system comprises a receiving and sending module, a sending and receiving module and a sending and receiving module, wherein the receiving and sending module is used for receiving a storage request from a terminal device, and the storage request comprises attributes of a plurality of target nodes and connection relations among the target nodes;

and the processing module is used for generating a DAG arrangement service file 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 a memory;

the memory stores computer-executable instructions;

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

In a sixth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored therein computer-executable instructions that, 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 a service orchestration method according to any one of the first aspect or implements a service orchestration method according to any one of the second aspect.

The service arranging method, the service arranging medium, the service arranging device and the service arranging computing equipment provided by the embodiment of the disclosure provide an arranging interface through terminal equipment, wherein the arranging interface comprises a node type area, an editing area and a node configuration area, the node type area comprises different types of node controls, firstly, in response to the dragging operation from a plurality of target node controls to the editing area, a plurality of target nodes are displayed in the editing area, then, in response to the configuration operation aiming at the plurality of target nodes in the node configuration area, the attributes of the plurality of target nodes are determined, and in response to the dragging operation aiming at each target node in the editing area, the connection relation among the plurality of target nodes is determined; after determining the attributes and the connection relations of the target nodes, responding to touch operation of a saving control on the arrangement interface, and sending a saving request to the server, so that the server generates a DAG arrangement service file according to the attributes and the connection relations of the target nodes. The scheme of the embodiment of the disclosure provides a service arrangement platform, corresponding interface operations are executed on an arrangement interface of the service arrangement platform, then a storage request is sent to a server through a storage control to generate a DAG arrangement service file, service arrangement can be realized, data service combination is not required to be carried out through background editing codes, the connection relation between target nodes and attribute configuration of the target nodes are determined through dragging operation to realize data service combination, and the service arrangement process is simple.

Drawings

The above and other objects, features and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description 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 and in which:

FIG. 1 is a first schematic diagram of a service arrangement;

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

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

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

FIG. 5 is a schematic diagram of an organization interface provided by an embodiment 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 node configuration diagram provided in the embodiments of the present disclosure;

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

fig. 9 is a schematic diagram of determining a connection relationship according to an embodiment of the disclosure;

FIG. 10 is two DAG graphs provided by embodiments of the present disclosure;

fig. 11 is a schematic diagram of a DAG graph saving and executing architecture provided by the embodiment of the present disclosure;

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

fig. 13 is a diagram illustrating a retry request according to an embodiment of the disclosure;

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

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

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

fig. 17 is a schematic structural diagram of a computing device according to 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 with reference to a number of exemplary embodiments. It is understood that these embodiments are given solely for the purpose of enabling those skilled in the art to better understand and to 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.

As will be appreciated by one skilled in the art, embodiments of the present disclosure may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to the embodiment of the disclosure, a service arranging method, a medium, a device and a computing device are provided. In this document, it is to be understood that any number of elements in the figures are provided by way of illustration and not limitation, and any nomenclature is used for differentiation only and not in any limiting sense.

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

API: application Programming Interface, Application Programming Interface.

A DAG: directed Acyclic Graph, in Graph theory, if a Directed Graph starts from any vertex and cannot go back to the point through several edges, the Graph is a Directed Acyclic Graph.

Service orchestration: the service orchestration is the ability to develop services by means of simple drag-and-drop process orchestration and parameter configuration, and supports the re-composition orchestration of developed services. The user can rapidly develop the service in the form of graphical arrangement in the service arrangement editor, expand richer business functions, and bind with the API interface to provide the service externally in the form of API.

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

Summary of The Invention

The data service is used as the uppermost layer of the unified data middle platform construction, can shield the details of bottom data storage and calculation, simplifies and enhances the use of data, provides data warehouse data to a data user in a servitization and interfacing mode, avoids chimney type construction, enhances the development and delivery efficiency of a data API, and improves the data utilization rate.

When providing data services externally, it is usually necessary to perform service arrangement on a plurality of data services according to business functions to implement development of the data services, and bind the developed data services with the API interface, thereby providing the data services in the form of the API interface.

The following describes implementation of two service arrangements in the related art with reference to fig. 1 and fig. 2.

Fig. 1 is a schematic diagram of a service arrangement. Referring to fig. 1, the service arrangement 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 data processing, the conversion node is used for branch condition judgment, and each service node constitutes a complete workflow through a scheduling engine. When the data service is called, the scheduling engine executes each service node in sequence according to the setting, transmits the parameters output by the service nodes, and automatically manages the state conversion of each service node.

Fig. 2 is a schematic diagram of a service arrangement. Referring to fig. 2, an example service orchestration is performed by the gateway, which processes and transforms the data. When a request arrives at the gateway, the gateway calls a plurality of backend services (such as the services provided by the service nodes like API service node-1, API service node-2, API service node-3, etc. illustrated in fig. 2), performs processing operations (including filtering, moving, renaming, packaging, unpacking, etc.) on the return data of each service on the gateway, and finally integrates the data and returns the data to the front end.

The inventor finds that, in the service arrangement scheme illustrated in fig. 1, each service node is scheduled by the scheduling engine, and after a complete workflow is formed, the scheduling engine can only execute the service nodes in sequence downwards, which is a serial arrangement scheme, and a certain service node cannot perform retry and exception checking, and is difficult to accurately locate a problem when an exception occurs in a data service. Meanwhile, the conversion node in the service orchestration scheme illustrated in fig. 1 can only perform a simpler judgment of the branch condition, and cannot meet a more complicated condition judgment requirement. The service arrangement scheme illustrated in fig. 2 is implemented by a gateway, logical operations among API service nodes are all handled by the gateway, the dependency on the gateway is relatively strong, and the service arrangement scheme belongs to a service aggregation operation with high coupling, and the availability and flexibility of service arrangement are relatively low. Further, the service arrangement schemes illustrated in fig. 1 and fig. 2 also need to edit codes in the background according to business functions to implement combination of data services, 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 described in detail below.

Application scene overview

An application scenario in which the embodiments of the present disclosure are applicable is first described with reference to fig. 3.

Fig. 3 is a schematic view of an application scenario provided by the embodiment of the present disclosure, and as shown in fig. 3, the application scenario includes 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 constructing a DAG graph and performing a drag-and-drop configuration on service orchestration.

Between the terminal device 31 and the server 32, a nginx cluster and an API gateway cluster may also be included, where the nginx cluster may be regarded as a part of a front end, and is mainly used to perform operations such as receiving a request, distributing a request, and responding to a request; the API gateway cluster is mainly used for executing some permission verification operations, taking an e-commerce platform as an example, if a data service is used for searching order information and the input parameter of the data service is an order number, the API gateway cluster needs to verify a currently logged-in user account number, password and the like after the order number and the search request reach the API gateway cluster, and sends the search request to a server for processing after the request is met.

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 firstly, and if the cache service does not have the information, the information is further searched from the data source and cached into the cache service. The information which is historically inquired is cached through the cache service, and the response speed of the inquired information can be improved. The time sequence database is mainly used for storing some historical operation or historical information time and is arranged according to the 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 different services, and the services provided by each resource group are not arranged for service. The API deployment service performs service deployment, and finally provides an API interface to outside from the resource group a, and the data service can call services of other resource groups according to the service deployment, 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

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

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

And S41, responding to the dragging operation from the target node controls to the editing area, and displaying a plurality of target nodes in the editing area.

The main execution body of the embodiment of the disclosure is a terminal device, the terminal device may be, for example, a mobile phone, a computer, a tablet, or the like, and an arrangement interface for arranging services is displayed on the terminal device.

Fig. 5 is a schematic diagram of a layout interface according to an embodiment of the present disclosure, as shown in fig. 5, the layout interface 50 includes a node type area 51, an editing area 52, and a node configuration area 53. The 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 the like. In fig. 5, API node control 511 and conditional node control 512 located in node type area 51 are illustrated.

Since the service arrangement is composed of a plurality of service nodes, a plurality of target nodes can be set as the service nodes according to the requirements of service functions. Specifically, a drag operation from the plurality of target node controls to the editing area 52 may be performed so 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 the API node control 511 is clicked and dragged to the editing region 52, and then the editing region 52 displays an API node, where the API node is one of the target nodes.

For any target node, the dragging operation from the target node control to the editing area 52 may be executed according to the target node control corresponding to the target node, so that the corresponding target node is displayed in the editing area.

And S42, responding to the configuration operation of the plurality of target nodes in the node configuration area, and determining the attributes of the plurality of target nodes.

Different types of target nodes have different attributes, e.g., attributes of the start node include entries and attributes of the API node include data processing information. If a plurality of target nodes include two condition nodes, the two condition nodes may include different determination conditions, and the different determination 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 can be configured in the node configuration area 53 by different types of target nodes may be different, for example, for a start node, only an entry parameter needs to be input 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 the determination result, and so on.

And S43, responding to the dragging operation between the editing area and each target node, and determining the connection relation among a plurality of target nodes.

After the target node controls are dragged to the editing area, a plurality of target nodes are displayed in the editing area, and the target nodes are in a scattered state, so that dragging operation between the target nodes needs to be executed in the editing area 52 to determine the connection relationship between the target nodes, and each target node is connected into a whole.

It should be noted that the execution among S41, S42, and S43 does not limit a strict order of sequence, and for a plurality of target nodes, S41 may be executed first, and after the plurality of target nodes are all displayed in the editing area 52, configuration operation is performed on each target node in sequence to determine the attribute of each target node, and after the attribute configuration is completed, S43 is executed to determine the connection relationship; or after a certain target node is displayed in the editing area, the configuration operation of the target node is executed first, and then the next target node is displayed in the editing area 52 by the dragging operation; it is also possible to perform a configuration operation of another target node after a certain target node is displayed in the edit area 52, and so on.

That is, the dragging operation of the target node control to the editing area 52, the configuration operation of the target node, and the dragging operation between the target nodes may be performed alternately 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 the target node targeted by the dragging operation is displayed in the editing area 52 when the dragging operation between the target nodes is performed.

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

Steps S41-S43 executed on the terminal device are all front-end execution steps, after the service arrangement is completed, the storage control on the arrangement interface 50 may be clicked, the terminal device sends a storage request to the server in response to a touch operation for the storage control, the storage request includes attributes and connection relationships of a plurality of target nodes, where the attributes of the plurality of nodes are attributes configured for each target node through a configuration operation in S42, and the connection relationships between the plurality of target nodes are connection relationships determined according to a dragging operation between the target nodes in S43.

After receiving the storage request, the server may acquire attributes of the plurality of target nodes and a connection relationship between the plurality of target nodes, and then generate a DAG orchestration service file according to the attributes of the plurality of target nodes and the connection relationship between the plurality of target nodes, where the DAG orchestration service file may be used to provide data services to the outside. For example, after the input parameter is input, the input parameter is processed according to the attribute of the target node recorded in the DAG layout service file, and then the parameter output by the target node is transferred to the next target node according to the connection relation between the target nodes until the processing result of the input parameter is finally output.

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

After determining the connection relations between the attributes of the target nodes and the target nodes, the terminal device 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 target nodes and the connection relations between the target nodes.

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

The DAG orchestration service file is used for recording an orchestration result of the terminal device, and may include basic information of service orchestration, and also include recorded attributes of the target nodes and connection relationships between the plurality of target nodes. The DAG arrangement service file can provide data service for the outside, after the access parameter is input, the DAG arrangement service file can process the access parameter according to the recorded attributes of the target nodes and the connection relation between the target nodes, and finally, the processing result of the DAG arrangement service file on the access parameter is output.

The DAG orchestration service file represents that a plurality of target nodes and connection relations between the target nodes form a DAG graph, fig. 6 is a DAG diagram provided by the embodiment of the present disclosure, as shown in fig. 6, a transition is made from a start node to a condition node, then to an API node 1 and/or an API node 2, then the API node 1 and/or the API node 2 is made to a script node 3, and finally to an end node, the DAG graph is formed between the target nodes, and after the DAG graph illustrated in fig. 6 is saved in a click, the server may be triggered to generate the DAG orchestration service file according to attributes and connection relations of the target nodes. If the target node in the example of fig. 6 is changed from the start node to the condition node, then to the API node 1 and/or API node 2, then the API node 1 and/or API node 2 is changed to the script node 3, and then the script node 3 is changed to the start node, a DAG graph is not formed, so that the DAG graph is not satisfactory, and the DAG orchestration service file cannot be generated according to the attributes and connection relationships of the target node.

The service arranging method provided by the embodiment of the disclosure provides an arranging interface through terminal equipment, wherein the arranging interface comprises a node type area, an editing area and a node configuration area, the node type area comprises different types of node controls, firstly, a plurality of target nodes are displayed in the editing area in response to dragging operation from the plurality of target node controls to the editing area, then, the attributes of the plurality of target nodes are determined in response to the configuration operation 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 the dragging operation between the editing area and each target node; after the attributes and the connection relations of the target nodes are determined, responding to touch operation of a storage control on the arrangement interface, and sending a storage request to a server, so that the server generates a DAG arrangement service file according to the attributes and the connection relations of the target nodes. The scheme of the embodiment of the disclosure provides a service arrangement platform, corresponding interface operations are executed on an arrangement interface of the service arrangement platform, then a storage request is sent to a server through a storage control to generate a DAG arrangement service file, service arrangement can be realized, data service combination is not required to be carried out through background editing codes, the connection relation between target nodes and attribute configuration of the target nodes are determined through dragging operation to realize data service combination, and the service arrangement process is simple.

On the basis of any one of the above embodiments, the service orchestration process is described in detail in conjunction with the following embodiments.

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

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

The attribute of the target node can be configured on the attribute setting interface, and after the configuration is completed, the terminal device responds to the configuration operation aiming at the attribute setting interface to determine the attribute of the target node. The target nodes mainly comprise 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. Different types of target nodes may include the same attribute configuration item, such as a node name, and each target node may also include different attribute configuration items. Different attribute configuration items will be introduced for different types of nodes.

The starting node is a node existing in a DAG graph arranged for each service, and only receives the access participation without executing business logic, so that the attribute configuration of the starting node mainly comprises the configuration of the access participation. Specifically, the attribute setting interface of the start node may include a parameter input box, a corresponding parameter may be input in the parameter input box, and the terminal device determines the parameter of the start node according to the input data in response to the input operation in the parameter input box.

Like the property setting interface 74 for the start node illustrated in fig. 7, the entry input box may also further include at least one of a parameter name, a parameter type, an input value, a default value, may also add or delete certain property configuration items as needed, and so on. Taking the example of the e-commerce platform inquiring the order information, the entry parameter at this time can be the order number, and then the order number is input in the entry parameter input box according to the order to be inquired, the parameter name can be the order number, for example, the parameter type can be an integer, and the like.

The API node is used for processing data, 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 into the API input box, and the terminal device 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 used 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 device 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 the circulation condition judgment, is associated with an edge of the connected target node, and is used for judging whether a downstream target node needs to be executed. The terminal device 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 judgment condition. The input judgment condition may be a regular expression, or may be a scripting language such as Python, groovy, or the like, and if the judgment condition is the scripting language, an open-source executor may need to be introduced for the execution of the script.

The end node is also a node existing in the DAG graph organized for each service, the end node is used for summarizing the processing result of the task node and outputting the processing result, and the attribute configuration item of the end node may include summary information, for example. And the attribute setting interface of the end node can comprise a summary information input box, summary information can be input into the summary information input box, and the summary information is used for indicating how to summarize the processing results of the task nodes so as to output the results.

In the above embodiment, the process of adding the target node and configuring the attribute of the target node by the dragging operation from the target node control to the editing area is described, and when there are redundant target nodes in the editing area, the target node may also be deleted.

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

And 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 for the deletion sub-control. As shown in fig. 8, when the delete child control 80 is clicked, the start node 71 is deleted and is not displayed in the edit area.

Having described the process of attribute configuration of the target nodes in the above embodiment, 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 device determines the connection relationship between the target nodes through the directional connection line between the target nodes. Specifically, for a first target node and a second target node in the plurality of target nodes, the first target node may be dragged to the second target node from the first target node, and the terminal device displays a directional connection line from the first target node to the second target node in response to a dragging operation from the first target node to the second target node.

Fig. 9 is a schematic diagram for determining a connection relationship 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 an editing area 52.

When a first target node and a second target node in the plurality of target nodes are connected, a cursor of the terminal device can be moved to the first target node, and then the cursor is clicked and dragged to the second target node, so that the directed connection line between the first target node and the second target node is completed. Fig. 9 illustrates a plurality of target nodes as free nodes on the left side, and illustrates a plurality of target nodes as connected by directional connection lines on the right side.

The target nodes may not be connected arbitrarily, but need to satisfy certain preset rules, which construct constraints for the DAG. Only if a preset rule is satisfied can the directional connecting line from the first target node to the second target node be displayed in the editing area. The preset rule will be described with reference to an example.

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

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

The first rule indicates that upstream of the end node cannot be the start node, i.e. there is no direct connection between the start node and the end node. Since the start node is used for receiving the incoming participation 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 participation directly reaches the end node, and no task node processes the incoming participation, so that the service arrangement is meaningless.

And when the second item is the API node, the first target node is a non-API node.

The second rule indicates that the API node is no longer upstream, i.e., there is no direct connection between two API nodes. The API node is used for data processing, and the script node is used for data processing. For example, a certain API node is used for determining the gender of the user according to the data a, the output result of the API node after processing the data a 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 output result of the API node. For example, 1 is processed to "male", 2 to "female", etc.

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.

And when the third item is that the first target node is a conditional node, the second target node is an unconditional node.

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

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 condition node, the upstream of the condition node is no longer an API node. The upstream of the condition node can only be a starting node, because the condition node can not process the service logic, the data can not be processed, if the upstream of the condition node is an API node, the data condition node output by the API node can not be processed, and the condition judgment and the flow circulation can not be carried out.

Fifth item-if the first target node or the second target node is a conditional node, the number of directed connection lines pointing to the conditional node is 1.

The fifth rule indicates that there can be only one node upstream of the conditional node. If two or more nodes exist at the upstream of the conditional node, that is, the number of the directional connecting lines pointing to the conditional node is greater than 1, the conditional node does not know which node at the upstream should perform the conditional judgment according to the data of the node at the upstream, and the flow cannot be circulated, so that only one node exists at the upstream of the conditional node.

The sixth item-each target node and the directed connecting lines between target nodes constitute a DAG graph.

The sixth rule indicates that the service orchestration results in a DAG graph, i.e., no self-loops are allowed to be sent. If the node is not a DAG graph, namely directed connecting lines between target nodes form a self-loop, the output result of the self-loop becomes the input of the next target node, so that the service arrangement is meaningless.

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

Fig. 10 is two DAG graphs provided by the embodiment of the present disclosure, as shown in fig. 10, a DAG long-chain path graph is illustrated on the left, where the DAG long-chain path graph includes a start node and a condition node, the condition node is connected to an API node 1 and an API node 2, the API node 1 is connected to a script node 1, an API node 3, and a script node 3 in sequence, the API node 2 is connected to a script node 2, an API node 4, and a script node 3 in sequence, and the script node 3 is connected to an end node. The example on the right is a DAG short-link graph which comprises a starting node and a condition node, wherein the condition node is connected with an API node 1 and an API node 2, the API node 1 and the API node 2 are both connected with a script node 3, and the script node 3 is connected with an ending node.

After the service arrangement is completed, a saving control on the arrangement interface can be clicked, the terminal equipment sends a saving request to the server, and the server saves the arranged DAG graph according to the saving request. Fig. 11 is a schematic view of a DAG graph saving and executing architecture provided in the embodiment of the present disclosure, and 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 those of the API gateway in the embodiment of fig. 3, and are not described here again. The server is mainly used for generating the DAG arrangement service file according to the DAG graph. Capability reference is an entry that can provide the kong gateway with choreographed data and buffers. The scheduler may schedule execution of a single target node or may execute the entire DAG graph.

After receiving the storage request sent by the terminal device, the server may generate a DAG orchestration service file according to the storage request. Specifically, the server converts the layout result (i.e., DAG) of the editing region into data and stores the data into three relational database tables according to the attributes of the target nodes and the connection relationships between the target nodes, where the three relational database tables are a layout table, a layout node table, and a node association table.

Table 1 is an exemplary layout table, and as shown in table 1, the layout table is mainly used for recording basic information of a DAG layout service, which may include, for example, an API identifier, a DAG identifier, an API name, and the like.

TABLE 1

API identification

DAG identification

API names

API type

API protocol

Creators

Creation time

1

Combination testing

Inner part

HTTP

Zhang San

2021-12-12

Table 2 is an exemplary orchestration node table, and as shown in table 2, the orchestration node table is mainly used for recording contents of a DAG orchestration service, and may include, for example, a DAG identifier, DAG attributes, DAG contents, a scheduling rule, a scheduling time, and the like, where the DAG contents include attributes of each target node in a DAG graph, and the scheduling rule may indicate, for example, a time or a frequency at which the DAG graph is scheduled to be executed, and the like.

TABLE 2

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

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

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 storage request, the terminal device may also trigger the operation of the DAG orchestration service file. The arrangement interface further comprises a running control which can be clicked, and the terminal equipment responds to touch operation aiming at the running control and sends a running request to the server.

After the server receives the operation request, because the DAG orchestration service file records the attributes and the connection relation of each target node, the server processes the input of the start node according to the operation request and the DAG orchestration service file to obtain an output result of input processing, and then the server returns the output result of input processing to the terminal device.

In addition to being run against the entire DAG graph, debugging may also be performed against target nodes of a partial DAG graph. Specifically, at least one target node of the plurality of target nodes may be selected, and the terminal device sends a debugging request to the server in response to the selected operation for the at least one target node. The server, upon receiving the debug request, needs to decide whether to execute a single target recall or execute the entire link. If a single target node is executed, the API node or the script node can be directly called without using a scheduler, and if the whole link is executed, the connection relation of the related nodes is pulled by the scheduler to be executed.

Specifically, the attribute of the at least one target node may be obtained according to the debugging request and the DAG orchestration service file, if there are a plurality of selected target nodes, the connection relationship of the selected target nodes may also be obtained according to the DAG orchestration service file, and then an 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 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 arrange the service files according to the retry request and the DAG to obtain a first DAG arranged service file for the third target node, and obtain an output result corresponding to the third target node according to the first DAG arranged service file, so as to return the output result to the terminal device.

Specifically, after receiving the retry request, the server 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 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 acquires 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 end node, and a directed connection line from the third target node to the virtual end node, where a DAG graph corresponding to the first DAG orchestration service file is as an example of a dashed-line frame in fig. 12. And then arranging the service file according to the first DAG to obtain an output result corresponding to the third target node and returning the output result to the terminal equipment.

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

And after receiving the retry request, the server acquires the attribute of the third target node, the attribute of each node from the third target node to the end node and each directed connecting line according to the DAG arrangement service file. And then, generating a first DAG arrangement service file according to the attribute of the virtual start node, the attribute of the third target node, the attribute of each node between the third target node and the end node, the directional connecting 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 connecting line. The DAG graph corresponding to the first DAG orchestration service file is illustrated as a dashed box in fig. 13. And then arranging the service file according to the first DAG to obtain 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 application program interface, the services are arranged in a dragging and visual mode, serial, parallel and branch calling of a plurality of services can be completed without writing codes additionally, and the development cost of the API services is greatly reduced. Because the calling of a plurality of data services is completed in the same resource group, each resource group is environment-isolated and data-isolated, and compared with self-compiling and building 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, because the front-end terminal device and the rear-end server can be realized in a cluster mode, the service arranging process and the calling process can be based on cloud-native containerization, dynamic expansion and contraction can be realized, developers do not need to pay attention to the bottom operating environment, and the complexity of service arranging is also reduced.

Exemplary Medium

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

Referring to fig. 14, a storage medium 140 stores therein a program product for implementing the above method according to an embodiment of the present disclosure, which 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. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. 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 thereof. 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 computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, 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 devices

After introducing the media of the exemplary embodiment of the present disclosure, next, a service orchestration device of the exemplary embodiment of the present disclosure is described with reference to fig. 15 and fig. 16 for implementing the method in any of the above method embodiments, which is similar in implementation principle and technical effect and is not described herein again.

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 region, an editing region, and a node configuration region, and the node type region includes different types of node controls, as shown in fig. 15, the service orchestration device 150 includes:

a display module 151, configured to display a plurality of target nodes in the editing region in response to a dragging operation from a plurality of target node controls to the editing region;

a first processing module 152 for determining attributes of the plurality of target nodes in response to a configuration operation for the plurality of target nodes in the node configuration area;

a second processing module 153, configured to determine, in response to a dragging operation between the editing area and each of the target nodes, a connection relationship between the plurality of target nodes;

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

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

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

responding to the touch operation aiming at 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 the configuration operation of the attribute setting interface.

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

and in response to the input operation in a condition input box of the attribute setting interface, determining the condition information of the condition node according to the input judgment condition.

In one possible embodiment, 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 embodiment, 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 embodiment, the target node is a start node; the first processing module 152 is specifically configured to:

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

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

and responding to the touch operation aiming at the deletion sub-control, and stopping displaying the target node in the editing area.

In a possible implementation manner, 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 directed 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 directed connection line between the target nodes.

In a possible embodiment, the preset rules comprise at least one of:

when the first target node is a start node, the second target node is a non-end 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 condition node, the second target node is a non-API node;

if the first target node or the second target node is a conditional node, the number of the directed connection lines pointing to the conditional node is 1;

and each target node and the directed connecting lines between the target nodes form a DAG graph.

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

responding to the touch operation aiming at the running control, and sending a running request to a server;

and receiving an output result of the participation process of the DAG orchestration service file to the start node from the server.

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

responding to the selected operation aiming at least one target node in the target nodes, and sending a debugging request to a server;

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

sending a retry request to a server in response to a retry operation for a third one of the target nodes;

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

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

and sending the retry request to the server according to the third target node, the virtual end node and a directed connection line from the third target node to the virtual end node.

In response to a second retry operation for the third target node, displaying a virtual start node and a directional connection line from the virtual start node to the third target node in the edit region;

and sending the retry request to the server according to the virtual start node, the third target node, the directional connection line from the virtual start node to the third target node, each node from the third target node to the end node, and each directional connection line.

The service orchestration device provided in the embodiment of the present disclosure may be used to implement the technical solution of the method embodiment, and the implementation principle and the technical effect are similar, which 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 saving request from a terminal device, where the saving request includes attributes of multiple target nodes and connection relationships between the multiple 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 relationship.

In a 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 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;

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

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

receiving an operation request from the terminal device;

according to the operation request and the DAG arrangement service file, performing parameter input processing on a starting node to obtain an output result of the parameter input processing;

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

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

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 one of the target nodes;

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

arranging a service file according to the first DAG to obtain an output result corresponding to the third target node;

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 end node and a directional connection line between the third target node and the virtual end node; the transceiver module 161 is further specifically configured to:

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

and generating the first DAG orchestration service file according to the attribute of the third target node, the attribute of the virtual end node and a directed connection line from the third target node to the virtual end node.

In one possible implementation, 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 further specifically configured to:

acquiring the attribute of the third target node, the attribute of each node between the third target node and the end node and each directed connecting line according to the DAG arranging service file;

and generating the first DAG orchestration service file according to the attributes of the virtual start node, the attributes of the third target node, the attributes of each node between the third target node and the end node, the directional connection lines 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.

The service orchestration device provided in the embodiments of the present disclosure may be used to implement the technical solution of the above method embodiments, and its implementation principle and technical effect are similar, which are not described herein again.

Exemplary computing device

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

The computing device 170 shown in fig. 17 is only one example and should not place any limitation on the scope of use and functionality of embodiments of the present disclosure.

As shown in fig. 17, 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 memory unit 172, and a bus 173 that couples various system components (including the processing unit 171 and the memory unit 172).

The 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 non-volatile memory, such as Read Only Memory (ROM) 1723.

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 of which, or some combination thereof, may comprise 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 via an input/output (I/O) interface 175. Also, the computing device 170 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) through the network adapter 176. As shown in FIG. 17, the network adapter 176 communicates with the other modules of the computing device 170 via the bus 173. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the computing device 170, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

It should be noted that although in the above detailed description several units/modules or sub-units/modules of the service orchestration device are mentioned, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the 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 embodiments by a plurality of units/modules.

Further, while the operations of the disclosed methods are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

While the spirit and principles of the present disclosure have been described with reference to several particular embodiments, it is to be understood that the present disclosure is not limited to the particular embodiments disclosed, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. 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 arranging method provides an arranging interface through terminal equipment, the arranging interface comprises a node type area, an editing area and a node configuration area, the node type area comprises different types of node controls, and the method comprises the following steps:

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

determining attributes of the plurality of target nodes in response to a configuration operation for the plurality of target nodes at the node configuration area;

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 region, comprising:

Aiming at any target node, responding to touch operation aiming at the target node, and displaying an editing control of the target node, wherein the editing control comprises a test node sub-control;

responding to touch operation aiming at 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;

3. The method according to claim 1 or 2, wherein determining the connection relation among the plurality of target nodes in response to the dragging operation among the editing area for each target node comprises:

4. The method of claim 3, the preset rules comprising at least one of:

5. A service orchestration method, comprising:

6. The method of claim 5, generating a DAG orchestration service file according to the attributes of the plurality of target nodes and the connection relationships, comprising:

the arrangement table comprises basic information of DAG arrangement service;

7. A service arranging device provides an arranging interface through terminal equipment, the arranging interface comprises a node type area, an editing area and a node configuration area, the node type area comprises different types of node controls, and the device comprises:

And the receiving and sending module is used for responding to the touch operation aiming at 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 attributes of the target nodes and the connection relation.

8. A service orchestration device comprising:

the system comprises a receiving and sending module, a sending and receiving module and a sending and receiving module, wherein the receiving and sending module is used for receiving a storage request from a terminal device, and the storage request comprises the attributes of a plurality of target nodes and the connection relation among the target nodes;

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

the memory stores computer execution instructions;

the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the service orchestration method according to any one of claims 1-4, or causes the at least one processor to perform the service orchestration method according to any one of claims 5-6.

10. A computer readable storage medium having stored thereon computer executable instructions which, when executed by a processor, implement a service orchestration method according to any one of claims 1-4 or implement a service orchestration method according to any one of claims 5-6.