CN113238844A - Service arrangement execution path playback method - Google Patents
Service arrangement execution path playback method Download PDFInfo
- Publication number
- CN113238844A CN113238844A CN202110533518.1A CN202110533518A CN113238844A CN 113238844 A CN113238844 A CN 113238844A CN 202110533518 A CN202110533518 A CN 202110533518A CN 113238844 A CN113238844 A CN 113238844A
- Authority
- CN
- China
- Prior art keywords
- service
- component
- arrangement
- trace data
- execution path
- 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
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000009877 rendering Methods 0.000 claims description 9
- 238000012827 research and development Methods 0.000 abstract description 4
- 238000012545 processing Methods 0.000 abstract description 3
- 238000013024 troubleshooting Methods 0.000 abstract 1
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000000712 assembly Effects 0.000 description 2
- 238000000429 assembly Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
- G06F16/9027—Trees
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/904—Browsing; Visualisation therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/544—Buffers; Shared memory; Pipes
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a service arrangement execution path echoing method, which comprises the following steps: the Web end generates service arrangement according to the arrangement operation of the user; the service layout comprises a workflow Id, a version and at least three components corresponding to the workflow Id; the workflow server side executes service arrangement to obtain trace data; the trace data comprises an executed Id corresponding to the trace data and at least three component IDs, and each component ID corresponds to each executed component; after the message consumption service end consumes the trace data, writing the consumed trace data into the ES; the Web terminal queries the ES according to the executed Id to acquire trace data; and the Web end renders an execution path of the service layout according to trace data, workflowId and version. The method and the device for processing the service layout can render the execution path of the service layout, so that a user can easily determine a specific error link through the rendered execution path, the efficiency of problem troubleshooting is improved, the research and development period is shortened, and the service layout is easy to manage. In addition, the method and the device for correcting the service arrangement ensure the correctness and rationality of the service arrangement through the rendered execution path.
Description
Technical Field
The invention relates to the technical field of service arrangement, in particular to a service arrangement execution path echoing method.
Background
The service arrangement means that a plurality of micro services can be called in sequence through one request, the returned result of each service is subjected to data processing, and finally the result is integrated into a large result and returned to the front end.
The service arrangement of the related technology only feeds back result data, and when an execution process of the service arrangement is wrong, a business party and a plurality of service providers are required to perform joint debugging test and communication coordination to determine a problem node, so that the related technology has the defects of low efficiency of problem checking and long research and development period. In addition, a clear responsibility relation is not established between a business party and a service provider in the related art, and when an execution process of service arrangement is wrong, the responsibility party cannot be judged, so that the management of the service is influenced.
Disclosure of Invention
In view of the above, in order to solve the problems in the related art to some extent, the present application provides a service orchestration execution path display method.
The invention adopts the following technical scheme: a service orchestration execution path echoing method, comprising:
the Web end generates service arrangement according to the arrangement operation of the user; the service layout comprises a workflow Id, a version and at least three components corresponding to the service layout;
the workflow server side executes the service arrangement to obtain trace data; the trace data comprises an executed Id corresponding to the trace data and at least three component IDs, and each component ID corresponds to each executed component;
after the message consumption service end consumes the trace data, writing the consumed trace data into an ES;
the Web terminal queries the ES according to the executed Id to acquire trace data;
and rendering the execution path of the service arrangement by the Web end according to the trace data, the workflow Id and the version.
Further, the service orchestration includes the following six components:
a Start component, a dubbo component, an http component, a return component, an event component, and an end component;
the Start component is used to mark the Start of execution of the service orchestration;
the dubbo component is used for storing basic service information; the basic service information is used for supporting the workflow server to acquire the data of the service arrangement;
the http component is used for storing http service information; the http service information is used for supporting the workflow server to acquire the data of the service arrangement;
the return component is used for stipulating a format of result return so that the workflow server side returns data in a corresponding format to the Web side according to the format;
the event component is used for storing information required by the message sending;
the end component is used for marking the service orchestration execution end.
Further, a straight line with an arrow is arranged between every two assemblies; the straight line with arrows is used for ensuring the execution sequence of each component in the service arrangement.
Further, when the component at least corresponds to two straight lines with arrows, judging conditions are set on the straight lines with arrows; the judgment condition is used for ensuring that only one straight line with an arrow corresponding to each component can pass through.
Further, the Web end comprises a front end and a background server;
the Web end generates service arrangement according to the arrangement operation of the user, and the service arrangement comprises the following steps:
the front end generates original service arrangement according to arrangement operation of a user;
the front end converts the original service arrangement into json data;
the front end sends the json data to the background server;
the backstage server converts the json data into new json data to obtain the service arrangement; and the new json data is used for supporting the workflow server side to analyze the service arrangement.
Further, after the Web end generates service orchestration according to the orchestration operation of the user, the method further includes:
and saving the service arrangement.
Further, the workflow server executes the service orchestration to obtain trace data, including:
the workflow server side analyzes the service arrangement to obtain information of each component;
the workflow server side stores the component information into a tree structure according to the sequence arranged by the user; the tree structure comprises a plurality of nodes, and the nodes are in one-to-one correspondence with the components and used for representing the corresponding components;
and executing all nodes to be executed in the tree structure by the workflow server to obtain the trace data.
Further, rendering, by the Web end, an execution path of the service layout according to the trace data, the workflow Id, and the version, including:
the Web end obtains the component ID according to the trace data;
the Web end obtains the json data according to the workflow Id and the version;
and rendering the execution path of the service arrangement by the Web terminal according to the component ID and the json data.
Further, the service orchestration execution path redisplaying method of the present application further includes:
and rendering time-consuming duration corresponding to each component of the service arrangement by the Web end according to the trace data, the workflow Id and the version.
By adopting the technical scheme, the Web end generates service arrangement according to the arrangement operation of the user; the service layout comprises a workflow Id, a version and at least three components corresponding to the workflow Id; the workflow server side executes service arrangement to obtain trace data; the trace data comprises an executed Id corresponding to the trace data and at least three component IDs, and each component ID corresponds to each executed component; after the message consumption service end consumes the trace data, writing the consumed trace data into the ES; the Web terminal queries the ES according to the executed Id to acquire trace data; and the Web end renders an execution path of the service arrangement according to trace data, the workflow Id and the version. Based on the method, the execution path of the service arrangement is rendered, when an execution process of the service arrangement is wrong, a user can easily determine a specific error link through the rendered execution path, the problem of the service arrangement provided by any party is determined, the problem checking efficiency is improved, the research and development period is shortened, and the service arrangement is easy to control. In addition, the execution path of the service arrangement can be rendered to correct the service arrangement, and the correctness and the rationality of the service arrangement are guaranteed.
Drawings
In order to more clearly illustrate the embodiments of the present invention 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 invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart illustrating a method for displaying a service orchestration execution path according to an embodiment of the present invention.
Fig. 2 is a schematic structural diagram of a service orchestration according to an embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a tree structure according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without any inventive step, are within the scope of the present invention.
Fig. 1 is a flowchart illustrating a method for displaying a service orchestration execution path according to an embodiment of the present invention. As shown in fig. 1, the method for displaying back a service orchestration execution path according to the embodiment of the present application includes:
s1, the Web end generates service arrangement according to the arrangement operation of the user; the service orchestration includes a workflow Id, version, and at least three components corresponding thereto.
Specifically, each service layout which is well laid out corresponds to a unique identifier (workflow Id) and a version number (version), and when the workflow ids corresponding to more than two service layouts are the same, the two service layouts are distinguished by adding 1 to the version. For example, when the workflow ids corresponding to the three service orchestrations are the same, version plus 1 may be performed according to the orchestration sequence, specifically: the version corresponding to the first arranged service arrangement is inconvenient, the version of the second arranged service arrangement is added with 1, and the version of the third arranged service arrangement is added with 2. This allows the system to more quickly determine the service choreography to be sought.
Based on the basic composition structure of the service choreography, each service choreography comprises a Start component and at least one return component and at least one end component.
S2, executing service arrangement by the workflow server to obtain trace data; the trace data includes an executed Id corresponding thereto and at least three component IDs, each corresponding to each executed component.
In detail, each time a workflow server uses a component, a corresponding component ID is generated, so that the system can determine all executed components according to the component ID, and thus determine the execution path of the service arrangement.
In addition, before the workflow server executes the service arrangement, an executed Id corresponding to the service arrangement is generated, and in the subsequent execution process, after the workflow server does not execute a component to acquire corresponding data, the acquired data with the executed Id and some machine information are written into Kafka, so that the same set of trace data is used for the executed Id, and the system can quickly determine the trace data to be searched according to the executed Id.
It should be noted that, because the volume of trace data generated by the workflow server per second is very large, and Kafka is a high-throughput distributed subscription and publication system, the workflow server writes trace data into Kafka, which can buffer trace data and is beneficial to system stability.
And S3, after consuming the trace data by the message consumption server, writing the consumed trace data into the ES.
Specifically, the workflow server writes trace data into Kafka as a buffer, then the message consumption server consumes the trace data, and writes the consumed trace data into elasticsearch (es).
The elastic search is a distributed multi-expansion high-real-time search and data analysis engine, and the trace data is stored in the elastic search, so that performance guarantee is provided for the system to acquire the trace data.
And S4, the Web terminal queries the ES according to the executed Id to acquire trace data.
And S5, rendering the execution path of the service layout by the Web end according to trace data, workflow Id and version.
In detail, the Web terminal queries the ES according to the executed Id, determines a component ID according to the trace data after acquiring the trace data, acquires a corresponding service layout from a preset database for storing the service layout according to the workflow Id and version, and finally renders an execution path of the service layout according to the component ID.
By adopting the technical scheme, the Web end generates service arrangement according to the arrangement operation of the user; the service layout comprises a workflow Id, a version and at least three components corresponding to the workflow Id; the workflow server side executes service arrangement to obtain trace data; the trace data comprises an executed Id corresponding to the trace data and at least three component IDs, and each component ID corresponds to each executed component; after the message consumption service end consumes the trace data, writing the consumed trace data into the ES; the Web terminal queries the ES according to the executed Id to acquire trace data; and the Web end renders an execution path of the service arrangement according to trace data, the workflow Id and the version. Based on the method, the execution path of the service arrangement is rendered, when an execution process of the service arrangement is wrong, a user can easily determine a specific error link through the rendered execution path, the problem of the service arrangement provided by any party is determined, the problem checking efficiency is improved, the research and development period is shortened, and the service arrangement is easy to control. In addition, the execution path of the service arrangement can be rendered to correct the service arrangement, and the correctness and the rationality of the service arrangement are guaranteed.
Further, the service orchestration includes the following six components:
a Start component, a dubbo component, an http component, a return component, an event component, and an end component.
Wherein the Start component is configured to mark the service orchestration to begin execution; the dubbo component is used for storing basic service information; the basic service information is used for supporting the workflow server to acquire the data of the service arrangement; the http component is used for storing http service information; the http service information is used for supporting the workflow server to acquire the data of the service arrangement; the return component is used for stipulating a format of result return so that the workflow server side returns data in a corresponding format to the Web side according to the format; the event component is used for storing information required by the message sending; the end component is used for marking the service orchestration execution end.
Specifically, the Start component marks that the service arrangement starts to be executed, if the service arrangement does not have a Start component, the page of the Web end prompts error information, and when the workflow server executes the service arrangement, an error is also reported. There is one and only one start component in each service schedule. The return component specifies the format of the result return, and the workflow server returns data in a corresponding format to the Web end according to the format. There is at least one return component in each service orchestration. The end component is used to mark the end of service orchestration execution. There is at least one end component in each service orchestration.
The dubbo component is used for storing basic service information, and the basic service information comprises class names, method names, access parameters and the like. And the workflow server side calls the dubbo component according to the basic service information to acquire data of service arrangement. There are at least 0 dubbo components in each service orchestration. The http component is configured to store http service information, where the http service information includes a Uniform Resource Locator (URL), a reference, a get request mode, or a post request mode. The workflow server side can call the http component according to the http service information to obtain the data of the service arrangement. There are at least 0 http components in each service orchestration. The event component is used for saving information required by the sending message, and comprises Kafka, rocktmq and the like. There are at least 0 event components per service orchestration.
Fig. 2 is a schematic structural diagram of a service orchestration according to an embodiment of the present invention. As shown in FIG. 2, the service orchestration of the present embodiment includes one Start component, two dubbo components, three return components, and three end components.
Further, a straight line with an arrow is arranged between every two assemblies; the line with arrows is used to ensure the execution order of the components in the service orchestration.
Further, when the component at least corresponds to two straight lines with arrows, judging conditions are set on the straight lines with the arrows; the judgment condition is used for ensuring that only one straight line with an arrow corresponding to each component can pass through.
As shown in fig. 2, the dubbo module 2 corresponds to the straight lines of the two arrowheads, which point to the return module 2 and the return module 3, respectively, and the condition 1 and the condition 2 are set, respectively. When executing the service arrangement, the workflow server executes the return component 2 when judging that the condition 1 is satisfied, and executes the return component 3 when judging that the condition 2 is satisfied. In this way, only one line of the two arrowheads can pass through.
Further, the Web end comprises a front end and a background server. Step S1 specifically includes:
the front end generates original service arrangement according to arrangement operation of a user;
the front end converts the original service arrangement into json data;
the front end sends the json data to a background server;
the backstage server converts the json data into new json data to obtain service arrangement; the new json data is used for supporting analysis service arrangement of the workflow server side.
Further, after step S1, the method further includes:
service choreography is saved.
Further, step S2 specifically includes:
the workflow server analyzes the service arrangement to obtain the information of each component;
the workflow server side stores the component information into a tree structure according to the sequence arranged by the user; the tree structure comprises a plurality of nodes, and the nodes are in one-to-one correspondence with the components and used for representing the corresponding components;
and executing all nodes to be executed in the tree structure by the workflow server side to obtain trace data.
Fig. 3 is a schematic structural diagram of a tree structure according to an embodiment of the present invention. The tree structure is obtained by analyzing the service arrangement shown in fig. 2 by the workflow server.
Further, the service orchestration execution path echoing method according to the embodiment of the present invention further includes:
and rendering the time-consuming duration corresponding to each component of the service arrangement by the Web end according to trace data, the workflow Id and the version.
In a specific example, a Web end firstly obtains component IDs and time-consuming durations corresponding to components according to trace data; trace data includes the time-consuming duration corresponding to each component. Then, the Web terminal acquires json data according to the workflow Id and version; and finally, the Web terminal renders the execution path of the service arrangement and the time-consuming duration corresponding to each component according to the component ID and the json data. Therefore, the time-consuming duration of each service arrangement execution and the time-consuming duration corresponding to each component can be conveniently and quickly checked through the method and the device, and then which service response time is too long in the service arrangement execution process is determined, which party is specifically called by each service is helped to solve the problem, and the method and the device are favorable for service management and optimization of service arrangement.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that the terms "first," "second," and the like in the description of the present invention are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present invention, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow diagrams or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present invention includes additional implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present invention.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (9)
1. A service orchestration execution path echoing method, comprising:
the Web end generates service arrangement according to the arrangement operation of the user; the service layout comprises a workflow Id, a version and at least three components corresponding to the service layout;
the workflow server side executes the service arrangement to obtain trace data; the trace data comprises an executed Id corresponding to the trace data and at least three component IDs, and each component ID corresponds to each executed component;
after the message consumption service end consumes the trace data, writing the consumed trace data into an ES;
the Web terminal queries the ES according to the executed Id to acquire trace data;
and rendering the execution path of the service arrangement by the Web end according to the trace data, the workflow Id and the version.
2. The service orchestration execution path echoing method according to claim 1, wherein the service orchestration comprises the following six components:
a Start component, a dubbo component, an http component, a return component, an event component, and an end component;
the Start component is used to mark the Start of execution of the service orchestration;
the dubbo component is used for storing basic service information; the basic service information is used for supporting the workflow server to acquire the data of the service arrangement;
the http component is used for storing http service information; the http service information is used for supporting the workflow server to acquire the data of the service arrangement;
the return component is used for stipulating a format of result return so that the workflow server side returns data in a corresponding format to the Web side according to the format;
the event component is used for storing information required by the message sending;
the end component is used for marking the service orchestration execution end.
3. The service orchestration execution path echoing method according to claim 1, wherein a straight line with an arrow is provided between each two of the components; the straight line with arrows is used for ensuring the execution sequence of each component in the service arrangement.
4. The service orchestration execution path echoing method according to claim 3, wherein when the component corresponds to at least two of the arrowed lines, a determination condition is set on the arrowed lines; the judgment condition is used for ensuring that only one straight line with an arrow corresponding to each component can pass through.
5. The service orchestration execution path echoing method according to claim 1, wherein the Web-side comprises a front-end and a back-end server;
the Web end generates service arrangement according to the arrangement operation of the user, and the service arrangement comprises the following steps:
the front end generates original service arrangement according to arrangement operation of a user;
the front end converts the original service arrangement into json data;
the front end sends the json data to the background server;
the backstage server converts the json data into new json data to obtain the service arrangement; and the new json data is used for supporting the workflow server side to analyze the service arrangement.
6. The service orchestration execution path redisplaying method according to claim 1, wherein after the Web end generates the service orchestration according to the orchestration operation of the user, the method further comprises:
and saving the service arrangement.
7. The service orchestration execution path echoing method according to claim 1, wherein the workflow server executes the service orchestration to obtain trace data, comprising:
the workflow server side analyzes the service arrangement to obtain information of each component;
the workflow server side stores the component information into a tree structure according to the sequence arranged by the user; the tree structure comprises a plurality of nodes, and the nodes are in one-to-one correspondence with the components and used for representing the corresponding components;
and executing all nodes to be executed in the tree structure by the workflow server to obtain the trace data.
8. The service orchestration execution path echoing method according to claim 5, wherein rendering, by the Web end, the execution path of the service orchestration according to the trace data, the workflow Id, and the version comprises:
the Web end obtains the component ID according to the trace data;
the Web end obtains the json data according to the workflow Id and the version;
and rendering the execution path of the service arrangement by the Web terminal according to the component ID and the json data.
9. The service orchestration execution path echoing method according to claim 1, further comprising:
and the Web end determines the time-consuming duration corresponding to each component of the service arrangement according to the trace data, the workflow Id and the version.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110533518.1A CN113238844A (en) | 2021-05-17 | 2021-05-17 | Service arrangement execution path playback method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110533518.1A CN113238844A (en) | 2021-05-17 | 2021-05-17 | Service arrangement execution path playback method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113238844A true CN113238844A (en) | 2021-08-10 |
Family
ID=77134556
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110533518.1A Pending CN113238844A (en) | 2021-05-17 | 2021-05-17 | Service arrangement execution path playback method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113238844A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110302239A1 (en) * | 2010-06-04 | 2011-12-08 | International Business Machines Corporation | Managing Rule Sets as Web Services |
| CN104346412A (en) * | 2013-08-09 | 2015-02-11 | 中国科学院沈阳自动化研究所 | Semantic information based RFID (Radio Frequency Identification Device) complex event processing method |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| US20180316587A1 (en) * | 2017-04-27 | 2018-11-01 | Salesforce.Com, Inc. | Automated analysis and recommendations for highly performant single page web applications |
| CN111078504A (en) * | 2019-12-25 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Distributed call chain tracking method and device, computer equipment and storage medium |
| CN111142867A (en) * | 2019-12-31 | 2020-05-12 | 谷云科技(广州)有限责任公司 | Service visual arrangement system and method under micro-service architecture |
| CN111722929A (en) * | 2020-06-18 | 2020-09-29 | 南京龙猫商业智能科技股份有限公司 | Micro-service orchestration engine management method based on PaaS |
-
2021
- 2021-05-17 CN CN202110533518.1A patent/CN113238844A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110302239A1 (en) * | 2010-06-04 | 2011-12-08 | International Business Machines Corporation | Managing Rule Sets as Web Services |
| CN104346412A (en) * | 2013-08-09 | 2015-02-11 | 中国科学院沈阳自动化研究所 | Semantic information based RFID (Radio Frequency Identification Device) complex event processing method |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| US20180316587A1 (en) * | 2017-04-27 | 2018-11-01 | Salesforce.Com, Inc. | Automated analysis and recommendations for highly performant single page web applications |
| CN111078504A (en) * | 2019-12-25 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Distributed call chain tracking method and device, computer equipment and storage medium |
| CN111142867A (en) * | 2019-12-31 | 2020-05-12 | 谷云科技(广州)有限责任公司 | Service visual arrangement system and method under micro-service architecture |
| CN111722929A (en) * | 2020-06-18 | 2020-09-29 | 南京龙猫商业智能科技股份有限公司 | Micro-service orchestration engine management method based on PaaS |
Non-Patent Citations (1)
| Title |
|---|
| JAVA架构师小黑: "《微服务设计-服务组合和可视化编排思考》", pages 1 - 14, Retrieved from the Internet <URL:https://zhuanlan.zhihu.com/p/343423030> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107562556B (en) | Failure recovery method, recovery device and storage medium | |
| CN112286806B (en) | Automatic test method and device, storage medium and electronic equipment | |
| CN108984389A (en) | A kind of applied program testing method and terminal device | |
| CN115840687A (en) | Visual log link tracking method and system based on service level | |
| CN111290951A (en) | Test method, terminal, server, system and storage medium | |
| CN110515750B (en) | Application topology generation method, system and cluster | |
| CN112540808B (en) | Recording method of program behavior hierarchy call relationship and related equipment | |
| CN117472372B (en) | Responsive form construction method and system | |
| CN110888800A (en) | Service interaction function test method, device, storage medium and test system | |
| US9104356B2 (en) | Extendable system for preprocessing print document and method for the same | |
| CN117648257A (en) | Web automatic test method and system under Linux operating system | |
| CN110543401B (en) | Hierarchical application topology generation method, hierarchical application topology generation system and hierarchical application topology cluster | |
| CN113238844A (en) | Service arrangement execution path playback method | |
| CN111950252A (en) | HTTP response message format verification method, device and equipment | |
| CN113238901B (en) | Multi-device automatic testing method and device, storage medium and computer device | |
| CN103019927B (en) | A kind of performance test methods and system | |
| CN111966394A (en) | ETL-based data analysis method, device, equipment and storage medium | |
| CN114817393B (en) | Data extraction and cleaning method and device and storage medium | |
| CN117171364B (en) | Operation and maintenance knowledge graph updating method and device | |
| CN117931681B (en) | Interface diff test method based on API gateway log playback | |
| CN111209161B (en) | Method and system for automatically generating configuration file based on interface monitoring | |
| CN116627775B (en) | Writing optimization method and device for stateful server non-perception function | |
| CN111209204B (en) | Automatic web testing method based on JSON, system and device thereof | |
| CN108415829B (en) | Method and terminal for detecting time consumed by loading module | |
| CN115203616A (en) | Element positioning method and element positioning device |
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 |