Service orchestration method, apparatus, device, and storage medium

Abstract

The application relates to the technical field of computers, and discloses a service arrangement method and device, equipment and a storage medium, wherein the method comprises the following steps: displaying a main interface, the main interface comprising N nodes, N being a positive integer; when there is a configuration operation for a target node, displaying a configuration interface of the target node, the configuration interface of the target node being used for acquiring configuration information of the target node, the target node after configuration corresponding to a service, the target node being any node in the N nodes; and when there is a connection operation for the N nodes, displaying a node chain comprising the N nodes, the node chain being used for generating a service arrangement file, the service arrangement file comprising an execution sequence of one or more services. Through the method, the development efficiency of a developer for service arrangement can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, and in particular to a service orchestration method and device, equipment and a storage medium. BACKGROUND

[0002] With the rapid development of digital transformation, traditional monolithic services have been unable to meet the technical needs of current interconnected products, and therefore service orchestration has emerged. Service orchestration is the orderly weaving of various services to complete a certain business, and the aggregation of each service into a specific execution chain, so that a user can call one or more microservices in the back end through a call request.

[0003] At present, most service orchestration implementation methods are achieved through code writing, and therefore the development cycle is long and the efficiency is low for developers. Therefore, how to efficiently implement service orchestration development has become a technical problem to be solved. SUMMARY

[0004] The embodiments of the present application provide a service orchestration method, device, equipment and storage medium, which can improve the development efficiency of developers for service orchestration.

[0005] In one aspect, the present application discloses a service orchestration method, which comprises the following steps:

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

[0007] when there is a configuration operation for a target node, displaying a configuration interface of the target node, wherein the configuration interface of the target node is used to obtain configuration information of the target node, and the target node corresponds to a service after being configured, and the target node is any node in the N nodes;

[0008] when there is a connection operation for the N nodes, displaying a node chain comprising the N nodes, wherein the node chain is used to generate a service orchestration file, and the service orchestration file comprises an execution order of one or more services.

[0009] In one aspect, the present application discloses a service orchestration device, which comprises the following steps:

[0010] a display unit configured to display a main interface, wherein the main interface comprises N nodes, and N is a positive integer;

[0011] The display unit is further configured to, when there is a configuration operation for a target node, display a configuration interface of the target node, wherein the configuration interface of the target node is used to obtain configuration information of the target node, and the target node corresponds to a service after being configured, and the target node is any node in the N nodes;

[0012] The display unit is further configured to display a node chain containing the N nodes when there is a connection operation for the N nodes, the node chain being used to generate a service orchestration file containing an execution order of one or more services.

[0013] In an aspect, the present application discloses a service orchestration device, which comprises:

[0014] A processor is adapted to implement one or more instructions, and a computer storage medium stores one or more instructions, which are adapted to be loaded and executed by the processor to implement the service orchestration method.

[0015] In an aspect, the present application discloses a computer readable storage medium storing a computer program, the computer program comprising program instructions, which, when executed by a processor, cause the processor to implement the service orchestration method.

[0016] In an aspect, the present application discloses a computer program product or computer program, which comprises computer instructions stored in a computer readable storage medium. A processor of a service orchestration device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to cause the service orchestration device to implement the service orchestration method.

[0017] In an aspect, the present application discloses a computer program product or computer program, which comprises computer instructions stored in a computer readable storage medium. A processor of a service orchestration device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to cause the service orchestration device to implement the service orchestration method. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced. Obviously, the accompanying drawings in the following description only represent some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0019] Figure 1 is a schematic diagram of the architecture of a service orchestration system disclosed by an embodiment of the present application;

[0020] Figure 2 is a schematic diagram of the flow of a service orchestration method disclosed by an embodiment of the present application;

[0021] Figure 3 is a schematic diagram of the main interface of a service orchestration method disclosed by an embodiment of the present application;

[0022] Figure 4 is a schematic diagram of a configuration interface disclosed by an embodiment of the present application;

[0023] Figure 5 is a schematic diagram of a service orchestration connection method disclosed by an embodiment of the present application;

[0024] Figure 6 is a schematic diagram of the flow of another service orchestration method disclosed by an embodiment of the present application;

[0025] Figure 7 is a schematic diagram of the structure of a service orchestration device disclosed by an embodiment of the present application;

[0026] Figure 8 is a schematic diagram of the structure of a service orchestration device disclosed by an embodiment of the present application. DETAILED DESCRIPTION

[0027] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments only represent some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of the present application.

[0028] Before the service orchestration method provided by the present application is described, some technical terms related to the present application will be introduced.

[0029] 1、Domain Specific Language (DSL): A programming language designed for a specific domain with limited expressiveness. By limiting the problem boundary, the complexity is locked, and the programming efficiency is improved. Using DSL as a service orchestration declaration configuration has the following advantages: 1. It can reduce the language expression error rate; 2. It can enable developers who are not familiar with how to implement technology or even business personnel to understand the model; 3. The specific domain language provides a specific domain Application Programming Interface (API) to operate the model, which can improve development efficiency; 4. The model has important business knowledge, which makes it relatively easy to migrate solutions from one technology to another or between different versions of the same technology. Generally, it can be done by modifying the generator or interpreter appropriately. 5. It can use the model to configure an implementation process that includes multiple different technologies, thereby reducing the technical difficulty and workload of implementing a solution using these technologies. In the embodiments of the present application, DSL mainly uses a yaml format file to describe the service orchestration file. Optionally, files in formats such as json, hcl, etc. can also be used to describe the service orchestration file. Among them, yaml, json, hcl are all markup languages.

[0030] 2、Low code: A visual application development method, through low code development, 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 low code method to carry the orchestration configuration of the present solution has the following advantages: 1. More intuitive application construction, user logic can be defined using a visual method, and the experience of developing API layers by different developers is smoothed out. 2. Developers can use their own coded enhancements to expand the application, and when custom code is needed, 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 to reduce project development risk. 4. Make full use of public clouds to automatically manage the reliability and scalability of applications through simple configuration, thereby reducing the maintenance cost and workload of the infrastructure. 5. Fully embodies the devops (process, method and system collectively) concept, automatically builds the system after configuration, and builds a test and verification branch before deployment. In the embodiments of the present application, the service orchestration file is constructed in a graphical interface in a drag-and-drop form, without the need for developers to write code line by line to construct the service orchestration file, thereby realizing the development efficiency of front-end developers.

[0031] 3. Service orchestration: using various capabilities to orchestrate to complete a certain business, various capabilities are woven in order, and aggregated into a specific execution chain. A single call will trigger one or more requests to the backend service.

[0032] 4. Node.js: a JavaScript runtime environment based on Chrome V8 engine. Node.js uses an event-driven, non-blocking I / O model, which is very suitable for I / O intensive applications. In the application embodiment, Node.js mainly completes the following work: 1. Write the core function of the service orchestrator in Node.js version, provide microservice aggregation and orchestration capabilities, so that the client request can obtain multiple backend microservice data through one request, and the strong customized orchestration logic can be used to orchestrate the calling order of the microservice. 2. Provide a DSL parsing engine, which parses the DSL description and makes a chained call to the backend microservice according to a certain logic. 3. Write a code generator that can use a template engine to generate deployable service code using an abstract syntax tree, support secondary development, and further improve development efficiency. Optionally, Golang (a static strongly typed compiled language), Java, PHP, Python, etc. can also be used.

[0033] In combination with the above related introduction, please refer to Figure 1 , Figure 1 The architecture of a service orchestration system disclosed in the application embodiment is shown in the following figure: Figure 1 The architecture diagram 100 of the service orchestration system includes a user terminal 110, a service orchestration device 120, and a 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 in communication. Specifically, the user terminal 110 is mainly used to send a service call request to the service orchestration device 120, or directly send a service call request to the server 130; the service orchestration device 120 is mainly used to implement the service orchestration method of the application, and in response to the service call request, it sequentially calls various services stored in the server 130, and then returns the execution result to the user terminal 110; compared with the user terminal 110 directly sending a service call request to the server 130, the service orchestration device in the architecture shown in the application embodiment implements the aggregation function of the service, and when the user terminal 110 initiates a service call request including multiple services, the service orchestration device 120 can be used to call the service, which can effectively reduce the network transmission cost consumed by the user terminal to call the service multiple times. The server 130 is mainly used to store services with various functions, and the services also include various microservices.

[0034] Based on the service orchestration system, the application provides a service orchestration method, in particular:

[0035] In a possible implementation, the service orchestration method is mainly executed by the service orchestration front end 121: a main interface is displayed, the main interface including N nodes, N being a positive integer; when there is a configuration operation for a target node, a configuration interface of the target node is displayed, the configuration interface of the target node being used to obtain configuration information of the target node, the target node after configuration corresponding to a service, the target node being 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, the node chain being used to generate a service orchestration file, the service orchestration file including an execution order of one or more services. The method is mainly used to configure information corresponding to the nodes through the service orchestration front end 121, so that service orchestration is efficiently implemented, the developer does not need to develop in the form of code, the development time can be saved, the workload can be reduced, and the development concept of the cloud era is better adapted.

[0036] In a possible implementation, the service orchestration method is mainly executed by the service orchestration server 122: the service orchestration file completed by the service orchestration front end 121 is parsed to obtain an executable code file, the executable code file including an execution order of one or more services corresponding to the service orchestration file and configuration information of each service; the executable code file is deployed, the deployed executable code file being used to respond to a service call request of a user terminal; the service call request is obtained, the service call request including a file identifier of the service orchestration file; the executable code file corresponding to the service orchestration file is executed, services are called in sequence according to the execution order of one or more services included in the service orchestration file and the configuration information of each service, and an execution result of the service call request is obtained; the execution result of the service call request is returned to the user terminal corresponding to the service call request. Through the service orchestration server 122, the executable code corresponding to the service orchestration file is directly executed, the returned step of repeated calling according to each service is not needed, and finally the execution result of the calling request is returned, so that the number of calling times of the user terminal can be effectively reduced, and the network transmission cost of the calling interface can be reduced.

[0037] In a possible implementation, the user terminal 110 includes, but is not limited to, a handheld device, a vehicle-mounted device, a wearable device, or a computing device with wireless communication function. Exemplarily, the user terminal 110 can be a mobile phone, a tablet computer, or a computer with wireless transceiver function. It can also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in unmanned driving, a wireless terminal device in telemedicine, a wireless terminal device in smart grid, a wireless terminal device in smart city, a wireless terminal device in smart home, and the like. The service orchestration server 122 and the server 130 can be a standalone physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, and basic cloud computing services such as big data and artificial intelligence platform.

[0038] Based on the above service orchestration system, the application provides a service orchestration method, as shown in Figure 2 Fig. 1 is a flow diagram of a service orchestration method according to an embodiment of the application. The service orchestration method can be executed by the service orchestration front end 121 in the service orchestration setting 120. The service orchestration method can specifically include the following steps:

[0039] S201, display a main interface, the main interface including N nodes, N being a positive integer.

[0040] The main interface is a visual interface for configuring nodes corresponding to service orchestration files. The main interface can refer to a method of visual application development, such as a lowcode development interface. Through the interface, developers of different experience levels can create web and mobile applications using graphical user interfaces, drag-and-drop components, and model-driven logic. In the embodiments of the application, the main interface is an interface for implementing service orchestration by dragging and dropping. Developers can select different types of nodes according to requirements and place them in the main interface, which can reduce the learning cost and learning burden of developers.

[0041] In a possible implementation, when service orchestration is needed, a developer clicks a main interface on a service orchestration front end, and the main interface is displayed. The main interface includes an add control, and the developer can add a node through the add control. The developer can select a node type for each node. After the developer adds a node, the main interface displayed includes the node added by the user.

[0042] For example, the main interface can be as shown in Figure 3 , which is a schematic diagram of a main interface of a service orchestration method disclosed in an embodiment of the present application. The interface has an add control 301. The developer clicks the add control 301 to display an interface 302. The developer can input a node type in the interface 302 according to a service to be selected. When the node type is determined, a node similar to node 1 is obtained. As shown in Figure 3 , the main interface displays three nodes, that is, N = 3. Optionally, the main interface also includes a view control. When 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 also includes a debug control. When the developer clicks the debug control, a corresponding execution result is obtained.

[0043] S202, when there is a configuration operation on a target node, a configuration interface of the target node is displayed. The configuration interface of the target node is used to obtain configuration information of the target node. The target node corresponds to a service after being configured. The target node is any one of the N nodes.

[0044] In the main interface, there are nodes dragged by the developer. Each node corresponds to a node type. The node types of several nodes can be the same, or different nodes can correspond to different node types. The specific node types need to be determined according to the services to be called by the developer during configuration. If the called service is implemented based on an rpc protocol, the corresponding node type can be an rpc type, where rpc is remote procedure call.

[0045] In a possible implementation, when there is a configuration operation on a target node, the service arrangement device acquires a pre-configuration file corresponding to a node type of the target node, and then displays a configuration interface of the target node on a main interface, and the configuration interface of the target node includes multiple file contents of the pre-configuration file. When there is a selection operation on a target file content, the target file content is taken as configuration information of the target node, and the target file content is also one of the multiple file contents of the pre-configuration file. Optionally, the configuration interface of the target node can be displayed at any position of the main interface. The target node is any one of N nodes, for example, any one of the three nodes shown in FIG. 1. Figure 3 The configuration operation can be specifically that a developer clicks the target node. The pre-configuration file is related to a node type, for example, a node of a trpc protocol type, and the corresponding pre-configuration file is "Polaris configuration" (the name is self-defined and used to distinguish different configurations). A node of an ilive protocol type corresponds to a pre-configuration file "l5 configuration".

[0046] For example, Figure 4 FIG. 4 shows a configuration interface of a target node disclosed in the application, and the configuration interface 401 of the target node is located on the right side of the main interface.

[0047] In a possible implementation, the multiple file contents of the pre-configuration file include service identifiers of multiple services, method identifiers of multiple methods contained in each service, and multiple method parameters of each method. One service can have multiple methods, and the method parameters corresponding to each method are different. When there is a configuration operation on a target node, the configuration interface of the target node (how to configure the target node) is displayed, including: when there is a selection operation on a service identifier of a target service, a method identifier list of multiple methods contained in the target service is displayed; when there is a selection operation on a method identifier of a target method, a multiple method parameter list of the target method is displayed; and when there is a selection operation on a target method parameter, the service identifier of the target service, the method identifier of the target method, and the target method parameter are all taken as configuration information of the target node, and the target node corresponds to the target service. Each service corresponds to a service identifier, and one service identifier can correspond to a service name. Similarly, each method corresponds to a method identifier, and each method identifier can also correspond to a method name.

[0048] For example, the configuration interface of the target node can be specifically as shown in FIG. 4. Figure 4As shown, it is a configuration interface schematic diagram of a target node disclosed by the application embodiment, wherein 401 is a configuration interface of node 1, and the interface includes service pb file setting (the pb file is a binary file representing model structure without source code), service routing setting, and namespace setting. The service routing can be obtained according to the parsed service pb file, and the namespace corresponds to the node type. The developer can dynamically select the namespace. Figure 4 In the configuration interface, service name setting, method name setting, and method parameter setting are further included. Since the service name, the method name, and the method parameter have a dependency relationship, the developer has a sequence when configuring. The service name, the method name, and the method parameter are all in the form of a drop-down box and are displayed to the developer for selection. The displayed service name, the method name, and the method parameter are all obtained according to the preconfigured 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 method name associated with the selected service name. When the target method is selected, the drop-down box of the method parameter contains the method parameter contained in the target method. That is, the method parameter contained in the drop-down box of the method parameter is the parameter associated with the selected method name.

[0049] S203, when there is a connection operation for N nodes, display a node chain containing N nodes, the node chain is used to generate a service orchestration file, and the service orchestration file contains the execution order of one or more services.

[0050] In a possible implementation, after steps S201-S202, N nodes that have been configured can be obtained. When there is a connection operation for N nodes, a node chain containing N nodes is displayed. That is, the developer connects the N nodes through a connection line 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. The multiple nodes can flow from node a to node b and then from node b to node c. Or it can flow from node a to node b and from node b to node c, and node b also flows to node d.

[0051] Specifically, as shown in Figure 5 It is a service orchestration connection method disclosed by the application embodiment. As can be seen, Figure 2 501 in the above is a connection method of a node chain, and 502 is another connection method of a node chain.

[0052] In a possible implementation, when the developer connects the configured N nodes, when the developer clicks the debugging control on the main interface, a service orchestration file is generated. The generated service orchestration file is a markup language file, such as the aforementioned yaml format file, json format file, or hcl format file. At the same time, the test result of the node chain (that is, the service orchestration file) is displayed on the interface. The service orchestration file further 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 result includes a 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 generated by the node chain. The second unit test result is a test result about the business execution result of the service orchestration file. Specifically, the first unit test result is used to detect whether the execution order of the multiple services in the service orchestration file is the same as the preset execution order. If yes, it is proved that the order is correct. If not, the developer needs to adjust the order, which can be directly modified in the main interface through the drag-and-drop method. The second unit test result is used to detect whether the business execution result of the service orchestration is the same as the preset execution result. If yes, it is proved that the service orchestration is successful. If not, the developer needs to adjust each node used by the service orchestration file. Optionally, the test result further includes a third unit test result. The third unit test result is about 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 not, the front-end developer needs to change the configuration information of the node.

[0053] In summary, the work of the service orchestration front end 121 can be summarized as follows: first, the developer drags out a number of nodes needed by the developer on the visual interface (such as the aforementioned low-code development interface), and configures the configuration information of each node according to the pre-configuration file (configures the configuration information in the configuration interface shown) Figure 4 The second step is that the developer arranges the nodes 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, a workflow (corresponding to the aforementioned node chain) and a corresponding workflow id (service orchestration file identifier) are obtained by clicking Save. The id can be used as a parameter when calling the execution workflow interface. The third step is that, in the debugging interface provided by the platform, the obtained workflow id is used to obtain the aggregated data of the service orchestration file and the test result.

[0054] In a possible implementation, the node chain generated in the main interface corresponds to a service orchestration file, and the service orchestration file can be used to directly implement a call to the service orchestration file. For the service orchestration file, there is a corresponding trigger action. When the trigger action receives a service call request initiated by a user terminal, the trigger action directly returns an execution result of the service orchestration file to the user. The trigger action can also be triggered by a developer and can obtain the execution result of the service orchestration file. This case corresponds to Platform as a Service (PaaS), which means that a user only needs to call a platform for developing the service orchestration to obtain an execution result of a service call request.

[0055] In the implementation of the present application, a main interface is displayed, the main interface includes N nodes, and N is a positive integer. When there is a configuration operation for a target node, a configuration interface of the target node is displayed, the configuration interface of the target node is used to obtain configuration information of the target node, and the target node after configuration corresponds to a service. The target node is any node of 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. The service orchestration file includes an execution sequence of one or more services. This method mainly enables a developer to efficiently implement service orchestration by dragging and dropping nodes in a visual interface of a service orchestration front end 121 and performing line configuration of node information, so that the developer does not need to develop in the form of code, development time can be saved, workload can be reduced, and the development concept of the cloud era is better adapted.

[0056] Based on the above service orchestration system and service orchestration method, the present application provides another service orchestration method, as shown in Figure 6 The flowchart of another service orchestration method disclosed in the implementation of the present application is shown in FIG. 6. The service orchestration method can be executed by a service orchestration server 122 in a service orchestration setting 120. The service orchestration method can specifically include the following steps:

[0057] S601, parse the service orchestration file to generate an executable code file. 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.

[0058] In a possible implementation, when 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 in DSL (Domain Specific Language), which can be a file in yaml format, or a file in json, hcl, or other formats. Further, the service orchestration front end 121 sends the service orchestration file to the service orchestration server 122.

[0059] Further, the registration 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 service orchestration file received includes the execution order of one or more services, the service orchestration server includes a node information interface, and the node information 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 order of one or more services corresponding to the service orchestration file and the configuration information of each service. The parsed executable code file can be divided into two types, one of which is an executable code file with a runtime, and the other is an executable code file without a runtime.

[0060] The generation process of the executable code file with the runtime is that the parser directly generates the executable code file according to the service orchestration file. The executable code file with the runtime can ensure the consistency of the executable code file and the service orchestration file, so as to reduce the error rate.

[0061] The generation process of the executable code file without the runtime is that the parser generates an auxiliary executable code file according to the service orchestration file, the auxiliary executable code file is manually edited by the developer, and the executable code file without the runtime is obtained. The executable code file without the runtime has stronger autonomy for the developer, and the developer can customize and write according to the demand.

[0062] 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, Golang language, which can better adapt to the language use habits and performance of the front-end developer, and also can be a compiled language such as Java, PHP, Python, etc.

[0063] S602, deploy the executable code file, and the deployed executable code file is used to respond to the service call request of the user terminal.

[0064] In a possible implementation, the service orchestration server can also deploy the parsed executable code file, and the purpose is to respond to the service call request initiated by the user terminal. Each deployed executable code file and the service orchestration file have a corresponding relationship, which can be distinguished by an identifier. For example, one service orchestration file corresponds to one id, and each id corresponds to one executable code file. Specifically, it can be as shown in Table 1. The file identifier of the service orchestration file and the executable code file have the same identifier information, so that the service orchestration server can better manage the service orchestration file.

[0065] Table 1

[0066] File identification of service orchestration file Executable code file identification id = 1 File 1 …… …… id = 1 File N

[0067] Optionally, the executable code file can be deployed by a developer or by a user terminal in the case that the user understands the logic of service orchestration. No limitation is made herein. The obtained executable code can be deployed to various cloud deployment platforms, such as Tencent cloud containers, cloud services, cloud functions, and the like, or can be deployed to various enterprise internal deployment platforms.

[0068] S603, a service calling request is obtained, the service calling request including a file identifier of the service orchestration file.

[0069] In a possible implementation, when the user terminal initiates the service calling request, the service orchestration server can obtain the service calling request, so as to quickly implement service calling of the service orchestration server and return an execution result to the user terminal. The service calling request includes a file identifier of the service orchestration file, such as the identifier information shown in Table 1, such as id = 1.

[0070] In a possible implementation, after receiving the service calling request, the service orchestration server further involves conversion of a network transmission protocol. Specifically, it can be explained as follows: first, the service orchestration server receives an original calling request sent by the user terminal, the original calling request being a request generated based on a first transmission protocol, and the service orchestration server can analyze a calling request of a second transmission protocol. Therefore, when the original calling request is sent to the service orchestration server, it is determined whether the first transmission protocol and the second transmission protocol are consistent. If they are consistent, the calling request corresponding to the service calling request can be directly executed. If they are inconsistent, the service orchestration server will first convert the original calling request into a service calling request corresponding to the second transmission protocol, and then process the service calling request.

[0071] For example, the original calling request sent by the user terminal is a request generated based on a first transmission protocol, such as a Hypertext Transfer Protocol (HTTP), and the service orchestration server can analyze a calling request of a second transmission protocol, such as a TRPC protocol. At this time, the HTTP protocol needs to be converted into the TRPC protocol. When the service orchestration server returns the execution result to the user terminal, the TRPC protocol needs to be converted into the HTTP protocol, so as to facilitate the user terminal to receive the execution result. The TRPC protocol is generated based on the RPC protocol.

[0072] S604, executing the executable code file corresponding to the service orchestration file, sequentially invoking services according to the execution order of one or more services contained in the service orchestration file and the configuration information of each service, and obtaining the execution result of the service invocation request.

[0073] In a possible implementation, when the service orchestration server obtains the service invocation request and the file identifier of the service orchestration file carried by the service invocation request, the execution workflow interface included in the service orchestration server can invoke the encapsulated workflow interface according to the file identifier of the service orchestration file, and execute the executable code file encapsulated by the workflow interface. Specifically, the execution workflow interface sequentially invokes services 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 execution result of the service invocation request. Through the invocation of the workflow interface, the aggregation of services is realized, and the network transmission cost of multiple invocations of different interfaces by the user terminal can be effectively reduced.

[0074] S605, returning the execution result of the service invocation request to the user terminal corresponding to the service invocation request.

[0075] In a possible implementation, after the service orchestration server obtains the execution result of the service invocation request, the execution result is returned to the user terminal, so as to meet the service invocation demand of the user.

[0076] In a possible implementation, the execution result of the service invocation request can be returned to the user terminal through the execution interface.

[0077] Optionally, the service orchestration server also provides a custom plug-in mechanism, supports developers to customize and expand logic, and front-end developers can insert custom logic into the service orchestration server by inserting rules to expand orchestration capabilities. Specifically, the service orchestration server can use the Plugin (Plug-in, addin, add-in, addon or add-on) plug-in mechanism, use dependency injection and life cycle hooks, and let front-end developers easily write custom logic. The plug-in mechanism can be understood as another insertion interface. For example, a developer customizes a code with a "log" or "monitoring" function, defines the execution time in the code, encapsulates the code into an insertion interface, and executes the custom code encapsulated in the insertion interface in parallel when the workflow interface is invoked to execute the executable code encapsulated by the workflow interface, so as to simultaneously implement service invocation and log recording in the process.

[0078] In a possible implementation, the developer can also pull other types of nodes in the main interface, such as a web hook node, a graphql node, a merge node, and the like. The developer can implement different functions by configuring these nodes, that is, each of the above nodes does not correspond to a service. The web hook node is an API concept, which is one of the use patterns of microservice API, also known as reverse API, that is, the front end does not actively send a request, and the back end completely pushes; the graphql node is a declarative data acquisition specification and query language for API, and a user can query an execution result by calling the node; and the merge node is a synthetic node in a general sense, which is needed in the process of aggregating data to implement aggregation.

[0079] According to the above embodiments, in a possible implementation method, on the basis of implementing the service orchestration method, different functions can be implemented by calling interfaces corresponding to different nodes, for example, continuous integration (CI) and continuous deployment (CD) can be implemented by calling an interface corresponding to a web hook node. The "CI" in CI / CD belongs to the automation process of the developer. Successful CI means that new changes of application code are periodically built, tested, and merged into a shared repository. The "CD" in CI / CD refers to continuous delivery and / or continuous deployment. For another example, a MOCK test can be implemented by a JSON node, where JSON (JavaScript Object Notation) is a lightweight data exchange format, that is, data transmitted by JSON is used to simulate a MOCK test. Mock testing is a test method in which a virtual object (Mock object) is created to test some objects that are not easy to construct (such as HttpServletRequest, which can be constructed only in a Servlet container) or not easy to obtain (such as a ResultSet object in JDBC) in a test process. For another example, a low-code configuration activity page can be implemented by an activity configuration node, that is, by configuring an activity configuration node, a visual interface (that is, a low-code configuration activity page) can be obtained by calling the activity configuration node.

[0080] In the embodiment of the present application, the service arrangement server parses the service arrangement file to obtain an executable code file, the executable code file includes the execution order of one or more services corresponding to the service arrangement file 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 calling request of the user terminal; the service calling request is obtained, the service calling request includes the file identifier of the service arrangement file; the executable code file corresponding to the service arrangement file is executed, the services are sequentially called according to the execution order of one or more services included in the service arrangement file and the configuration information of each service, and the execution result of the service calling request is obtained; and the execution result of the service calling request is returned to the user terminal corresponding to the service calling request. By directly executing the executable code corresponding to the service arrangement file through the service arrangement server, the returned steps do not need to be repeatedly called according to each service, and finally the execution result of the calling request can be returned, which can effectively reduce the calling times of the user terminal and reduce the network transmission cost of the calling interface.

[0081] According to Figure 2 and Figure 6 It can be known from the embodiments described above that the service arrangement method provided by the present application can smoothly migrate the existing services on the visual interface by relying on DSL without affecting the existing services (that is, the service arrangement 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 comply with the development concept in the cloud era. The service arrangement method of the present application is constructed in the form of drag and drop, and does not need to be developed in the form of code by the developer, so the learning cost and mental burden of the user are reduced, the development efficiency of the developer can be improved, the engineering manpower investment in product development is reduced, and the possibility of subsequent platform productization is provided. The service arrangement method of the present application can debug the service arrangement file on the visual interface, and does not need to be tested in sequence at the API gateway layer, so the workload is greatly reduced and the testing is easier, and the data security is easier to guarantee. The service arrangement method of the present application can realize service aggregation through encapsulation of the executable code, and the user terminal only needs to call one interface to obtain the execution result of the calling request when calling multiple services, which can effectively reduce the network transmission cost of multiple calling interfaces of the client.

[0082] Based on the above service arrangement system and service arrangement method, the embodiment of the present application discloses a service arrangement device, as shown in Figure 7 The structure of the service arrangement device disclosed by the embodiment of the present application is a schematic view, Figure 7 The service arrangement device 70 shown in FIG. 7 can run the following units:

[0083] The display unit 701 is configured to display a main interface, and the main interface includes N nodes, where N is a positive integer.

[0084] 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, the configuration interface of the target node being used to obtain configuration information of the target node, the target node corresponding to one service, and the target node being any one of the N nodes.

[0085] The display unit 701 is further configured to display a node chain containing the N nodes when there is a connection operation for the N nodes, the node chain being used to generate a service orchestration file, and the service orchestration file containing execution sequences of one or more services.

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

[0087] The transceiver unit 702 is configured to obtain a preconfigured file corresponding to the node type of the target node when there is a configuration operation for the target node.

[0088] The display unit 701 is further configured to display the configuration interface of the target node according to the preconfigured file, and the configuration interface of the target node includes multiple file contents of the preconfigured file.

[0089] The determination unit 703 is configured to take a target file content as the configuration information of the target node when there is a selection operation for the target file content in the multiple file contents.

[0090] In a possible implementation, the multiple file contents of the preconfigured file include service identifiers of multiple services, method identifiers of multiple methods included in each service, and multiple method parameters of each method; and the determination unit takes the target file content as the configuration information of the target node when there is a selection operation for the target file content in the multiple file contents, including:

[0091] The display unit 701 is configured to display method identifiers of multiple methods included in a target service when there is a selection operation for a service identifier of the target service in the service identifiers of the multiple services.

[0092] The display unit 701 is further configured to display multiple method parameters included in a target method when there is a selection operation for the method identifier of the target method included in the target service.

[0093] The determining unit 703 is further configured to, when there is a selection operation on a target method parameter in the plurality of method parameters contained in the target method, take the service identifier of the target service, the method identifier of the target method, and the target method parameter as the configuration information of the target node, the target node corresponding to the target service.

[0094] In a possible implementation, the service orchestration file is a file in a markup language; the processing unit 704 is configured to:

[0095] generate a service orchestration file according to the node chain of the N nodes and the configuration information of each node, the service orchestration file further including configuration information of each service, the configuration information of each service being determined by the configuration information of the node corresponding to each service;

[0096] parse the service orchestration file to obtain an executable code file, the executable code file including the execution order of one or more services corresponding to the service orchestration file, and the configuration information of each service;

[0097] deploy the executable code file, the deployed executable code file being configured to respond to a service invocation request of a user terminal.

[0098] In a possible implementation, the processing unit 704 is configured to, when the debugging control is selected, test the service orchestration file to obtain a test result, the test result including a first unit test result and a second unit test result, the first unit test result being a test result about the execution order of one or more services contained in the service orchestration file, and the second unit test result being a test result about a business execution result of the service orchestration file.

[0099] In a possible implementation, the transceiving unit 702 is further configured to obtain a service invocation request, the service invocation request including a file identifier of the service orchestration file.

[0100] The processing unit 704 executes the executable code file corresponding to the service orchestration file, and invokes 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, to obtain an execution result of the service invocation request.

[0101] The transceiving unit 702 is configured to return the execution result of the service invocation request to a user terminal corresponding to the service invocation request.

[0102] In a possible implementation, a transmission protocol corresponding to a service invocation request is a second transmission protocol; and the obtaining of the service invocation request includes:

[0103] The transceiver unit 702 is used to receive the original call request sent by the user terminal, the original call request being a request generated based on the first transmission protocol;

[0104] The processing unit 704 is used to convert the original call request into a service call request corresponding to a second transport protocol, wherein the first transport protocol and the second transport protocol are different.

[0105] According to one embodiment of this application, Figure 2 as well as Figure 6 The service orchestration method shown can involve various steps that can be derived from... Figure 7 This is performed by the individual units in the service orchestration apparatus 70 shown. For example, Figure 2 In the service orchestration method shown, steps S201 to S203 can be derived from... Figure 7 The service orchestration apparatus 70 shown is executed by the display unit 701; for example, Figure 6 In the service orchestration method shown, steps S601 to S602 and step S604 can be derived from... Figure 7 The processing unit 704 in the service orchestration apparatus 70 shown executes steps S603 and S605, which can be performed by... Figure 7 The transceiver unit 702 in the service orchestration apparatus 70 shown performs this function.

[0106] According to another embodiment of this application, Figure 7 The units in the service orchestration apparatus 70 shown can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the service orchestration apparatus 70 may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0107] According to another embodiment of this application, the following can be achieved by running on a general-purpose computing device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), a device capable of performing operations such as... Figure 2 as well as Figure 6 The computer program (including program code) for each step involved in the corresponding method shown, to construct such... Figure 7The service arrangement device 70 shown in the figure, and to implement the service arrangement method of the embodiments of the present application. The computer program can be recorded on, for example, a computer readable storage medium, and loaded into the above-mentioned computing device through the computer readable storage medium, and run therein.

[0108] In the embodiments of the present application, a main interface is displayed, the main interface including N nodes, N being a positive integer; when there is a configuration operation for a target node, a configuration interface of the target node is displayed, the configuration interface of the target node being used to obtain configuration information of the target node, the target node after configuration corresponding to a service, the target node being any one of the N nodes; when there is a connection operation for the N nodes, a node chain containing the N nodes is displayed, the node chain being used to generate a service arrangement file, the service arrangement file containing an execution order of one or more services. The method mainly enables the developer to drag and drop the nodes in the visual interface of the service arrangement front end 121 and perform line configuration of the node information, thereby efficiently implementing service arrangement, without the developer developing in the form of code, which can save development time and reduce workload, and better conforms to the development concept in the cloud era.

[0109] Based on the above method and device embodiments, the embodiments of the present application provide a service arrangement device. Referring to Figure 8 , a structural schematic diagram of a service arrangement device provided by the embodiments of the present application. Figure 8 The service arrangement device 80 shown in the figure at least includes 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 other means.

[0110] The computer storage medium 804 can be stored in the memory 805 of the service arrangement device 80, and the computer storage medium 804 is used to store a computer program, the computer program including program instructions, and the processor 801 is used to execute the program instructions stored in the computer storage medium 804. The processor 801 (or CPU (Central Processing Unit, Central Processor)) is the computing core and control core of the service arrangement device 80, which is suitable for implementing one or more instructions, and is specifically suitable for loading and executing one or more computer instructions to implement a corresponding method flow or a corresponding function.

[0111] The embodiment of the present application further provides a computer storage medium (Memory), which is a memory device in the service arrangement device 80 and is used for storing programs and data. It can be understood that the computer storage medium herein can include a built-in storage medium in the service arrangement device 80, and of course can also include an extended storage medium supported by the service arrangement device 80. The computer storage medium provides a storage space, and the storage space stores an operating system of the service arrangement device 80. In addition, one or more instructions suitable for being loaded and executed by the processor 801 are also stored in the storage space, and the instructions can be one or more computer programs (including program codes). It should be noted that the computer storage medium herein can be a high-speed RAM memory, or a non-volatile memory such as at least one disk memory; and optionally can also be at least one computer storage medium located away from the aforementioned processor.

[0112] In one embodiment, the computer storage medium can be loaded and executed by the processor 801 to implement the corresponding steps of the service arrangement method shown in the above description. Figure 2 And Figure 6 In a specific implementation, the one or more instructions in the computer storage medium are loaded and executed by the processor 801 to implement the following steps:

[0113] displaying a main interface, the main interface including N nodes, N being a positive integer;

[0114] when there is a configuration operation for a target node, displaying a configuration interface of the target node, the configuration interface of the target node being used to acquire configuration information of the target node, the target node after configuration corresponding to a service, the target node being any node in the N nodes;

[0115] when there is a connection operation for the N nodes, displaying a node chain including the N nodes, the node chain being used to generate a service arrangement file, the service arrangement file including an execution order of one or more services.

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

[0117] when there is a configuration operation for the target node, acquiring a pre-configuration file corresponding to the node type of the target node;

[0118] display a configuration interface of the target node according to the pre-configuration file, the configuration interface of the target node including a plurality of file contents of the pre-configuration file;

[0119] when there is a selection operation on a target file content in the plurality of file contents, the target file content is taken as the configuration information of the target node.

[0120] In a possible implementation, the plurality of file contents of the pre-configuration file includes service identifiers of a plurality of services, method identifiers of a plurality of methods contained in each service, and a plurality of method parameters of each method; and when there is a selection operation on a target file content in the plurality of file contents, the processor 801 takes the target file content as the configuration information of the target node, including:

[0121] when there is a selection operation on a target service identifier in the service identifiers of the plurality of services, displaying the method identifiers of the plurality of methods contained in the target service;

[0122] when there is a selection operation on a target method identifier of a target method contained in the target service, displaying the plurality of method parameters contained in the target method;

[0123] when there is a selection operation on a target method parameter in the plurality of method parameters contained in the target method, taking the service identifier of the target service, the method identifier of the target method, and the target method parameter as the configuration information of the target node, the target node corresponding to the target service.

[0124] In a possible implementation, the service orchestration file is a file in a markup language; and the processor 801 is further configured to:

[0125] generating a service orchestration file according to the node chain of the N nodes and the configuration information of each node, the service orchestration file further including configuration information of each service, the configuration information of each service being determined by the configuration information of the node corresponding to the service;

[0126] parsing the service orchestration file to obtain an executable code file, the executable code file including an execution order of one or more services corresponding to the service orchestration file, and the configuration information of each service;

[0127] deploying the executable code file, the deployed executable code file being used to respond to a service invocation request of a user terminal.

[0128] In a possible implementation, the processor 801 is further configured to:

[0129] When the debugging control is selected, the service orchestration file is tested to obtain a test result, the test result including a first unit test result and a second unit test result, the first unit test result being a test result about an execution order of one or more services contained in the service orchestration file, and the second unit test result being a test result about a business execution result of the service orchestration file.

[0130] In a possible implementation, the processor 801 is further configured to:

[0131] obtain a service invocation request, the service invocation request including a file identifier of the service orchestration file;

[0132] execute an executable code file corresponding to the service orchestration file, and sequentially invoke services according to an execution order of one or more services contained in the service orchestration file and configuration information of each service, to obtain an execution result of the service invocation request;

[0133] return the execution result of the service invocation request to a user terminal corresponding to the service invocation request.

[0134] In a possible implementation, a transmission protocol corresponding to the service invocation request is a second transmission protocol; and the processor 801 obtains the service invocation request by:

[0135] receiving an original invocation request sent by the user terminal, the original invocation request being a request generated based on a first transmission protocol;

[0136] converting the original invocation request into a service invocation request corresponding to a second transmission protocol, the first transmission protocol being different from the second transmission protocol.

[0137] In the implementation of the present application, a main interface is displayed, the main interface including N nodes, N being a positive integer; when there is a configuration operation for a target node, a configuration interface of the target node is displayed, the configuration interface of the target node being used to obtain configuration information of the target node, the target node corresponding to a service after being configured, the target node being any one of the N nodes; when there is a connection operation for the N nodes, a node chain including the N nodes is displayed, the node chain being used to generate a service orchestration file, the service orchestration file containing an execution order of one or more services. This method mainly enables a developer to efficiently implement service orchestration by dragging and dropping nodes in a visual interface of a service orchestration front end 121 and configuring node information, so that the developer does not need to develop in the form of code, development time can be saved, workload can be reduced, and the development concept of the cloud era is better adapted.

[0138] It should be noted that, for the foregoing method embodiments, the sequences of the described actions are not necessarily required to practice the present application, nor are the sequences of the described actions necessarily required in the implementations of these embodiments. Further, some of the described acts or events can occur in a different sequence, be added, omitted, or occur concurrently.

[0139] In several embodiments provided in the present application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of the above-described units is merely a logical function division. In actual implementation, another division manner can be adopted. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0140] The above describes only the specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A service orchestration method, characterized by, The method comprises: displaying a main interface, the main interface comprising N nodes, N being a positive integer; when there is a configuration operation for a target node, displaying a configuration interface of the target node, the configuration interface of the target node being used to acquire configuration information of the target node, the configuration information comprising a service identifier corresponding to the target node, a method identifier and a method parameter, the target node corresponding to one service after configuration, the target node being any node in the N nodes; when there is a connection operation for the N nodes, displaying a node chain comprising the N nodes; generating a service orchestration file according to the node chain of the N nodes and the configuration information of each node, the service orchestration file being a file described by a markup language across technology stacks, comprising an execution sequence of one or more services and the configuration information of each service, the configuration information of each service being determined by the configuration information of the node corresponding to each service; parsing the service orchestration file to obtain an executable code file, the executable code file comprising at least one of an executable code file with a runtime and an executable code file without a runtime, the executable code file without a runtime being obtained from an editable auxiliary executable code file generated according to the service orchestration file; deploying the executable code file, the deployed executable code file being used to respond to a service call request of a user terminal.

2. The method of claim 1, wherein, Each node corresponds to a node type, the node type being divided according to the function of the service corresponding to the node; when there is a configuration operation for a target node, displaying a configuration interface of the target node, the configuration interface of the target node being used to acquire configuration information of the target node, the configuration information comprising a service identifier corresponding to the target node, a method identifier and a method parameter, the target node corresponding to one service after configuration, the target node being any node in the N nodes; when there is a configuration operation for a target node, acquiring a pre-configuration file corresponding to the node type of the target node; displaying the configuration interface of the target node according to the pre-configuration file, the configuration interface of the target node comprising multiple file contents of the pre-configuration file; when there is a selection operation for a target file content in the multiple file contents, taking the target file content as the configuration information of the target node.

3. The method of claim 2, wherein, The multiple file contents of the pre-configuration file comprise service identifiers of multiple services, method identifiers of multiple methods contained in each service and multiple method parameters of each method; when there is a selection operation for a target service identifier in the service identifiers of the multiple services, displaying the method identifiers of the multiple methods contained in the target service; when there is a selection operation for a method identifier of a target method contained in the target service, displaying the multiple method parameters contained in the target method; when there is a selection operation for a target method parameter in the multiple method parameters contained in the target method, taking the service identifier of the target service, the method identifier of the target method and the target method parameter as the configuration information of the target node, the target node corresponding to the target service. The main interface further comprises a debugging control, and the method further comprises:

4. The method of claim 1, wherein, ​ When the debugging control is selected, the service orchestration file is tested to obtain a test result, the test result including a first unit test result and a second unit test result, the first unit test result being a test result about an execution order of one or more services contained in the service orchestration file, and the second unit test result being a test result about a business execution result of the service orchestration file.

5. The method of claim 1, wherein, Also comprising: Obtaining a service call request, the service call request including a file identifier of the service orchestration file; Executing an executable code file corresponding to the service orchestration file, calling services in an execution order of one or more services contained in the service orchestration file and configuration information of each service in sequence to obtain an execution result of the service call request; Returning the execution result of the service call request to a user terminal corresponding to the service call request.

6. The method of claim 5, wherein, The transmission protocol corresponding to the service call request is a second transmission protocol; The service call request includes: Receiving an original call request sent by the user terminal, the original call request being a request generated based on a first transmission protocol; Converting the original call request into a service call request corresponding to a second transmission protocol, the first transmission protocol and the second transmission protocol being different.

7. A service orchestration apparatus, characterized by, The service orchestration device includes: A display unit configured to display a main interface, the main interface including N nodes, N being a positive integer; The display unit is further configured to display a configuration interface of a target node when there is a configuration operation for the target node, the configuration interface of the target node being configured to obtain configuration information of the target node, the configuration information including a service identifier, a method identifier, and a method parameter corresponding to the target node, the target node corresponding to one service after configuration, and the target node being any node of 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; A processing unit configured to generate a service orchestration file according to the node chain of the N nodes and the configuration information of each node, the service orchestration file being a file described by a markup language across technology stacks, containing an execution order of one or more services and configuration information of each service, the configuration information of each service being determined by the configuration information of a node corresponding to each service; parse the service orchestration file to obtain an executable code file, the executable code file including at least one of an executable code file with a runtime and an executable code file without a runtime, the executable code file without a runtime being obtained from an editable auxiliary executable code file generated according to the service orchestration file; and deploy the executable code file, the deployed executable code file being configured to respond to a service call request of a user terminal.

8. A service orchestration device, characterized by, The service orchestration device includes: a processor adapted to implement one or more instructions; and A computer storage medium storing one or more instructions adapted to be loaded and executed by the processor to perform the service orchestration method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, the computer program comprising program instructions which, when executed by a processor, cause the processor to perform the service orchestration method according to any one of claims 1-6.

Images