CN114816375A - Service arranging method, device, equipment and storage medium - Google Patents
Service arranging method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114816375A CN114816375A CN202110132787.7A CN202110132787A CN114816375A CN 114816375 A CN114816375 A CN 114816375A CN 202110132787 A CN202110132787 A CN 202110132787A CN 114816375 A CN114816375 A CN 114816375A
- Authority
- CN
- China
- Prior art keywords
- service
- file
- node
- target
- target node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
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
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
With the rapid development of digital transformation, the traditional single service can not meet the technical requirements of the current interconnected products, and therefore, service arrangement is in process. The service arrangement means that various services are orderly woven to complete a certain service, the services are aggregated into a specific execution chain, and a user can call one or more micro services at the back end through a call request.
At present, most of service arrangement implementation methods are written by codes, so that development period is long and efficiency is low for developers, and how to efficiently implement development of service arrangement becomes a technical problem to be solved urgently.
Disclosure of Invention
The embodiment of the application provides a service arrangement method, a device, equipment and a storage medium, which can improve the development efficiency of service arrangement for developers.
In one aspect, the present application discloses a service orchestration method, including:
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.
In one aspect, the present application discloses a service orchestration device, which includes:
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.
In one aspect, an embodiment of the present application discloses a service orchestration device, including:
a processor adapted to implement one or more instructions; and a computer storage medium storing one or more instructions adapted to be loaded by the processor and to perform the service orchestration method described above.
In one 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 execute the service orchestration method described above.
An aspect of an embodiment of the present application discloses a computer program product or a computer program, which includes computer instructions 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 executes the computer instructions, so that the service orchestration device performs the service orchestration method described above.
The method comprises the steps of 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. The method has the advantages that the developer can place the nodes on the visual interface in a dragging mode and configure the node information, so that the service arrangement file is obtained, the developer does not need to develop in a code mode, the learning cost is low, the workload of the developer can be reduced, the development time can be saved, and the development efficiency of the developer on the service arrangement is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram of an architecture of a service orchestration system according to an embodiment of the present disclosure;
FIG. 2 is a flow chart illustrating a service orchestration method according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a service orchestration method main interface according to an embodiment of the present disclosure;
FIG. 4 is a schematic illustration of a configuration interface disclosed in an embodiment of the present application;
FIG. 5 is a schematic diagram of a service orchestration connection as disclosed in an embodiment of the present application;
FIG. 6 is a flow chart illustrating another service orchestration method disclosed in embodiments of the present application;
FIG. 7 is a schematic structural diagram of a service orchestration device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a service orchestration device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Before describing the service orchestration method provided by the present application, the technical terms related to the present application are introduced:
1. domain Specific Language (DSL): a programming language designed for a specific domain with limited expressiveness. By defining problem boundaries, thereby locking complexity and increasing programming efficiency, the use of DSL as a declaration of service orchestration provides the following advantages: firstly, the error rate of language expression can be reduced; secondly, developers and even business personnel who are not familiar with how to realize the technology can know the model; third, the specific domain language provides an Application Programming Interface (API) of the specific domain to operate the model, so that the development efficiency can be improved; and fourthly, important business knowledge is provided in the model, and the solution is migrated from one technology to another technology or between different versions of the same technology, so that the migration is relatively easy. This is typically done by modifying the generator or interpreter appropriately. And fifthly, an implementation process comprising a plurality of different technologies can be configured by using the model, so that the technical difficulty and the workload of realizing a solution by using the technologies are reduced. In the present embodiment, DSL uses primarily yaml formatted files to describe service orchestration files. Alternatively, service orchestration files may also be described using files formatted as json, hcl, and the like. Wherein, yaml, json and hcl are all markup languages.
2. Low code (lowcode): a method of visualizing application development 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. The use of lowcode to carry the scheduling configuration of the scheme has the following advantages: firstly, the application is more intuitively constructed, and the visualization method can be used for defining the user logic and floating the experience of different developers for developing the API layer. And secondly, developers can expand the application by using the coded enhanced functions, and related codes can be packaged into a shared module when the codes need to be customized, so that the whole development team is dragged into the applications. And thirdly, automatic testing is built in, active quality monitoring and real-time performance management are performed, and the risk of project development is reduced. And fourthly, fully utilizing the public cloud, and automatically managing the reliability and the expansibility of the application by simple configuration, thereby reducing the maintenance cost and the workload of the infrastructure. And fifthly, fully embodying the concept of devops (general term of process, method and system), automatically constructing the system after completing configuration, and constructing a test and verification branch after deploying money. In the embodiment of the application, the service arrangement file is constructed on the graphical interface in a dragging mode, and a developer does not need to write codes line by line to construct the service arrangement file, so that the development efficiency of a front-end developer is realized.
3. Service orchestration: various capabilities are arranged to complete a certain service, and the various capabilities are orderly woven and aggregated into a specific execution chain. A single call may cause one or more requests for backend services.
4. Js: a JavaScript execution environment based on the ChromeV8 engine. 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: the method comprises the steps of compiling a node.js edition service orchestrator core function, providing micro-service aggregation capability and orchestration capability, enabling a client request to acquire a plurality of back-end micro-service data through one request, and orchestrating a micro-service calling sequence by using a strongly customized orchestration logic. And secondly, providing a DSL analysis engine, and performing chain calling on the back-end micro-service according to certain logic after the DSL description is analyzed. And thirdly, writing a code generator, generating a deployable service code by using a template engine and utilizing an abstract syntax tree, supporting secondary development and further improving the development efficiency. Alternatively, Golang (a static strongly typed compiled language), Java, PHP, Python, etc. languages may be used.
Referring to fig. 1 in conjunction with the above related descriptions, fig. 1 is a schematic structural diagram of a service orchestration system disclosed in an embodiment of the present application, and as shown in fig. 1, an architectural diagram 100 of the service orchestration system includes a user terminal 110, a service orchestration device 120, and a server 130, where the service orchestration device 120 includes a service orchestration front end 121 and a service orchestration server 122, and a communication connection may be performed between the user terminal 110, the service orchestration device 120, and the server 130. Specifically, the user terminal 110 is mainly configured to send a service invocation request to the service orchestration device 120, or directly send a service invocation request to the server 130; the service orchestration device 120 is mainly used to implement the service orchestration method of the present application, and sequentially invokes various services stored in the server 130 in response to a service invocation request, and then returns an execution result to the user terminal 110; compared with the case that the user terminal 110 directly sends the service calling request to the server 130, the service orchestration device in the architecture shown in the present application realizes the service aggregation function, and after the user terminal 110 initiates the service calling request including a plurality of services, the service orchestration device 120 can realize the calling of the services. The server 130 is mainly used for storing services with various functions, and the services also include various micro services.
Based on the service arranging system, the application provides a service arranging method, which comprises the following specific steps:
in a possible implementation manner, the service orchestration method is mainly performed by the service orchestration front-end 121: 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. The method is mainly characterized in that information corresponding to the nodes is configured at the service orchestration front end 121, so that service orchestration is efficiently realized, development of developers in a code mode is not needed, development time can be saved, workload is reduced, and the development concept of the cloud era is better conformed.
In one possible implementation, the service orchestration method is mainly performed by the service orchestration server 122: analyzing the service arrangement file completed by the service arrangement front end 121 to obtain an executable code file, where the executable code file includes an execution sequence of one or more services corresponding to the service arrangement file, and configuration information of each service; deploying an executable code file, wherein the deployed executable code file is used for responding to a service calling request of a user terminal; acquiring a service calling request, wherein the service calling request comprises a file identifier of the service arrangement file; executing an 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. The service orchestration server 122 directly executes the executable code corresponding to the service orchestration file, and finally returns the execution result of the call request without repeating the step of returning according to each service, so that the call times of the user terminal can be effectively reduced, and the network transmission cost of the call interface can be reduced.
In one possible implementation, the user terminal 110 includes, but is not limited to, a handheld device, an in-vehicle device, a wearable device, or a computing device having wireless communication capabilities. Illustratively, the user terminal 110 may be a mobile phone (mobile phone), a tablet computer or a computer with wireless transceiving function. But also 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 smart grid, wireless terminal equipment in smart city (smart city), wireless terminal equipment in smart home (smart home), and the like. The service orchestration server 122 and the server 130 may be independent physical servers, may also be a server cluster or a distributed system formed by a plurality of physical servers, and may also be cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDNs, and big data and artificial intelligence platforms.
Based on the service orchestration system, the present application provides a service orchestration method, as shown in fig. 2, which is a flow diagram of a service orchestration method disclosed in the present application, where the service orchestration method can be executed by a service orchestration front end 121 in a service orchestration setting 120, and the service orchestration method specifically includes the following steps:
s201, displaying a main interface, wherein the main interface comprises N nodes, and N is a positive integer.
The main interface is a visualization interface for configuring nodes corresponding to the service layout file, and the main interface may refer to a method for developing a visualization application, such as a lowcode development interface, through which developers with different experience levels can create Web and mobile applications through a graphical user interface using drag-and-drop components and model-driven logic. In the embodiment of the application, the main interface is an interface for realizing service arrangement in a dragging mode, and developers can select different types of nodes according to requirements and place the nodes in the main interface, so that the learning cost and the learning burden of the developers can be reduced.
In one possible implementation, when the service orchestration is needed, the developer clicks the main interface on the service orchestration front end, so that the main interface is displayed. The main interface comprises an adding control, a developer can add nodes through the adding control, the developer can select the node type of each node, and after the developer adds the nodes, the displayed main interface comprises the nodes which are clicked by the user. The node types are divided according to the functions of the corresponding services of the node, for example, the functions of the services may be a database (such as functions of adding, deleting, changing and the like), a redis, or even various application services (such as WeChat), and the node types may also be divided according to the transmission protocol of the corresponding services of the node. Specifically, the service may be a currently popular micro service, and for example, a supermarket on the internet may have a plurality of services, such as user management, commodity management, and order management, where each management corresponds to one micro service, and may also be understood as one function corresponding to one micro service.
For example, as shown in fig. 3, the main interface is a schematic diagram of a main interface of a service orchestration method disclosed in this embodiment of the present application, where the interface has an "add" control 301, and a developer clicks the "add" control 301 to display an interface 302, and the developer can perform an input operation of a node type in the interface 302 according to a service that the developer wants to select, and when the node type is determined, a node similar to node 1 is obtained, and it can be seen that, in the main interface shown in fig. 3, three nodes are displayed, that is, N is 3. Optionally, the main interface further includes a "view" control, and after the information of each node is configured, the developer may 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 is obtained.
S202, when configuration operation aiming at the 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 one service, and the target node is any node in the N nodes.
The main interface is provided with nodes dragged by a developer, each node corresponds to a node type, the node types of several nodes are possibly the same, different nodes correspond to different node types, and the specific requirements are related to services required to be called when the developer configures. If the calling service is implemented based on the rpc protocol, the corresponding node type may be the rpc type, where 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 may obtain a pre-configuration file corresponding to the node type of the target node, and then display a configuration interface of the target node on the main interface, where the configuration interface of the target node includes a plurality of file contents of the pre-configuration file, and when there is a selection operation for the target file content, use the target file content as configuration information of the target node, where the target file content is also in the plurality of file contents of the pre-configuration file. Optionally, the configuration interface of the target node may be displayed at any position of the main interface. Wherein, the target node is any one of the N nodes, for example, any one of the three nodes shown in fig. 3; the configuration operation may specifically be that a developer clicks on a target node. The preconfigured file is related to a node type, for example, a node of a trpc protocol type, the corresponding preconfigured file is "north star configuration" (the name is customized and is used for distinguishing different configurations), and the preconfigured file corresponding to the active protocol type node is "l 5 configuration".
For example, fig. 4 is a schematic view of a configuration interface of a target node disclosed in the application embodiment, and the 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 preconfigured file include service identifiers of multiple services, method identifiers of multiple methods included in each service, and multiple method parameters of each method, where one service may have multiple methods, and the method parameters corresponding to each method are different, and when configuration operation for the target node exists, a configuration interface of the target node is displayed (specifically how to configure the target node), including: when there is a selection operation for a service identifier of a target service, displaying a method identifier list of a plurality of methods contained by the target service; displaying a plurality of method parameter lists of the target method when there is a selection operation for a method identification of the target method; when the selection operation aiming at the target method parameter exists, the service identifier of the target service, the method identifier of the target method and the target method parameter are all used as the configuration information of the target node, and the target node corresponds to the target service. Each service corresponds to a service identifier, and a service identifier may correspond to a service name.
For example, as shown in fig. 4, the configuration interface diagram of a target node disclosed in the application embodiment may be specifically shown, where 401 is a configuration interface of a node 1, and the interface includes service pb file setting (a pb file is a binary file representing a model structure and does not have source code), service route setting, and namespace setting, where the service route may be obtained by parsing the service pb file, and the namespace corresponds to a node type, and a developer may dynamically select the namespace. In fig. 4, the configuration interface further includes service name setting, method name setting, and method parameter setting, and because 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 displayed to the developer in a drop-down box form for selection, and the displayed service name, the method name, and the method parameter are all obtained according to a pre-configuration file corresponding to the node type. When the service name of the target service is selected, the drop-down box of the method name comprises the method name of the method contained by the target service, namely 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 a parameter associated with the selected method name.
S203, 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.
In a possible implementation manner, through steps S201 to S202, N configured nodes may be obtained, and when there is a connection operation for the N nodes, a node chain including the N nodes is displayed, that is, a developer connects the N nodes together through a connection line to obtain a connected node chain, where the node chain may be a directed acyclic graph, specifically: the node can be a single node or a plurality of nodes, and the plurality of nodes can flow from the node a to the node b and then from the node b to the node c; the flow may be from node a to node b, from node b to node c, and from node b to node d.
Specifically, as shown in fig. 5, the method is a schematic diagram of a service orchestration connection manner disclosed in an embodiment of the present application, and it can be seen that 501 in fig. 2 is a connection manner of a node chain, and 502 is another connection manner of a node chain.
In a possible implementation manner, after the developer connects the configured N nodes, when the developer clicks the debug control on the main interface, a service layout file is correspondingly generated, where the generated service layout file is a file in a markup language, such as the aforementioned file in the yaml format, the file in the json format, and the file in the hcl format. Meanwhile, the test result of the node chain (i.e. the service arrangement file) is displayed on the interface. The service arrangement file also comprises configuration information of each service, and the configuration information of each service is determined by the configuration information of a 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 regarding an 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 a test result regarding a service execution result of the service orchestration file. Specifically, the first unit test result is used to detect whether the execution sequence of the plurality of services in the service layout file is the same as a preset execution sequence, if so, the sequence is proved to be unproblematic, otherwise, if an error is reported, a developer needs to adjust the sequence, and the sequence can be directly modified in the main interface in a dragging manner. The second unit test result is used for detecting whether the service execution result of the service arrangement is the same as the preset one, if so, the service arrangement is proved to be successful, otherwise, if an error is reported, developers need to adjust each node used by the service arrangement file. Optionally, the test result further includes a third unit test result, where the third unit test result is a service execution result of each node corresponding to the service orchestration file, and can detect whether the service configured by each node can be successfully executed, and if the service configured by each node cannot be successfully executed, the front-end developer changes the configuration information of the node.
In summary, the work of the service orchestration front end 121 can be summarized as: firstly, a developer drags a required number of nodes on a visual interface (such as the aforementioned lowcode development interface), and configures the configuration (configured in the configuration interface shown in fig. 4) of each node according to a pre-configuration file, where the configured information includes a service name, a method name, and a method parameter; secondly, arranging all nodes according to a certain sequence on a visual interface by a developer, for example, the first node is a configured node A, the second node is a configured node C, the last node is a configured node B, connecting the three nodes, clicking and storing to obtain a workflow (corresponding to the node chain) and a corresponding workflow id (service arrangement file identifier), wherein the id can be used for calling parameters when a workflow interface is executed; the third step: and in a debugging interface provided by the platform, the obtained workflow id is used to obtain the service arrangement file to obtain aggregated data and a test result.
In a possible implementation manner, the service arrangement file corresponding to the node chain generated in the main interface may be used to directly implement the call of the service arrangement file, for the service arrangement file, there is a corresponding trigger action, and the trigger action may receive a service call request initiated by a user terminal, and then directly return an execution result of the service arrangement file to the user, and the trigger action may also be triggered by a developer, and may also obtain an execution result of the service arrangement file. This case corresponds to Platform as a Service (PaaS), which means. It will be appreciated that the user need only invoke the platform for developing this service orchestration to obtain the results of the execution of the service invocation request.
In the implementation of the application, a main interface is displayed, 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. The method mainly comprises the steps that a developer drags and drops nodes in a visual interface of the service arrangement front end 121 and performs row configuration of node information, so that service arrangement is efficiently realized, the developer does not need to develop in a code mode, development time can be saved, workload can be reduced, and the development concept of the cloud era is better conformed.
Based on the service orchestration system and the service orchestration method, the present application provides another service orchestration method, as shown in fig. 6, which is a flowchart of another service orchestration method disclosed in the present application, where the service orchestration method may be executed by a service orchestration server 122 in a service orchestration setting 120, and the service orchestration method specifically may include the following steps:
s601, analyzing the service arrangement file, and generating 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.
In one possible implementation, after configuring each node corresponding to the service orchestration file 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 DSL (Domain Specific Language), and specifically may be a file in yaml format, and may also be 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.
Further, a registered node interface included in the service orchestration server receives a service orchestration file sent by the service orchestration front end and configuration information of each node, the received service orchestration file includes an execution sequence of one or more services, and an interface included in the service orchestration server learns that the node information analyzes the service orchestration file to generate an executable code file, and the executable code file is packaged into a workflow interface. 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. The executable code file generated by parsing can be divided into two types, wherein one type is called executable code file with runtime, and the other type is called executable code file without runtime.
The generation process of the executable code file with the runtime comprises the following steps: the analyzer directly and automatically generates an executable code file according to the service arrangement file. The executable code file with the 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 the runtime is as follows: the analyzer automatically generates an auxiliary executable code file according to the service layout file, and developers manually edit the auxiliary executable code file to obtain an executable code file without a runtime. The executable code file without the operation has stronger autonomy for developers, and the developers can carry out custom writing according to requirements.
Optionally, the service orchestration server may further convert the service orchestration file into any executable code file suitable for the development platform, such as Node and Golang languages, which may better fit the language usage habits and performances of the front-end developers, and may further include compiled languages such as Java, PHP, Python, and the like.
S602, deploying the executable code file, wherein the deployed executable code file is used for responding to a service calling request of the user terminal.
In a possible implementation manner, the service orchestration server may also deploy the parsed executable code file, which is intended to respond to a service invocation request initiated by the user terminal. Each deployed executable code file and service orchestration file have a corresponding relationship, which may be identified for differentiation. For example, a service orchestration file corresponds to an id, each id corresponding to an executable code file. Specifically, as shown in table one, 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.
Watch 1
File identification for service orchestration files | Executable code file identification |
id=1 | Document 1 |
…… | …… |
id=1 | File N |
Alternatively, the executable code file may be deployed by a developer, or by a user terminal in the case where the user understands the logic of the service orchestration. It is not limited 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, and can also be deployed to deployment platforms in various enterprises.
S603, obtaining a service calling request, wherein the service calling request comprises a file identifier of the service arrangement file.
In a possible implementation manner, after the user terminal initiates a service invocation request, the service orchestration server may obtain the service invocation request correspondingly, so as to rapidly implement the invocation of the service by the service orchestration server, and return an execution result to the user terminal. The service calling request includes a file identifier of the service arrangement file, such as identification information shown in table one, for example, id ═ 1.
In a possible implementation manner, after receiving the service invocation request, the service orchestration server further involves conversion of a network transport protocol, which may be specifically interpreted as: firstly, the service arranging server receives an original calling request sent by a user terminal, the original calling request is a request generated based on a first transmission protocol, and the service arranging server can analyze a calling request of a second transmission protocol.
For example, the original call request sent by the user terminal is a request generated based on a first transmission Protocol, if the first transmission Protocol is a Hypertext Transfer Protocol (HTTP), and the service orchestration server can parse the call request of a second transmission Protocol, if the second transmission Protocol is a TRPC Protocol, the HTTP Protocol needs to be converted into the TRPC Protocol, and when the service orchestration server returns the execution result to the user terminal, the TRPC Protocol also needs to be converted into the HTTP Protocol, so that the user terminal can receive the execution result. Wherein the TRPC protocol is generated based on the RPC protocol.
S604, 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.
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 by the service invocation request, the execution workflow interface included in the service orchestration server may 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 calls the services according to the execution sequence of one or more services included in the service arrangement file and the configuration information of each service, that is, executes the executable code file corresponding to the service arrangement file to obtain the execution result of the service call request. The service aggregation is realized by calling the workflow interface, and the network transmission cost of calling different interfaces for multiple times by the user terminal can be effectively reduced.
And S605, returning the execution result of the service calling request to the user terminal corresponding to the service calling request.
In a possible implementation manner, after obtaining the execution result of the service invocation request, the service orchestration server returns the execution result to the user terminal, so as to meet the invocation demand of the user on the service.
In a possible implementation manner, the execution result of the service invocation request may be returned to the user terminal through the execution interface.
Optionally, the service orchestration server further provides a self-defined plug-in mechanism, which supports developers to define extension logic, and front-end developers can write the self-defined logic into the service orchestration server according to plug-in rules to extend orchestration capability. Specifically, the service orchestration server may make a front-end developer write custom logic very easily by relying on an injection and lifecycle hook through a Plug-in (Plug-in, addin, add-in, addon, or add-on) Plug-in mechanism, and may understand the Plug-in mechanism into another Plug-in interface, for example, a developer may customize a code having a "log" or "monitoring" function, an execution time is defined in the code, and the section of code is encapsulated into the Plug-in interface, and then the workflow interface is invoked to execute the executable code encapsulated by the workflow interface, and concurrently execute the custom code encapsulated by the Plug-in interface, so that the invocation of the service may be simultaneously realized, and the recording of the execution log in the process may also be realized.
In a possible implementation manner, the developer may also pull other types of nodes, such as a web hook node, a graph ql node, a merge node, and the like, in the main interface, and the developer may implement functions different from the service orchestration by configuring the nodes, that is, each node does not correspond to one service. The web hook node is an API concept, is one of the use paradigms of the micro service API, and is also called as a reverse API, namely the front end does not actively send a request and is completely pushed by the back end; the graph ql node is a declarative data acquisition specification and query language for the API, and a user can query an execution result by calling the node; the popular understanding of the merge node is a synthetic node, and in the process of aggregating data, one synthetic node is needed to realize aggregation.
According to the above embodiments, in a possible implementation method, on the basis of implementing the service orchestration method of the present application, different functions may be implemented by calling interfaces corresponding to different nodes, for example, by calling an interface corresponding to a web hook node to implement Continuous Integration (CI)/Continuous Deployment (CD)). The "CI" in CI/CD belongs to the developer's automation process. Successful CI means that new changes to the application code are built, tested, and incorporated into the shared repository on a regular basis, with "CD" in CI/CD referring to continuous delivery and/or continuous deployment. For another example, the MOCK test can be implemented by using a JSON node, where JSON (JavaScript Object notification, JS) is a lightweight data exchange format, that is, data transferred by JSON is used to simulate and implement the MOCK test, and the MOCK test is a test method created by using a virtual Object (MOCK Object) to test some complex objects (e.g., ResultSet Object in JDBC) that are not easy to construct (e.g., http request must be constructed in Servlet container) or not easy to obtain during the test process; for another example, the low-code configuration activity page may be implemented by an active configuration node, that is, an active configuration node is configured, and a visual interface (that is, the low-code configuration activity page) may be obtained by invoking the active configuration node.
In the embodiment of the application, the service arrangement server analyzes the service arrangement file to obtain an executable code file, wherein the executable code file comprises the execution sequence of one or more services corresponding to the service arrangement file and the configuration information of each service; deploying the executable code file, wherein the deployed executable code file is used for responding to a service calling request of a user terminal; acquiring a service calling request, wherein the service calling request comprises a file identifier of a service arrangement file; executing an 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. The service arrangement server directly executes the executable codes corresponding to the service arrangement files, the step of returning is not required to be repeatedly called according to each service, and the execution result of the calling request is finally returned, so that the calling times of the user terminal can be effectively reduced, and the network transmission cost of the calling interface is reduced.
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 existing services on the visual interface by means of DSL (i.e., construct a service orchestration file in a drag-and-drop manner on the visual interface) without affecting the existing services, so that a back-end developer can concentrate on management and development of the services, and comply with the cloud era development concept; the service arrangement method constructs the service arrangement file in a drag-and-drop mode, and developers do not need to exchange codes for development, so that the learning cost and mental burden of the users are reduced, the development efficiency of the developers can be improved, the engineering labor input in product development is reduced, and the possibility is provided for subsequent platform productization; the service arranging method can debug the service arranging file on the visual interface without testing in the API gateway layer in sequence, so that the workload is greatly reduced, the testing is easier, and the data security is easier to ensure; the service arranging method can realize service aggregation by packaging the executable code, and the user terminal can obtain the execution result of the calling request only by calling one interface when calling a plurality of services, thereby effectively reducing the network transmission cost of calling the interface for a plurality of times by the client.
Based on the service orchestration system and the service orchestration method, an embodiment of the present application discloses a service orchestration device, as shown in fig. 7, which is a schematic diagram of a structure of the service orchestration device disclosed in the embodiment of the present application, and the service orchestration device 70 shown in fig. 7 may run the following units:
a display unit 701, configured to display a main interface, where the main interface includes N nodes, and N is a positive integer;
the display unit 701 is further configured to display a configuration interface of the target node when a 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 701 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 sequence of one or more services.
In one possible implementation, each node corresponds to a node type, which is divided according to the functions of the corresponding service of the node; when the configuration operation for the target node exists, displaying a configuration interface of the target node by a unit, wherein the configuration interface comprises:
a transceiving unit 702, configured to, when there is a configuration operation for the target node, obtain a pre-configuration file corresponding to a node type of the target node;
the display unit 701 is further configured to display a configuration interface of the target node according to the preconfigured file, where the configuration interface of the target node includes a plurality of file contents of the preconfigured file;
a determining unit 703, configured to use, when there is a selection operation for a target file content of the plurality of file contents, the target file content as configuration information of the target node.
In one possible implementation manner, the plurality of file contents of the pre-configured file include 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:
a display unit 701 configured to display method identifiers of a plurality of methods included in a target service when there is a selection operation for a service identifier of the target service among the service identifiers of the plurality of services;
the display unit 701 is further configured to display a plurality of method parameters included in a target method when there is a selection operation for a 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 a target method parameter in a plurality of method parameters included in the target method, use 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.
In one possible implementation, the service orchestration file is a file of a markup language; a processing unit 704 configured to:
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.
In a possible implementation manner, the processing unit 704 is configured to, when the debug control is selected, test the service layout file to obtain a test result, where the test result includes a first unit test result and a second unit test result, the first unit test result is a test result regarding an execution sequence of one or more services included in the service layout file, and the second unit test result is a test result regarding a service execution result of the service layout file.
In a possible implementation manner, the transceiver 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 arrangement file, and sequentially calls the services 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;
the transceiving unit 702 is configured to return an execution result of the service invocation request to the user terminal corresponding to the service invocation request.
In one possible implementation manner, the transmission protocol corresponding to the service invocation request is a second transmission protocol; the acquiring the service call request includes:
the transceiver 702 is configured to receive an original invocation request sent by the user terminal, where the original invocation 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 is different from the second transmission protocol.
According to an embodiment of the present application, the steps involved in the service orchestration methods shown in fig. 2 and 6 may be performed by the units in the service orchestration device 70 shown in fig. 7. For example, steps S201 to S203 in the service orchestration method shown in fig. 2 may be performed by the display unit 701 in the service orchestration device 70 shown in fig. 7; for another example, steps S601 to S602 and S604 in the service arranging method shown in fig. 6 may be executed by the processing unit 704 in the service arranging apparatus 70 shown in fig. 7, and steps S603 and S605 may be executed by the transceiver unit 702 in the service arranging apparatus 70 shown in fig. 7.
According to another embodiment of the present application, the units in the service orchestration device 70 shown in fig. 7 may be respectively or entirely combined into one or several other units to form one or several other units, or some unit(s) may be further split into multiple units with smaller functions to form the same operation, without affecting the achievement of the technical effect of the embodiments of the present application. The units are divided based on logic functions, and in practical application, the functions of one unit can be realized by a plurality of units, or the functions of a plurality of units can be realized by one unit. In other embodiments of the present application, the service orchestration device 70 may also include other units, and in practical applications, these functions may also be implemented by assistance of other units, and may be implemented by cooperation of multiple units.
According to another embodiment of the present application, the service orchestration apparatus 70 as shown in fig. 7 may be constructed by running a computer program (including program codes) capable of executing the steps involved in the respective methods shown in fig. 2 and fig. 6 on a general-purpose computing device, such as a computer, including a processing element and a storage element, such as a Central Processing Unit (CPU), a random access storage medium (RAM), a read-only storage medium (ROM), and the like, and implementing the service orchestration method according to the embodiments of the present application. The computer program may be embodied on a computer-readable storage medium, for example, and loaded into and executed by the above-described computing apparatus via the computer-readable storage medium.
In the implementation of the application, a main interface is displayed, 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. The method mainly comprises the steps that developers drag and drop nodes in a visual interface of the service arrangement front end 121 and perform row configuration of node information, so that service arrangement is efficiently achieved, the developers do not need to develop in a code mode, development time can be saved, workload is reduced, and the development concept of the cloud era is better conformed.
Based on the method and the device embodiment, the embodiment of the application provides a service arranging device. Referring to fig. 8, a schematic structural diagram of a service orchestration device according to an embodiment of the present application is provided. The service orchestration device 80 shown in fig. 8 comprises 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 may be connected by a bus or other means.
A computer storage medium 804 may be stored in the memory 805 of the service orchestration device 80, the computer storage medium 804 being for storing a computer program comprising program instructions, the processor 801 being for executing the program instructions stored by the computer storage medium 804. Processor 801 (or CPU) is a computing core and a control core of service orchestration device 80, and is adapted to implement one or more instructions, and in particular to load and execute one or more computer instructions to implement corresponding method flows or corresponding functions.
An embodiment of the present application further provides a computer storage medium (Memory), which is a Memory device in the service orchestration device 80 and is used to store programs and data. It is understood that the computer storage medium herein may include both a built-in storage medium in service orchestration device 80 and, of course, an extended storage medium supported by service orchestration device 80. The computer storage medium provides a storage space that stores the operating system of service orchestration device 80. Also stored in this memory space are one or more instructions, which may be one or more computer programs (including program code), suitable for loading and execution by processor 801. The computer storage medium may be a high-speed RAM memory, or may be a non-volatile memory (non-volatile memory), such as at least one disk memory; and optionally at least one computer storage medium located remotely from the processor.
In one embodiment, the computer storage medium may be loaded with one or more instructions and executed by processor 801 to implement the corresponding steps of the service orchestration method described above with respect to fig. 2 and 6. In particular implementations, one or more instructions in the computer storage medium are loaded and executed by the processor 801 to perform the steps of:
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.
In one possible implementation, each node corresponds to a node type, which is divided according to the functions of the corresponding service of the node; when there is a configuration operation for a target node, the processor 801 displays a configuration interface of the target node, for:
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.
In one possible implementation manner, the plurality of file contents of the pre-configured file include 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, the processor 801 regards 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.
In one possible implementation, the service orchestration file is a file of a markup language; the processor 801 is further configured to:
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.
In one possible implementation manner, the processor 801 is further configured to:
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.
In one possible implementation manner, the processor 801 is further configured to:
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.
In one possible implementation manner, the transmission protocol corresponding to the service invocation request is a second transmission protocol; the processor 801 obtains a service invocation request, including:
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.
In the implementation of the application, a main interface is displayed, 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. The method mainly comprises the steps that developers drag and drop nodes in a visual interface of the service arrangement front end 121 and perform row configuration of node information, so that service arrangement is efficiently achieved, the developers do not need to develop in a code mode, development time can be saved, workload is reduced, and the development concept of the cloud era is better conformed.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall 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.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110132787.7A CN114816375A (en) | 2021-01-29 | 2021-01-29 | Service arranging method, device, equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110132787.7A CN114816375A (en) | 2021-01-29 | 2021-01-29 | Service arranging method, device, equipment and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN114816375A true CN114816375A (en) | 2022-07-29 |
Family
ID=82526458
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110132787.7A Pending CN114816375A (en) | 2021-01-29 | 2021-01-29 | Service arranging method, device, equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114816375A (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115145560A (en) * | 2022-09-06 | 2022-10-04 | 北京国电通网络技术有限公司 | Business orchestration method, device, equipment, computer readable medium and program product |
CN115412606A (en) * | 2022-08-31 | 2022-11-29 | 上海得帆信息技术有限公司 | iPaaS service arranging method and system based on open source mule integrated platform |
CN115550425A (en) * | 2022-09-21 | 2022-12-30 | 中国电子科技集团公司第二十八研究所 | Business process arrangement method facing microservice |
CN118502992A (en) * | 2024-07-22 | 2024-08-16 | 国网信息通信产业集团有限公司 | Service arrangement method and related equipment |
-
2021
- 2021-01-29 CN CN202110132787.7A patent/CN114816375A/en active Pending
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115412606A (en) * | 2022-08-31 | 2022-11-29 | 上海得帆信息技术有限公司 | iPaaS service arranging method and system based on open source mule integrated platform |
CN115412606B (en) * | 2022-08-31 | 2024-01-23 | 上海得帆信息技术有限公司 | iPaaS service arrangement method and system based on open source mule integration platform |
CN115145560A (en) * | 2022-09-06 | 2022-10-04 | 北京国电通网络技术有限公司 | Business orchestration method, device, equipment, computer readable medium and program product |
CN115550425A (en) * | 2022-09-21 | 2022-12-30 | 中国电子科技集团公司第二十八研究所 | Business process arrangement method facing microservice |
CN115550425B (en) * | 2022-09-21 | 2024-08-09 | 中国电子科技集团公司第二十八研究所 | Business process arrangement method for micro-service |
CN118502992A (en) * | 2024-07-22 | 2024-08-16 | 国网信息通信产业集团有限公司 | Service arrangement method and related equipment |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110321152B (en) | Software development platform | |
CN114816375A (en) | Service arranging method, device, equipment and storage medium | |
US8959477B2 (en) | Scripting language for business applications | |
US8019860B2 (en) | Service accounting method and apparatus for composite service | |
US20100153150A1 (en) | Software for business adaptation catalog modeling | |
CN117008923B (en) | Code generation and compiling deployment method, platform and equipment based on AI large model | |
US20100153149A1 (en) | Software for model-based configuration constraint generation | |
US20130091491A1 (en) | Self-Documentation of Development Systems | |
US8645913B2 (en) | Web-service based generation of business objects | |
US11003835B2 (en) | System and method to convert a webpage built on a legacy framework to a webpage compatible with a target framework | |
US10089084B2 (en) | System and method for reusing JavaScript code available in a SOA middleware environment from a process defined by a process execution language | |
US11763217B2 (en) | Dynamic feature loading | |
Rattanapoka et al. | An MQTT-based IoT cloud platform with flow design by Node-RED | |
Bergmayr et al. | Cloud modeling languages by example | |
Gómez et al. | A model-based approach for developing event-driven architectures with AsyncAPI | |
CN116414370A (en) | Platform construction method and device based on low codes, medium and electronic equipment | |
Pedratscher et al. | M2FaaS: Transparent and fault tolerant FaaSification of Node. js monolith code blocks | |
US10223143B2 (en) | System and method for supporting javascript as an expression language in a process defined by a process execution language for execution in a SOA middleware environment | |
Affonso et al. | A reference architecture to support the development of mobile applications based on self-adaptive services | |
US10268496B2 (en) | System and method for supporting object notation variables in a process defined by a process execution language for execution in a SOA middleware environment | |
Indamutsa et al. | MDEForgeWL: Towards cloud-based discovery and composition of model management services | |
CN115567526A (en) | Data monitoring method, device, equipment and medium | |
US10223142B2 (en) | System and method for supporting javascript activities in a process defined by a process execution language for execution in a SOA middleware environment | |
Alshuqayran | Static microservice architecture recovery using model-driven engineering | |
Jansen | Exploring interactive application landscape visualizations based on low-code automation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |