CN114816375A - Service orchestration method, apparatus, device and storage medium - Google Patents

Abstract

The application relates to the technical field of computers and discloses a service arranging method, a device, equipment and a storage medium, wherein the method comprises the following steps: displaying a main interface, wherein the main interface comprises N nodes, and N is a positive integer; when configuration operation for a target node exists, displaying a configuration interface of the target node, wherein the configuration interface of the target node is used for acquiring configuration information of the target node, the configured target node corresponds to a service, and the target node is any one of N nodes; when there is a connection operation for the N nodes, a node chain including the N nodes is displayed, and the node chain is used to generate a service orchestration file including an execution order of one or more services. By the method, the development efficiency of the developer on the service arrangement can be improved.

Description

Service orchestration method, apparatus, device and storage medium

technical field

The present application relates to the field of computer technologies, and in particular, to a service orchestration method, apparatus, device, and storage medium.

Background technique

With the rapid development of digital transformation, traditional monolithic services can no longer meet the technical requirements of current interconnected products. Therefore, service orchestration emerges as the times require. Service orchestration is to weave various services in an orderly manner to complete a certain business, aggregate each service into a specific execution chain, and users can call one or more backend microservices through a single call request.

At present, most of the implementation methods of service orchestration are written by code. Therefore, for developers, the development cycle is long and the efficiency is low. Therefore, how to efficiently realize the development of service orchestration has become a technical problem that needs to be solved urgently.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a service orchestration method, apparatus, device, and storage medium, which can improve the development efficiency of service orchestration by developers.

In one aspect of the implementation of the present application, a service orchestration method is disclosed, and the method includes:

Displaying a main interface, the main interface includes N nodes, and N is a positive integer;

When there is a configuration operation for the target node, the configuration interface of the target node is displayed. The configuration interface of the target node is used to obtain the configuration information of the target node. The configured target node corresponds to a service, and the target node is the target node. any node in the N nodes;

When there is a connection operation for the N nodes, a node chain including the N nodes is displayed, and the node chain is used to generate a service orchestration file containing the execution order of one or more services.

An aspect of the implementation of the present application discloses a service orchestration device, the device comprising:

a display unit for displaying a main interface, the main interface includes N nodes, and N is a positive integer;

The display unit is further configured to display a configuration interface of the target node when there is a configuration operation for the target node, where the configuration interface of the target node is used to obtain configuration information of the target node, and the configured target node Corresponding to a service, the target node is any node in the N nodes;

The display unit is further configured to display a node chain including the N nodes when there is a connection operation for the N nodes, the node chain is used to generate a service arrangement file, and the service arrangement file includes a or the order of execution of multiple services.

In one aspect of the implementation of the present application, a service orchestration device is disclosed, and the device includes:

a processor adapted to implement one or more instructions; and a computer storage medium having stored one or more instructions adapted to be loaded by the processor and execute the above Service Orchestration Method.

An aspect of an embodiment of the present application discloses a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program includes program instructions that, when executed by a processor, cause the processor to Execute the service orchestration method described above.

In one aspect, embodiments of the present application disclose a computer product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the service orchestration device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the service orchestration device executes the above-mentioned service orchestration method.

In this embodiment of the present application, a main interface is displayed, and the main interface includes N nodes, where N is a positive integer; when there is a configuration operation for the target node, the configuration interface of the target node is displayed, and the configuration interface of the target node is used to obtain the information of the target node. Configuration information, the configured target node corresponds to a service, and the target node is any node among N nodes; when there is a connection operation for N nodes, the node chain containing N nodes is displayed, and the node chain is used to generate services An orchestration file that contains the execution order for one or more services. Developers can place nodes in the form of drag and drop on the visual interface, and configure node information to obtain service orchestration files, which do not require developers to develop in the form of code, and the learning cost is low, which can reduce the workload of developers. It can save development time, thereby improving developers' development efficiency for service orchestration.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1 is a schematic diagram of the architecture of a service orchestration system disclosed in an embodiment of the present application;

FIG. 2 is a schematic flowchart of a service orchestration method disclosed in an embodiment of the present application;

3 is a schematic diagram of a main interface of a service orchestration method disclosed in an embodiment of the present application;

4 is a schematic diagram of a configuration interface disclosed in an embodiment of the present application;

FIG. 5 is a schematic diagram of a service orchestration connection mode disclosed in an embodiment of the present application;

6 is a schematic flowchart of another service orchestration method disclosed in an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a service orchestration apparatus disclosed in an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a service orchestration device disclosed in an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

Before explaining the service orchestration method provided by this application, first introduce the technical terms related to this application:

1. Domain Specific Language (DSL): A programming language with limited expressiveness designed for a specific domain. By limiting the problem boundary, so as to lock the complexity and improve the programming efficiency, using DSL as the declarative configuration of service orchestration has the following advantages: First, it can reduce the error rate of language expression; Able to understand the model; 3. The domain-specific language provides a domain-specific Application Programming Interface (API) to operate the model, which can improve development efficiency; 4. The model has important business knowledge, and the solution is transformed from a technology Migrating to another technology, or between versions of the same technology, makes it relatively easy. This can usually be done by modifying the generator or interpreter appropriately. 5. You can use the model to configure an implementation process that includes a variety of different technologies, thereby reducing the technical difficulty and workload of implementing a solution using these technologies. In the embodiment of the present application, the DSL mainly uses a yaml format file to describe the service orchestration file. Optionally, a file in a format such as json and hcl can also be used to describe the service orchestration file. Among them, yaml, json, and hcl are all markup languages.

2. Lowcode: A method of visual application development through which developers of different experience levels can create web and mobile applications through a graphical user interface, using drag-and-drop components and model-driven logic. Using the lowcode method to carry the orchestration configuration of this solution has the following advantages: 1. Building applications more intuitively, you can use a visual method to define user logic, and smooth out the experience of different developers in developing the API layer. Second, developers can use their own coding enhancements to expand the application, and when they need to customize the code, they can encapsulate the relevant code into a shared module, so that the entire development team can drag it into their application. 3. Built-in automatic testing, active quality monitoring and real-time performance management, reduce project development risks. Fourth, make full use of the public cloud, and automatically manage the reliability and scalability of applications through simple configuration, thereby reducing the maintenance cost and workload of the infrastructure. 5. Fully embody the concept of devops (the collective term for processes, methods and systems), automatically build the system after completing the configuration, and build the test and verification branches during deployment. In the application embodiment, the service orchestration file is constructed on the graphical interface by dragging and dropping, and developers are not required to write code line by line to construct the service orchestration file, thereby realizing the development efficiency of front-end developers.

3. Service orchestration: Use various capabilities to orchestrate to complete a certain business, and each capability is woven in an orderly manner and aggregated into a specific execution chain. A single call will cause one or more requests to the backend service.

4. Node.js: A JavaScript runtime environment based on the Chrome V8 engine. Node.js uses an event-driven, non-blocking I/O model that is ideal for I/O-intensive applications. In the application example, Node.js mainly completes the following tasks: 1. Writing the core functions of the service orchestrator of the Node.js version, providing micro-service aggregation capabilities and orchestration capabilities, so that client requests can obtain multiple Back-end microservice data, and the ability to use strongly customized orchestration logic to orchestrate the call sequence of microservices. 2. Provide a DSL parsing engine, which parses the DSL description and makes chained calls to the back-end microservices according to certain logic. 3. Write a code generator, which can use a template engine to generate deployable service code using abstract syntax trees, support secondary development, and further improve development efficiency. Optionally, languages such as Golang (a static strongly typed compiled language), Java, PHP, and Python can also be used.

With reference to the above related introduction, please refer to FIG. 1 , which is a schematic diagram of the architecture of a service orchestration system disclosed in an embodiment of the present application. As shown in FIG. 1 , the architecture diagram 100 of the service orchestration system includes a user terminal 110 , a service orchestration system The device 120 and the server 130, wherein the service orchestration device 120 includes a service orchestration front end 121 and a service orchestration server 122, and the user terminal 110, the service orchestration device 120 and the server 130 can be connected by communication. Specifically, the user terminal 110 is mainly used to send a service invocation request to the service orchestration device 120, or directly to the server 130; Invoke various services stored in the server 130, and then return the execution result to the user terminal 110; compared with the user terminal 110 directly sending the service invocation request to the server 130, the service orchestration device in the architecture shown in this application realizes the service When the user terminal 110 initiates a service invocation request including multiple services, the service orchestration device 120 can implement the invocation of the service. Effectively reduce the network transmission cost consumed by the user terminal calling the service multiple times. The server 130 is mainly used to store services with various functions, and the services also include various microservices.

Based on the service orchestration system, the present application provides a service orchestration method, specifically:

In a possible implementation manner, the service orchestration method is mainly performed by the service orchestration front end 121: displaying a main interface, the main interface includes N nodes, where N is a positive integer; when there is a configuration operation for the target node, displaying the target node's Configuration interface, the configuration interface of the target node is used to obtain the configuration information of the target node, the configured target node corresponds to a service, and the target node is any node among N nodes; when there is a connection operation for N nodes, Displays a node chain containing N nodes, the node chain is used to generate a service orchestration file that contains the execution order of one or more services. This method mainly configures the information corresponding to the nodes in the service orchestration front-end 121, so as to efficiently realize the service orchestration, and does not require developers to develop in the form of code, which can save development time, reduce workload, and better adapt to the Development concept in the cloud era.

In a possible implementation manner, the service orchestration method is mainly executed by the service orchestration server 122: parsing the service orchestration file completed by the service orchestration front end 121 to obtain an executable code file, the executable code file includes one or more corresponding to the service orchestration file. The execution sequence of multiple services, and the configuration information of each service; the executable code file is deployed, and the deployed executable code file is used to respond to the service invocation request of the user terminal; the service invocation request is obtained, and the service invocation request includes the service The file identifier of the orchestration file; the executable code file corresponding to the execution service orchestration file is called according to the execution order of one or more services contained in the service orchestration file and the configuration information of each service, and the execution result of the service invocation request is obtained. ; Return the execution result of the service invocation request to the user terminal corresponding to the service invocation request. The executable code corresponding to the service orchestration file is directly executed by the service orchestration server 122, without repeating the steps of calling and returning according to each service, and finally returning the execution result of the call request, which can effectively reduce the number of calls by the user terminal and reduce the number of calls. The network transfer cost of the interface.

In a possible implementation manner, the user terminal 110 includes, but is not limited to, a handheld device with a wireless communication function, a vehicle-mounted device, a wearable device, or a computing device. Exemplarily, the user terminal 110 may be a mobile phone, a tablet computer or a computer with a wireless transceiving function. It can also be virtual reality (VR) terminal equipment, augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in unmanned driving, wireless terminal equipment in telemedicine, Wireless terminal equipment in a smart grid, wireless terminal equipment in a smart city, wireless terminal equipment in a smart home, and so on. The service orchestration server 122 and the server 130 may be independent physical servers, or may be server clusters or distributed systems composed of multiple physical servers, or may provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network Cloud servers for basic cloud computing services such as services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

Based on the above service orchestration system, the present application provides a service orchestration method, as shown in FIG. The service orchestration front end 121 executes, and the service orchestration method may specifically include the following steps:

S201. Display a main interface, where the main interface includes N nodes, where N is a positive integer.

Among them, the main interface is the visual boundary of the node corresponding to the configuration service orchestration file. The main interface can refer to a method of visual application development, such as the lowcode (low code) development interface. Through this interface, developers of different experience levels can Create web and mobile applications using drag-and-drop components and model-driven logic through a graphical user interface. In the embodiment of the present application, the main interface is an interface used to implement service orchestration by dragging and dropping. Developers can select different types of nodes according to their needs and place them in the main interface, which can reduce the learning cost and learning burden of developers.

In a possible implementation manner, when service orchestration needs to be performed, the developer clicks on the main interface on the front end of the service orchestration, thereby displaying the main interface. The main interface includes adding controls. The developer can add nodes by adding controls. The developer can select the node type of each node. After the developer adds, the displayed main interface will include the user click to add. node. Among them, the node type is divided according to the function of the corresponding service of the node. For example, the function of the service can be database (such as adding, deleting, modifying and other functions), redis, and even various application services (such as WeChat), and the node type can also be based on Nodes are divided by the transport protocol of the corresponding service. Specifically, a service can be a popular microservice. Taking an online supermarket as an example, an online supermarket can have multiple services, such as user management, commodity management, and order management. Each management corresponds to a microservice, which can also be understood as a A function corresponds to a microservice.

For example, the main interface may be as shown in FIG. 3 , which is a schematic diagram of the main interface of a service orchestration method disclosed in the embodiment of the present application. There is an “add” control 301 on the interface, and the developer clicks the “add” control 301 to display the interface 302, the developer can input the node type in the interface 302 according to the service they want to select. When the node type is determined, a node similar to node 1 will be obtained. It can be seen that, as shown in Figure 3 In the main interface, three nodes are displayed, namely N=3. Optionally, the main interface also includes a "view" control. After the information of each node is configured, the developer can click the "view" control to view the configuration information of each node. Optionally, the main interface further includes a "debug" control, and when the developer clicks the "debug" control, a corresponding execution result will be obtained.

S202. When there is a configuration operation for the target node, display the configuration interface of the target node, where the configuration interface of the target node is used to obtain the configuration information of the target node, the configured target node corresponds to a service, and the target node is one of the N nodes. of any node.

Among them, there are nodes dragged by developers in the main interface, and each node corresponds to a node type. It is possible that several nodes have the same node type, or different nodes may correspond to different node types. The service that needs to be called is related. If the calling service is implemented based on the rpc protocol, the corresponding node type may be the rpc type, where the rpc is a remote procedure call (Remote Procedure Call).

In a possible implementation manner, when there is a configuration operation for the target node, the service orchestration device will obtain the pre-configuration file corresponding to the node type of the target node, and then display the configuration interface of the target node on the main interface, corresponding to The configuration interface of the target node includes multiple file contents of the pre-configured file. When there is a selection operation for the target file content, the target file content is used as the configuration information of the target node, and the target file content file is also a plurality of pre-configured files. in the file content. Optionally, the configuration interface of the target node can be displayed anywhere on the main interface. The target node is any one of the N nodes, for example, it may be any one of the three nodes shown in FIG. 3 ; the configuration operation may specifically be that the developer clicks on the target node. Among them, the pre-configuration file is related to the node type. For example, for a node of the trpc protocol type, the corresponding pre-configuration file is "North Star Configuration" (the name is customized and used to distinguish different configurations), ilive protocol The corresponding preconfiguration file for the type node is "l5 configuration".

For example, as shown in FIG. 4 , it is a schematic diagram of a configuration interface of a target node disclosed in an embodiment of the application, and a configuration interface 401 of the target node is located on the right side of the main interface.

In a possible implementation manner, the multiple file contents of the pre-configuration file include service identifiers of multiple services, method identifiers of multiple methods included in each service, and multiple method parameters of each method, wherein one service There may be multiple methods, and the method parameters corresponding to each method are different. When there is a configuration operation for the target node, the configuration interface of the target node (specifically how to configure the target node) is displayed, including: when there is a configuration operation for the target node When there is a selection operation for the service identifier of the target service, a list of method identifiers of multiple methods included in the target service is displayed; when there is a selection operation for the method identifier of the target method, multiple method parameter lists of the target method are displayed; when there are parameters for the target method During the selection operation, the service identifier of the target service, the method identifier of the target method, and the parameters of the target method are all used as the configuration information of the target node, and the target node here corresponds to the target service. Among them, each service corresponds to a service ID, and a service ID can correspond to a service name. Similarly, each method corresponds to a method ID, and each method ID can also correspond to a method name.

For example, as shown in FIG. 4 , which is a schematic diagram of a configuration interface of a target node disclosed in the embodiment of the application, wherein 401 is the configuration interface of node 1, and the interface includes the settings for the service pb file (the pb file represents the model structure The binary file (without source code), service routing settings, and namespace settings, where the service routing can be obtained by parsing the service pb file, and the namespace corresponds to the node type. Developers can dynamically configure the namespace to make a selection. In Figure 4, the configuration interface also includes service name settings, method name settings, and method parameter settings. Since the service name, method name, and method parameters have dependencies, developers have a sequence in the configuration. The service name , method names and method parameters are displayed to the developer in the form of a drop-down box for selection. The displayed service name, method name and method parameters are obtained according to the pre-configured file corresponding to the node type. When the service name of the target service is selected, the drop-down box of the method name contains the method name of the method contained in the target service, that is, when the service name of the target service is selected, the method name contained in the drop-down box of the method name is the same as the selected one. The method name associated with the service name; when the target method is selected, the drop-down box of method parameters contains the method parameters included in the target method, that is, the method parameters included in the drop-down box of method parameters are the parameters associated with the selected method name.

S203. When there is a connection operation for N nodes, display a node chain including N nodes, where the node chain is used to generate a service arrangement file, where the service arrangement file includes the execution sequence of one or more services.

In a possible implementation manner, through steps S201 to S202, N nodes that have been configured can be obtained, and when there is a connection operation for N nodes, a node chain containing N nodes is displayed, that is, the development of Personnel connect these N nodes through connecting lines to obtain a connected node chain. The node chain can be a directed acyclic graph. Specifically: it can be a single node or multiple nodes, and multiple nodes can be slave nodes. a flows to node b, and then from node b to node c; it can also flow from node a to node b, from node b to node c, and at the same time, node b also flows to node d.

Specifically, as shown in FIG. 5 , which is a schematic diagram of a service orchestration connection method disclosed in an embodiment of the present application, it can be seen that 501 in FIG. 2 is a connection method of a node chain, and 502 is another kind of node How the chain is connected.

In a possible implementation, after the developer has connected the configured N nodes, and clicks the debug control on the main interface, a corresponding service orchestration file will be generated, and the generated service orchestration file is marked Language files, such as the aforementioned yaml format files, json format files, and hcl format files. At the same time, the test results of the node chain (that is, the service orchestration file) will be displayed on the interface. The service arrangement file also includes configuration information of each service, and the configuration information of each service is determined by the configuration information of the node corresponding to each service; the test results include the first unit test result and the second unit test result, and the first unit test result and the second unit test result. The first unit test result is the test result about the execution order of one or more services included in the service orchestration file generated by the node chain, and the second unit test result is the test result about the service execution result of the service orchestration file. Specifically, the first unit test result is used to detect whether the execution order of multiple services in the service orchestration file is the same as the preset execution order. Developers need to adjust the order, which can be modified directly in the main interface by dragging and dropping. The second unit test result is used to detect whether the service execution result of the service orchestration is the same as the preset one. If it is the same, it proves that the service orchestration is successful. On the contrary, if an error occurs, the developer needs to match the service orchestration files node to adjust. Optionally, the test result further includes a third unit test result, and the third unit test result is the business execution result of each node corresponding to the service orchestration file. It can be detected whether the service configured by each node can be successfully executed. If the execution is successful, the front-end developer will change the configuration information of the node.

To sum up, the work of the service orchestration front-end 121 can be summarized as: the first step, developers drag and drop the number of nodes they need on the visual interface (such as the aforementioned lowcode development interface), and configure each node according to the pre-configured file. The configuration that each node should have (configured in the configuration interface shown in Figure 4), the configuration information includes service name, method name and method parameters; the second step, the developer arranges each node in a certain order on the visual interface , for example, the first node is the configured node A, the second node is the configured node C, and the last node is the configured node B. After connecting the three nodes, click Save to get a workflow (corresponding to the aforementioned node chain) and a corresponding workflow id (service orchestration file identifier), the id can be used to call the parameters when executing the workflow interface; the third step: in the debugging interface provided by the platform, use the obtained workflow id, The service orchestration file can be obtained to obtain aggregated data and test results.

In a possible implementation, the service orchestration file corresponding to the node chain generated in the main interface can be used to directly implement the invocation of the service orchestration file. For the service orchestration file, there is a corresponding trigger action, and the trigger action can be received The service invocation request initiated by the user terminal directly returns the execution result of the service orchestration file to the user, and the triggering action can also be triggered by the developer, and the execution result of the service orchestration file can also be obtained. This situation corresponds to a platform as a service (Platform as a Service, PaaS), which means. It can be understood that the user only needs to call the platform that develops the service orchestration to get the execution result of the service invocation request.

In the implementation of this application, the main interface is displayed, the main interface includes N nodes, and N is a positive integer; when there is a configuration operation for the target node, the configuration interface of the target node is displayed, and the configuration interface of the target node is used to obtain the target node's configuration interface. Configuration information, the configured target node corresponds to a service, and the target node is any node among N nodes; when there is a connection operation for N nodes, the node chain containing N nodes is displayed, and the node chain is used to generate services An orchestration file that contains the execution order for one or more services. This method is mainly that developers can efficiently implement service orchestration by dragging and dropping nodes in the visual interface of the service orchestration front-end 121 and configuring the rows of node information, which does not require developers to develop in the form of code, which can save development time. , reduce the workload, and better conform to the development concept of the cloud era.

Based on the above-mentioned service orchestration system and service orchestration method, the present application provides another service orchestration method, as shown in FIG. Executed by the service orchestration server 122 in the orchestration setting 120, the service orchestration method may specifically include the following steps:

S601. Parse the service orchestration file to generate an executable code file, where the executable code file includes an execution sequence of one or more services corresponding to the service orchestration file, and configuration information of each service.

In a possible implementation manner, after each node corresponding to the service orchestration file is configured in the service orchestration front-end 121, the corresponding service orchestration file is generated. In the embodiment of the present application, the generated service orchestration file is described by a DSL (Domain Specific Language, domain specific language), and may specifically be a file in a yaml format, or a file in a format such as json or hcl. Further, the service orchestration front end 121 sends the service orchestration file to the service orchestration server 122 .

Further, the registered node interface included in the service orchestration server receives the service orchestration file and the configuration information of each node sent by the service orchestration front end, the execution sequence of one or more services included in the received service orchestration file, and the learned node information included in the service orchestration server. The interface parses the service orchestration file to generate an executable code file and encapsulates the executable code file as a workflow interface. The executable code file includes the execution sequence of one or more services corresponding to the service orchestration file, and configuration information of each service. Among them, the executable code files generated by parsing can be divided into two types, one of which is called an executable code file with runtime, and the other is called an executable code file without runtime.

The generating process of the executable code file with runtime is as follows: the parser directly and automatically generates the executable code file according to the service orchestration file. The executable code file with runtime can ensure the consistency of the obtained executable code file and the service arrangement file, so as to reduce the error rate.

The generation process of the executable code file without runtime is as follows: the parser automatically generates the auxiliary executable code file according to the service arrangement file, and the developer manually edits the auxiliary executable code file to obtain the executable code file without runtime. Executable code files without runtime are more autonomous for developers, who can customize and write according to their needs.

Optionally, the service orchestration server can also convert the service orchestration file into any executable code file suitable for the development platform, such as Node and Golang languages. These two languages can better suit the language usage habits and language usage of front-end developers. performance, but also compiled languages such as Java, PHP, Python, etc.

S602. Deploy an executable code file, where the deployed executable code file is used to respond to a service invocation request of a user terminal.

In a possible implementation manner, the service orchestration server may also deploy the executable code file obtained by parsing, the purpose of which is to respond to the service invocation request initiated by the user terminal. Each deployed executable code file and service orchestration file have a corresponding relationship, which can be distinguished by an identifier. For example, a service orchestration file corresponds to an id, and each id corresponds to an executable code file. Specifically, as shown in Table 1, the file identifier of the service orchestration file and the executable code file have the same identification information, so that the service orchestration server can better manage the service orchestration file.

Table I

File ID for the service orchestration file Executable code file identification id=1 File 1 ... ... id=1 file N

Optionally, the executable code file can be deployed by a developer, and can also be deployed by a user terminal if the user understands the logic of service orchestration. It is not limited here. The obtained executable code can be deployed to various cloud deployment platforms, such as Tencent Cloud containers, cloud services, cloud functions, etc., as well as deployment platforms within each enterprise.

S603. Obtain a service invocation request, where the service invocation request includes a file identifier of the service arrangement file.

In a possible implementation manner, after the user terminal initiates a service invocation request, correspondingly, the service orchestration server can obtain the service invocation request, so as to quickly realize the service invocation by the service orchestration server, and return to the user terminal. Results of the. The service invocation request includes the file identifier of the service arrangement file, such as the identifier information shown in Table 1, for example, id=1.

In a possible implementation manner, after the service orchestration server receives the service invocation request, it also involves the conversion of the network transmission protocol, which can be specifically explained as: first, the service orchestration server receives the original invocation request sent by the user terminal, the original The invocation request is a request generated based on the first transmission protocol, and the service orchestration server can parse the invocation request of the second transmission protocol. Therefore, when the original invocation request is sent to the service orchestration server, the first transmission protocol and the second transmission protocol Whether the transmission protocol is consistent, if it is consistent, the call request corresponding to the service call request can be directly executed. If it is inconsistent, the service orchestration server will first convert the original call request into the service call request corresponding to the second transmission protocol, and then execute the corresponding service call request. The service call request is processed.

For example, the original invocation request sent by the user terminal is a request generated based on the first transmission protocol. For example, the first transmission protocol is Hypertext Transfer Protocol (Hypertext Transfer Protocol, HTTP), and the service orchestration server can parse the second transmission protocol. For the call request, if the second transmission protocol is the TRPC protocol, then the HTTP protocol needs to be converted into the TRPC protocol. When the service orchestration server returns the execution result to the user terminal, it also needs to convert the TRPC protocol into the HTTP protocol, so that the user terminal can Receive the execution result. Among them, the TRPC protocol is generated based on the RPC protocol.

S604. Execute the executable code file corresponding to the service orchestration file, and sequentially call the services according to the execution sequence of one or more services contained in the service orchestration file and the configuration information of each service, to obtain the execution result of the service invocation request.

In a possible implementation manner, after the service orchestration server obtains the service invocation request and the file identifier of the service orchestration file carried in the service invocation request, the execution workflow interface included in the service orchestration server can orchestrate the file according to the service orchestration file. Identifies invoking the encapsulated workflow interface, and executes the executable code file encapsulated by the workflow interface. Specifically, the execution workflow interface invokes the services in sequence according to the execution order of one or more services contained in the service orchestration file and the configuration information of each service, that is, executes the executable code file corresponding to the service orchestration file, and obtains the service invocation request. Results of the. The aggregation of services is realized by calling the workflow interface, which can effectively reduce the network transmission cost of the user terminal calling different interfaces multiple times.

S605. Return the execution result of the service invocation request to the user terminal corresponding to the service invocation request.

In a possible implementation manner, after obtaining the execution result of the service invocation request, the service orchestration server will return the execution result to the user terminal to meet the user's invocation requirement for the service.

In a possible implementation manner, the execution result of the service invocation request may be returned to the user terminal through the foregoing execution interface.

Optionally, the service orchestration server also provides a custom plug-in mechanism to support developers' custom expansion logic. Front-end developers can write custom logic for plug-in rules and insert them into the service orchestration server to expand the orchestration capability. Specifically, the service orchestration server can use the Plugin (Plug-in, addin, add-in, addon or add-on) plug-in mechanism, through dependency injection and life cycle hooks, so that front-end developers can write custom logic very easily, The plug-in mechanism can be understood as another plug-in interface. For example, a developer customizes a code with a "log" or "monitoring" function, and the execution time is defined in the code, and the code is encapsulated into an plug-in interface, and the work is called. When the flow interface executes the executable code encapsulated by the workflow interface, the custom code inserted into the interface encapsulation can be executed in parallel, so as to realize the invocation of the service and the recording of the execution log in the process.

In a possible implementation, developers can also pull other types of nodes in the main interface, such as web hook nodes, graphql nodes, merge nodes, etc., developers can configure these nodes to achieve different from service orchestration function, that is, each of the above nodes will not correspond to a service. Among them, the web hook node is an API concept, which is one of the usage paradigms of microservice API, also known as reverse API, that is, the front end does not actively send requests, but is completely pushed by the back end; the graphql node is the declarative data used for the API To obtain the specification and query language, the user can query the execution result by calling this node; the common understanding of the merge node is a synthesis node. In the process of aggregating data, a synthesis node is needed to realize the aggregation.

According to the above embodiment, in a possible implementation method, on the basis of implementing the service orchestration method of the present application, different functions can also be implemented by calling interfaces corresponding to different nodes, for example, by calling interfaces corresponding to web hook nodes Implement continuous integration (Continuous Integration, CI)/continuous deployment (Continuous Deployment, CD)). The "CI" in CI/CD belongs to the automated process of developers. Successful CI means that new changes to application code are regularly built, tested, and merged into a shared repository. The "CD" in CI/CD refers to continuous delivery and/or continuous deployment. For another example, the MOCK test can be implemented through the JSON node, in which JSON (JavaScript ObjectNotation, JS) is a lightweight data exchange format, that is, the data passed through JSON, to simulate the implementation of the MOCK test, and the Mock test is in the testing process. For some complex objects that are not easy to construct (such as HttpServletRequest must be constructed in the servlet container) or difficult to obtain (such as the ResultSet object in JDBC), a virtual object (Mock object) is used to create a The test method of the test; for another example, the low-code configuration activity page can also be implemented through the activity configuration node, that is, an activity configuration node is configured, and a visual interface (ie, the low-code configuration activity page) can be obtained by calling the activity configuration node.

In this embodiment of the present application, the service orchestration server parses the service orchestration file to obtain an executable code file, where the executable code file includes the execution sequence of one or more services corresponding to the service orchestration file, and the configuration information of each service; Executable code file, the deployed executable code file is used to respond to the service invocation request of the user terminal; obtain the service invocation request, the service invocation request includes the file identifier of the service arrangement file; execute the executable code file corresponding to the service arrangement file, According to the execution sequence of one or more services contained in the service orchestration file and the configuration information of each service, the services are called in sequence to obtain the execution result of the service invocation request; the execution result of the service invocation request is returned to the user terminal corresponding to the service invocation request . The executable code corresponding to the service orchestration file is directly executed by the service orchestration server. It is not necessary to repeat the call and return steps according to each service, and finally return the execution result of the call request, which can effectively reduce the number of calls by the user terminal and the call interface. network transmission costs.

According to the embodiments illustrated in FIG. 2 and FIG. 6 , it can be known that the service orchestration method provided by the present application can smoothly migrate the existing services by relying on DSL on the visual interface without affecting the existing services (that is, in the The service orchestration file is constructed in the form of drag and drop on the visual interface), so that the back-end developers can focus on the management and development of services, and conform to the development concept in the cloud era; the service orchestration method of this application is to construct the service orchestration file by dragging and dropping. , there is no need for developers to develop in the form of code, thus reducing the learning cost and mental burden of users, improving the development efficiency of developers, reducing engineering manpower input in product development, and providing the possibility for subsequent platform productization The service orchestration method of the present application can debug the service orchestration file on the visual interface, and does not need to test at the API gateway layer in turn. Therefore, the workload is greatly reduced, it is easier to test, and data security is also easier to be guaranteed. ; The service orchestration method of the present application can realize service aggregation by encapsulating executable codes, and the user terminal only needs to call one interface to obtain the execution result of the call request when calling multiple services, which can effectively reduce the number of calls by the client to the interface. network transmission costs.

Based on the above service orchestration system and service orchestration method, an embodiment of the present application discloses a service orchestration apparatus, as shown in FIG. The server orchestration device 70 may run the following units:

A display unit 701, configured to display a main interface, where the main interface includes N nodes, where N is a positive integer;

The display unit 701 is further configured to display a configuration interface of the target node when there is a configuration operation for the target node, where the configuration interface of the target node is used to obtain configuration information of the target node, and the configured target The node corresponds to a service, and the target node is any node in the N nodes;

The display unit 701 is further configured to display a node chain including the N nodes when there is a connection operation for the N nodes, the node chain is used to generate a service orchestration file, and the service orchestration file includes: The execution order of one or more services.

In a possible implementation manner, each node corresponds to a node type, and the node type is divided according to the function of the service corresponding to the node; when there is a configuration operation for the target node, the display unit displays the configuration interface of the target node ,include:

A transceiver unit 702, configured to acquire a pre-configuration file corresponding to the node type of the target node when there is a configuration operation for the target node;

The display unit 701 is further configured to display a configuration interface of the target node according to the pre-configuration file, where the configuration interface of the target node includes multiple file contents of the pre-configuration file;

The determining unit 703 is configured to use the target file content as the configuration information of the target node when there is a selection operation on the target file content among the plurality of file contents.

In a possible implementation manner, the multiple file contents of the pre-configuration file include service identifiers of multiple services, method identifiers of multiple methods included in each service, and multiple method parameters of each method; the When there is a selection operation for the target file content in the multiple file contents, the target file content is used as the configuration information of the target node, including:

A display unit 701, configured to display the method identifiers of multiple methods included in the target service when there is a selection operation for the service identifier of the target service in the service identifiers of the multiple services;

The display unit 701 is further configured to display a plurality of method parameters included in the target method when there is a selection operation for the method identifier of the target method included in the target service;

The determining unit 703 is further configured to, when there is a selection operation for the target method parameter among the multiple method parameters included in the target method, the service identifier of the target service, the method identifier of the target method, and the selected target method. The target method parameters are used as configuration information of the target node, and the target node corresponds to the target service.

In a possible implementation manner, the service orchestration file is a markup language file; the processing unit 704 is configured to:

According to the node chain of the N nodes and the configuration information of each node, a service orchestration file is generated, and the service orchestration file also includes the configuration information of each service, and the configuration information of each service is corresponding to each service. The configuration information of the node is determined;

Parsing the service orchestration file to obtain an executable code file, where the executable code file includes the execution sequence of one or more services corresponding to the service orchestration file, and configuration information of each service;

The executable code file is deployed, and the deployed executable code file is used to respond to a service invocation request of the user terminal.

In a possible implementation manner, the processing unit 704 is configured to test the service orchestration file when the debugging control is selected to obtain a test result, where the test result includes the first unit test result and A second unit test result, the first unit test result is a test result about the execution order of one or more services included in the service orchestration file, and the second unit test result is a business about the service orchestration file Execute the result of the test result.

In a possible implementation manner, the transceiver unit 702 is further configured to obtain a service invocation request, where the service invocation request includes a file identifier of the service orchestration file;

The processing unit 704 executes the executable code file corresponding to the service orchestration file, and sequentially invokes the services according to the execution sequence of one or more services contained in the service orchestration file and the configuration information of each service to obtain the service. The execution result of the call request;

The transceiver unit 702 is configured to return the execution result of the service invocation request to the user terminal corresponding to the service invocation request.

In a possible implementation manner, the transmission protocol corresponding to the service invocation request is the second transmission protocol; the acquiring the service invocation request includes:

The transceiver unit 702 is configured to receive an original call request sent by the user terminal, where the original call request is a request generated based on a first transmission protocol;

The processing unit 704 is configured to convert the original invocation request into a service invocation request corresponding to a second transmission protocol, where the first transmission protocol and the second transmission protocol are different.

According to an embodiment of the present application, each step involved in the service orchestration method shown in FIG. 2 and FIG. 6 may be performed by each unit in the service orchestration apparatus 70 shown in FIG. 7 . For example, steps S201 to S203 in the service orchestration method shown in FIG. 2 can be performed by the display unit 701 in the service orchestration apparatus 70 shown in FIG. 7 ; for another example, steps S601 to S601 in the service orchestration method shown in FIG. 6 Steps S602 and S604 may be performed by the processing unit 704 in the service orchestration apparatus 70 shown in FIG. 7 , and steps S603 and S605 may be performed by the transceiver unit 702 in the service orchestration apparatus 70 shown in FIG. 7 .

According to another embodiment of the present application, each unit in the service orchestration apparatus 70 shown in FIG. 7 may be respectively or all combined into one or several other units to form, or some of the unit(s) may be further It is divided into multiple units with smaller functions, which can realize the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of one unit may also be implemented by multiple units, or the functions of multiple units may be implemented by one unit. In other embodiments of the present application, the service orchestration apparatus 70 may also include other units. In practical applications, these functions may also be implemented with the assistance of other units, and may be implemented by cooperation of multiple units.

According to another embodiment of the present application, a general-purpose computing device, such as a computer, may be implemented on a general-purpose computing device including a central processing unit (CPU), a random access storage medium (RAM), a read-only storage medium (ROM), and other processing elements and storage elements. Run a computer program (including program code) capable of executing the steps involved in the corresponding methods as shown in FIG. 2 and FIG. 6 to construct the service orchestration apparatus 70 as shown in FIG. 7 , and to implement the services of the embodiments of the present application arrangement method. The computer program can be recorded on, for example, a computer-readable storage medium, loaded into the above-mentioned computing device via the computer-readable storage medium, and executed therein.

In the implementation of this application, the main interface is displayed, the main interface includes N nodes, and N is a positive integer; when there is a configuration operation for the target node, the configuration interface of the target node is displayed, and the configuration interface of the target node is used to obtain the target node's configuration interface. Configuration information, the configured target node corresponds to a service, and the target node is any node among N nodes; when there is a connection operation for N nodes, the node chain containing N nodes is displayed, and the node chain is used to generate services An orchestration file that contains the execution order for one or more services. This method is mainly that developers can efficiently implement service orchestration by dragging and dropping nodes in the visual interface of the service orchestration front-end 121 and configuring the rows of node information, which does not require developers to develop in the form of code, which can save development time. , reduce the workload, and better conform to the development concept of the cloud era.

Based on the foregoing method and apparatus embodiments, the embodiments of the present application provide a service orchestration device. Referring to FIG. 8 , it is a schematic structural diagram of a service orchestration device according to an embodiment of the present application. The service orchestration device 80 shown in FIG. 8 includes at least a processor 801, an input interface 802, an output interface 803, and a computer storage medium 804, wherein the processor 801, the input interface 802, the output interface 803, and the computer storage medium 804 can be connected through a bus or a computer storage medium 804. Connect in other ways.

A computer storage medium 804 may be stored in the memory 805 of the service orchestration device 80, the computer storage medium 804 for storing a computer program comprising program instructions, the processor 801 for executing the computer storage medium 804 Stored program instructions. The processor 801 (or called CPU (Central Processing Unit, central processing unit)) is the computing core and the control core of the service orchestration device 80, which is suitable for implementing one or more instructions, specifically suitable for loading and executing one or more computer The instruction thus implements the corresponding method flow or corresponding function.

Embodiments of the present application further provide a computer storage medium (Memory), where the computer storage medium is a memory device in the service orchestration device 80 and is used to store programs and data. It can be understood that, the computer storage medium here may include both a built-in storage medium in the service orchestration device 80 , and certainly also an extended storage medium supported by the service orchestration device 80 . The computer storage medium provides storage space in which the operating system of the service orchestration device 80 is stored. In addition, one or more instructions suitable for being loaded and executed by the processor 801 are also stored in the storage space, and these instructions may be one or more computer programs (including program codes). It should be noted that the computer storage medium here can be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk memory; optionally, it can also be at least one memory located far away from the aforementioned processor. computer storage media.

In one embodiment, the computer storage medium can be loaded by the processor 801 and execute one or more instructions stored in the computer storage medium to implement the above-mentioned corresponding steps of the service orchestration method shown in FIG. 2 and FIG. 6 . In a specific implementation, one or more instructions in the computer storage medium are loaded by the processor 801 and execute the following steps:

Displaying a main interface, the main interface includes N nodes, and N is a positive integer;

When there is a configuration operation for the target node, the configuration interface of the target node is displayed. The configuration interface of the target node is used to obtain the configuration information of the target node. The configured target node corresponds to a service, and the target node is the target node. any node in the N nodes;

When there is a connection operation for the N nodes, a node chain including the N nodes is displayed, and the node chain is used to generate a service orchestration file containing the execution order of one or more services.

In a possible implementation manner, each node corresponds to a node type, and the node type is divided according to the function of the corresponding service of the node; when the processor 801 has a configuration operation for the target node, the display unit of the target node configuration interface for:

When there is a configuration operation for the target node, obtain a pre-configuration file corresponding to the node type of the target node;

Displaying a configuration interface of the target node according to the pre-configuration file, where the configuration interface of the target node includes multiple file contents of the pre-configuration file;

When there is a selection operation on the target file content among the plurality of file contents, the target file content is used as the configuration information of the target node.

In a possible implementation manner, the multiple file contents of the pre-configuration file include service identifiers of multiple services, method identifiers of multiple methods included in each service, and multiple method parameters of each method; the When there is a selection operation for the target file content in the multiple file contents, the processor 801 uses the target file content as the configuration information of the target node, including:

When there is a selection operation for the service identifier of the target service in the service identifiers of the multiple services, displaying the method identifiers of the multiple methods included in the target service;

When there is a selection operation for the method identifier of the target method included in the target service, displaying a plurality of method parameters included in the target method;

When there is a selection operation for a target method parameter among multiple method parameters included in the target method, the service identifier of the target service, the method identifier of the target method, and the target method parameter are all used as the target The configuration information of the node, the target node corresponds to the target service.

In a possible implementation manner, the service orchestration file is a markup language file; the processor 801 is further configured to:

According to the node chain of the N nodes and the configuration information of each node, a service orchestration file is generated, and the service orchestration file also includes the configuration information of each service, and the configuration information of each service is corresponding to each service. The configuration information of the node is determined;

Parsing the service orchestration file to obtain an executable code file, where the executable code file includes the execution sequence of one or more services corresponding to the service orchestration file, and configuration information of each service;

The executable code file is deployed, and the deployed executable code file is used to respond to a service invocation request of the user terminal.

In a possible implementation manner, the processor 801 is further configured to:

When the debugging control is selected, the service orchestration file is tested to obtain a test result, the test result includes a first unit test result and a second unit test result, and the first unit test result is related to the A test result of the execution sequence of one or more services contained in the service orchestration file, and the second unit test result is a test result of the service execution result of the service orchestration file.

In a possible implementation manner, the processor 801 is further configured to:

obtaining a service invocation request, where the service invocation request includes a file identifier of the service orchestration file;

Execute the executable code file corresponding to the service orchestration file, call services in sequence according to the execution order of one or more services contained in the service orchestration file and the configuration information of each service, and obtain the execution result of the service invocation request ;

The execution result of the service invocation request is returned to the user terminal corresponding to the service invocation request.

In a possible implementation manner, the transmission protocol corresponding to the service invocation request is the second transmission protocol; the processor 801 obtains the service invocation request, including:

receiving an original invocation request sent by the user terminal, where the original invocation request is a request generated based on a first transmission protocol;

Converting the original invocation request into a service invocation request corresponding to a second transmission protocol, where the first transmission protocol and the second transmission protocol are different.

In the implementation of this application, the main interface is displayed, and the main interface includes N nodes, where N is a positive integer; when there is a configuration operation for the target node, the configuration interface of the target node is displayed, and the configuration interface of the target node is used to obtain the configuration of the target node. Information, the configured target node corresponds to a service, and the target node is any node among N nodes; when there is a connection operation for N nodes, the node chain containing N nodes is displayed, and the node chain is used to generate service orchestration file, the service orchestration file contains the execution order of one or more services. This method is mainly that developers can efficiently implement service orchestration by dragging and dropping nodes in the visual interface of the service orchestration front end 121 and configuring the row of node information, which does not require developers to develop in the form of code, which can save development time , reduce the workload, and better conform to the development concept of the cloud era.

It should be noted that, for the sake of simple description, the foregoing method embodiments are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the described action sequence. Because in accordance with the present application, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the device embodiments described above are only illustrative. For example, the division of the above-mentioned units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (10)

1. A method of service orchestration, the method comprising:

displaying a main interface, wherein the main interface comprises N nodes, and N is a positive integer;

when configuration operation for a target node exists, displaying a configuration interface of the target node, wherein the configuration interface of the target node is used for acquiring configuration information of the target node, the configured target node corresponds to a service, and the target node is any one of the N nodes;

when connection operation aiming at the N nodes exists, displaying a node chain containing the N nodes, wherein the node chain is used for generating a service arrangement file, and the service arrangement file contains an execution sequence of one or more services.

2. The method of claim 1, wherein each node corresponds to a node type, the node types being partitioned according to the functionality of the node corresponding service;

when the configuration operation for the target node exists, displaying a configuration interface of the target node, wherein the configuration interface comprises:

when configuration operation for the target node exists, acquiring a pre-configuration file corresponding to the node type of the target node;

displaying a configuration interface of the target node according to the pre-configuration file, wherein the configuration interface of the target node comprises a plurality of file contents of the pre-configuration file;

and when the selection operation for the target file content in the plurality of file contents exists, taking the target file content as the configuration information of the target node.

3. The method of claim 2, wherein the plurality of file contents of the pre-configured file comprise service identifications of a plurality of services, method identifications of a plurality of methods included in each service, and a plurality of method parameters of each method;

when there is a selection operation for a target file content of the plurality of file contents, taking the target file content as configuration information of the target node, including:

when there is a selection operation for a service identifier of a target service among the service identifiers of the plurality of services, displaying method identifiers of a plurality of methods included in the target service;

when there is a selection operation for a method identifier of a target method included in the target service, displaying a plurality of method parameters included in the target method;

when there is a selection operation for a target method parameter in a plurality of method parameters included in the target method, taking a service identifier of the target service, a method identifier of the target method, and the target method parameter as configuration information of the target node, where the target node corresponds to the target service.

4. The method of claim 1, wherein the service orchestration file is a file of a markup language; the method further comprises the following steps:

generating a service arrangement file according to the node chain of the N nodes and the configuration information of each node, wherein the service arrangement file further comprises the configuration information of each service, and the configuration information of each service is determined by the configuration information of the node corresponding to each service;

analyzing the service arrangement file to obtain an executable code file, wherein the executable code file comprises an execution sequence of one or more services corresponding to the service arrangement file and configuration information of each service;

and deploying the executable code file, wherein the deployed executable code file is used for responding to a service calling request of the user terminal.

5. The method of claim 4, wherein the primary interface further comprises a debug control, the method further comprising:

when the debugging control is selected, testing the service layout file to obtain a test result, wherein the test result comprises a first unit test result and a second unit test result, the first unit test result is a test result related to the execution sequence of one or more services contained in the service layout file, and the second unit test result is a test result related to the service execution result of the service layout file.

6. The method of claim 4, further comprising:

acquiring a service calling request, wherein the service calling request comprises a file identifier of the service arrangement file;

executing the executable code file corresponding to the service arrangement file, and calling the services in sequence according to the execution sequence of one or more services contained in the service arrangement file and the configuration information of each service to obtain the execution result of the service calling request;

and returning the execution result of the service calling request to the user terminal corresponding to the service calling request.

7. The method of claim 6, wherein the transmission protocol corresponding to the service invocation request is a second transmission protocol;

the acquiring the service call request includes:

receiving an original calling request sent by the user terminal, wherein the original calling request is a request generated based on a first transmission protocol;

and converting the original calling request into a service calling request corresponding to a second transmission protocol, wherein the first transmission protocol is different from the second transmission protocol.

8. A service orchestration device, the service orchestration device comprising:

the display unit is used for displaying a main interface, the main interface comprises N nodes, and N is a positive integer;

the display unit is further configured to display a configuration interface of the target node when configuration operation for the target node exists, where the configuration interface of the target node is used to obtain configuration information of the target node, the configured target node corresponds to a service, and the target node is any node in the N nodes;

the display unit is further configured to display a node chain including the N nodes when there is a connection operation for the N nodes, where the node chain is used to generate a service orchestration file, and the service orchestration file includes an execution order of one or more services.

9. A service orchestration device, the service orchestration device comprising:

a processor adapted to implement one or more instructions; and (c) a second step of,

a computer storage medium having stored thereon one or more instructions adapted to be loaded by the processor and to execute the service orchestration method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that it stores a computer program comprising program instructions which, when executed by a processor, cause the processor to carry out the service orchestration method according to any one of claims 1-7.

Images