CN115421824B - Micro-service execution engine, running method and application method - Google Patents

Abstract

The embodiment of the disclosure discloses a micro-service execution engine, an operation method and an application method. The micro-service execution engine includes: the system comprises a flow registration service component, a flow execution component, a flow analysis component, an exception handling component, an external access component and a business service agent component; the flow registration service component is used for supporting the registration function of the business flow edited by the visual editing tool; the flow execution component is used for supporting searching the business flow, executing the business flow, analyzing the business flow and calling the component to complete the service; the flow analysis component is used for analyzing the business flow; the exception handling component is used for capturing and handling exceptions in the execution process; the external access component is used for accessing the micro-service gateway to acquire an external service result when the service in the business process is external service; the business service agent component is an access portal for the microservice. The implementation mode can effectively locate, execute and analyze the business process of the micro service.

Description

Micro-service execution engine, running method and application method

Technical Field

The embodiment of the disclosure relates to the technical field of data analysis and display, in particular to a micro-service execution engine, an operation method and an application method.

Background

When the micro service platform is used for completing various service functions by calling a large number of external services, the coding mode can cause code redundancy, has poor readability and is easy to make mistakes. In addition, when micro-service business is debugged, the input and output of each service are inconvenient to check in the business process, and the single-step execution on each debugged service is inconvenient. Thus, there is an urgent need for a method that can efficiently perform, process, and facilitate progress knowledge for micro services.

Disclosure of Invention

In view of this, the embodiments of the present disclosure provide a micro-service execution engine, an operation method and an application method, so as to solve the technical problem in the prior art how to effectively execute and process the micro-service and facilitate the progress understanding.

In a first aspect of embodiments of the present disclosure, there is provided a micro-service execution engine comprising: the system comprises a flow registration service component, a flow execution component, a flow analysis component, an exception handling component, an external access component and a business service agent component; the process registration service component is used for supporting the registration function of the business process edited by the visual editing tool; the flow execution component is used for supporting searching the business flow, executing the business flow, analyzing the business flow and calling the component to complete service; the flow analysis component is used for analyzing the business flow; the exception handling component is used for capturing and handling exceptions in the execution process; the external access component is used for accessing the micro-service gateway to acquire an external service result when the service in the business process is external service; the above-described business service agent component is an access portal for micro services.

In some optional implementations of some embodiments, the above-described flow execution component further has a single step function and a function of checking execution progress, execution parameters, and execution results.

In some alternative implementations of some embodiments, the business process includes: XML-described business processes, JSON-described business processes, and intermediate business processes.

In some optional implementations of some embodiments, the flow resolution component includes: the system comprises a flow function processing part, a flow logic node processing part, a flow asynchronous processing part and a flow service single-step processing part; wherein the flow function processing part comprises a conversion function; the flow logic node processing part is used for processing logic branches of the business flow; the flow asynchronous processing part comprises an asynchronous synchronous call mechanism; the single step processing part of the flow service comprises a single step debugging mechanism.

In a second aspect of the embodiments of the present disclosure, there is provided a method for operating a micro service execution engine, including: the service agent component of the micro-service execution engine receives a service flow positioning request sent by a micro-service registry; the flow execution component of the micro-service execution engine searches the service flow in the service flow warehouse according to the service flow positioning request; and the flow analysis component of the micro-service execution engine analyzes the business flow and completes the request.

In a third aspect of the embodiments of the present disclosure, there is provided an application method of a micro service execution engine, including: receiving a business process positioning request sent by a micro-service registration center; transmitting the business process positioning request to a process execution component through a business service agent component of the micro-service execution engine; the flow execution component of the micro service execution engine is controlled to search the business flow in a business flow warehouse based on the business flow positioning request; and in the process of executing the flow executing component, controlling the flow executing component of the micro service executing engine to analyze the service flow so as to finish the request.

In some optional implementations of some embodiments, the flow execution component that controls the micro-service execution engine searches for a business flow in a business flow repository based on the business flow location request, and the method further includes: detecting whether an abnormality occurs in the process of executing the flow executing component; in response to determining that an exception occurs, controlling an exception handling component of the micro-service execution engine to capture the exception; and controlling the exception handling component to handle the exception.

In some optional implementations of some embodiments, the flow execution component that controls the micro-service execution engine searches for a business flow in a business flow repository based on the business flow location request, and the method further includes: determining whether an external service is called in the execution process of the business process; and in response to determining that the external service is invoked in the execution process of the business flow, controlling an external access component of the micro-service execution engine to access the micro-service gateway, and obtaining an external service result.

In some optional implementations of some embodiments, the flow execution component that controls the micro-service execution engine searches for a business flow in a business flow repository based on the business flow location request, and the method further includes: and displaying an execution process browsing page in the target browser in the process of executing the process execution component, wherein the execution process browsing page is displayed with a flow chart containing input and output parameters of the current service node and the service node.

In some optional implementations of some embodiments, in the process of executing by the flow execution component, controlling the flow execution component of the micro service execution engine to parse the service flow to complete the request includes: determining whether a modification operation for the above-described flowchart is detected; in response to not detecting the modification operation for the flow chart, controlling a flow execution component of the micro service execution engine to analyze the service flow to finish the request; in response to detecting a modification operation for the flowchart, modifying the flowchart according to the modification operation; and based on the modified flow chart, controlling a flow execution component of the micro service execution engine to analyze the new business flow so as to finish the request.

In a fourth aspect of the disclosed embodiments, there is provided an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the above method when the computer program is executed.

In a fifth aspect of the disclosed embodiments, a computer readable storage medium is provided, which stores a computer program which, when executed by a processor, implements the steps of the above method.

One of the above embodiments of the present disclosure has the following advantageous effects: a micro-service execution engine, comprising: the system comprises a flow registration service component, a flow execution component, a flow analysis component, an exception handling component, an external access component and a business service agent component; the process registration service component is used for supporting the registration function of the business process edited by the visual editing tool; the flow execution component is used for supporting searching the business flow, executing the business flow, analyzing the business flow and calling the component to complete service; the flow analysis component is used for analyzing the business flow; the exception handling component is used for capturing and handling exceptions in the execution process; the external access component is used for accessing the micro-service gateway to acquire an external service result when the service in the business process is external service; the above-described business service agent component is an access portal for micro services. The micro-service execution engine provided by the disclosure can effectively locate, execute and analyze the business process of the micro-service. In addition, the flow execution component also has a single step debugging function and a function of checking execution progress, execution parameters and execution results, so that the visualization of the processing procedure of the business flow is realized, and great convenience is brought for solving the processing progress and debugging conditions.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

FIG. 1 is a schematic diagram of a micro-service execution engine according to some embodiments of the present disclosure;

FIG. 2 is a flow diagram of some embodiments of a method of operation of a micro-service execution engine according to the present disclosure;

FIG. 3 is a flow diagram of some embodiments of an application method of a micro-service execution engine according to the present disclosure;

fig. 4 is a schematic structural diagram of an electronic device suitable for use in implementing some embodiments of the present disclosure.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the disclosed embodiments. However, it will be apparent to one skilled in the art that the present disclosure may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present disclosure with unnecessary detail.

A data display method, apparatus, electronic device, and medium applied to the medical field according to embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a micro-service execution engine according to some embodiments of the present disclosure.

As shown in fig. 1, the micro service execution engine 101 includes: a flow registration service component 102, a flow execution component 103, a flow resolution component 104, an exception handling component 105, an external access component 106, and a business service proxy component 107. Here, the above-described flow registration service component 102 is used to support the registration function of the business flow edited by the visual editing tool. The process execution component 103 is configured to support searching for a business process, executing the business process, analyzing the business process, and calling the component to complete a service. The process parsing component 104 is configured to parse a business process. The exception handling component 105 is used to capture exceptions during execution and handle exceptions. The external access component 106 is configured to access the micro service gateway to obtain an external service result when the service in the business process is an external service. The business service agent component 107 described above is an access portal for micro services.

The flow execution component 103 set forth above also has a single step function and a function of viewing execution progress, execution parameters, and execution results. The business process comprises the following steps: XML-described business processes, JSON-described business processes, and intermediate business processes. The above-mentioned intermediate business processes are business processes described in other forms besides XML-described business processes and JSON-described business processes. The flow parsing component 104 includes: a flow function processing section 1041, a flow logical node processing section 1042, a flow asynchronous processing section 1043, and a flow service single-step processing section 1044. Here, the flow function processing section 1041 includes a conversion function, the flow logical node processing section 1042 is configured to process a logical branch of a business flow, the flow asynchronous processing section 1043 includes an asynchronous synchronous call mechanism, and the flow service single step processing section 1044 includes a single step mechanism.

The role of the micro-service execution engine is described below with one example:

in the process of 'in-line transfer', a bank customer can initiate a transfer request through channels such as a counter or an ATM, and the micro-service execution engine invokes external services and organizes the external services, and finally returns the transfer result to the channel for sending the transfer request. The micro service execution engine may be used for a pneumatic query for checking whether an account is restricted or not, and for a core transfer for billing a transfer-out side and a transfer-in side account, respectively, when using an external service. The micro service execution engine may be used for transfer flow registration, which is used for registering a service to the database, and transfer flow update, which is used for updating a service state of the database, when the internal service is used. The constraint condition of the micro service execution engine is that the transfer is forbidden when the wind control inquiry bit passes the verification. Specific examples are: the transfer request is received, and first, the micro service execution engine internally registers the transfer flow. Then, a flow logic node processing part in the flow analysis component is called to determine whether risk checking and controlling are passed, an abnormality processing component is controlled to capture non-financial abnormality in the risk checking and controlling process, if abnormality occurs, the internal service of the micro-service execution engine updates transfer running water, and the abnormality is ended; if no abnormality occurs, determining whether risk checking and controlling pass or not, if not, updating transfer running water by internal service of the micro service execution engine, and ending failure; and if the external service is passed, calling the external access component to use the external service to transfer the core system, and controlling the exception handling component to capture the financial exception in the transfer process. If abnormality occurs in the process of abnormality capturing, the internal service of the micro-service execution engine updates transfer running water, and the abnormality fails; if no abnormality occurs, determining whether the transfer is successful or not through the flow logic node processing part, if so, updating the transfer flow by the internal service of the micro service execution engine, and if not, ending successfully.

In some alternative implementations of some embodiments, the preconditions of the micro-service execution engine require the developer to do the following: editing two service editing processes of account transfer flow registration and account transfer flow update in a business process warehouse, wherein the two service editing processes are similar to account transfer processes; registering in an external gateway to check and control risks, and transferring two external services by a core; the transfer flow service is compiled in the business flow repository, with the former two running water registration internal services and the two external services being orchestrated into a new service.

In some alternative implementations of some embodiments, the flow registration service component of the micro-service execution engine can only execute external and internal services that invoke registration completion. When the system for installing the micro-service execution engine runs, the service in the business process warehouse is automatically registered in the service system by scanning the service description file in a specific format in the file catalog of the service warehouse, and analyzing and loading the service according to the file format.

In some optional implementations of some embodiments, the flow execution component of the micro service execution engine may accept the request message sent by the registry, and the execution component may find the registered service flow from the service name according to the request message, and add appropriate context (e.g., serial number of transaction, system date, etc.) parameters to start executing the flow. Here, the service name is generated for each external system request by the adapter of the external gateway unique in the system.

In some alternative implementations of some embodiments, the flow resolution component of the micro-service execution engine is responsible for completion during execution of the flow, with the primary role of flow resolution group pricing being to sequentially or selectively execute content (including nodes and services) in the flow according to the flow orchestration.

The flow function of the flow function processing part in the flow analysis component exists in each internal or external service, is added by a developer when the flow is arranged, and is used for making necessary conversion on the parameters of the request content of each service (the service node needs to have the request content capacity work, and each service also can generate corresponding output content). For example, when a core transfer is called, the request parameter has a password field, but the password field is processed by ATM or counter encryption when a channel is requested, when a core transfer interface is called, the ATM encryption needs to be converted into the core encryption, when development is performed, the password in the request needs to be applied with a transfer encryption function corepassword=fn: convertPwd (atmPassword), when the flow function component finds that the parameter is wrapped by the function, the flow function component calls a corresponding function code to process the parameter first, and then the correct request parameter is transferred to the core transfer.

The processing part of the flow logic node in the flow parsing component is used for guiding the flow to different branches when a certain condition is met, each node is provided with a logic expression, and the value to be judged by the expression is derived from the output generated by the service on the node, such as selection or circulation.

The flow asynchronous processing part in the flow analysis component can execute the service or logic branch under the service in a multithreading mode before the service returns a result when the flow is executed. In a JAVA engine, each thread of JAVA can execute tasks while not interfering with each other, a flow service is organized as a main thread, and an asynchronously executed service is an child thread. In addition, in a special process, for example, a client submits a batch transfer of tens of thousands of times, but the client cannot wait until all execution is completed, usually, a first request is adopted, the banking service tells the client to accept successfully after receiving the request, and the asynchronous processing part of the process can save processing time and improve processing efficiency in the subsequent process of inquiring results.

The single-step processing part of the flow service in the flow analysis component is the basis of visual flow debugging, and when the flow is in a debugging mode, each service does not execute the next node or service immediately after the execution of each service is completed, but waits for the next instruction. The next node or service can be continuously executed after the instruction arrives, and meanwhile, the JAVA micro service engine provides a corresponding API (application program interface) to inquire the input before each service is executed and the result generated after the service is executed, so that the effect of debugging the visual flow can be achieved by making a webpage.

In some alternative implementations of some embodiments, the exception handling component of the micro-service execution engine has within the flow a virtual exception handling container (which may be understood as the scope of the exception handling component being responsible for exception capture) containing at least two branches, the types of branches including branches that are not in error and branches that are in error, the branches that are not in error being used to report to the services of the branches that are not in error, the flow being directed to branches that are in error when the execution is in error, each of which may capture a different error, e.g., a timeout error or a system shutdown error.

Fig. 2 is a flow diagram of some embodiments of a method of operating a micro-service execution engine according to the present disclosure. The method of operation of the micro-service execution engine of fig. 2 may be performed by the micro-service execution engine 101 of fig. 1. As shown in fig. 2, the method for operating the micro service execution engine includes the following steps:

in step S201, the service agent component of the micro service execution engine receives the service flow location request sent by the micro service registry.

In some embodiments, a business service proxy component of the micro-service execution engine may receive a business process location request issued by a micro-service registry. The service agent component is an access portal for the micro-service, and the micro-service registry invokes the agent service through the service agent component of the micro-service execution engine. Here, because different execution engines are required for different forms of business processes to execute, in order to reduce the coupling of codes, the business processes are uniformly distributed to different engines for processing after the business service agent component accepts the request when executing the business processes. The business process location request may be a lookup or generation request for describing the process of the business requirement. Here, the business process includes: XML-described business processes, JSON-described business processes, and intermediate business processes. The business process is completed and packaged jar package in code form.

Step S202, the flow execution component of the micro-service execution engine searches the business flow in the business flow warehouse according to the business flow positioning request.

In some embodiments, the flow execution component of the micro-service execution engine may search the business flow repository for business flows according to the business flow location request. The business processes are stored in the business process warehouse. As an example, the flow execution component of the micro-service execution engine may search the business flow repository for a business flow that meets or is similar to the business flow location request description described above, based on the business flow location request. Specifically, the above-mentioned flow execution component also has a single step function and a function of checking execution progress, execution parameters and execution results. A single step debugging function is understood to be a function that can be debugged while viewing execution progress.

In step S203, the flow analysis component of the micro service execution engine analyzes the service flow, and completes the request.

In some embodiments, the flow resolution component of the micro-service execution engine may resolve the business flow described above, completing the request. Here, the flow parsing component includes: the system comprises a flow function processing part, a flow logic node processing part, a flow asynchronous processing part and a flow service single-step processing part. Specifically, the flow function processing part includes a conversion function, the flow logic node processing part is used for processing logic branches of a business flow, the flow asynchronous processing part includes an asynchronous synchronous call mechanism, and the flow service single-step processing part includes a single-step debugging mechanism. An asynchronous synchronous call mechanism is understood here to be a management mechanism that can make calls synchronously or asynchronously.

One of the above embodiments of the present disclosure has the following advantageous effects: a micro-service execution engine, comprising: the system comprises a flow registration service component, a flow execution component, a flow analysis component, an exception handling component, an external access component and a business service agent component; the process registration service component is used for supporting the registration function of the business process edited by the visual editing tool; the flow execution component is used for supporting searching the business flow, executing the business flow, analyzing the business flow and calling the component to complete service; the flow analysis component is used for analyzing the business flow; the exception handling component is used for capturing and handling exceptions in the execution process; the external access component is used for accessing the micro-service gateway to acquire an external service result when the service in the business process is external service; the above-described business service agent component is an access portal for micro services. The running method of the micro-service execution engine can effectively locate, execute and analyze the business process of the micro-service. In addition, the flow execution component also has a single step debugging function and a function of checking execution progress, execution parameters and execution results, so that the visualization of the processing procedure of the business flow is realized, and great convenience is brought for solving the processing progress and debugging conditions. In addition, the business flow is the jar packet which is completed and packaged in a code form, the problems of code redundancy, poor readability, easy error and the like caused by a coding mode are avoided in the calling and analyzing processes, the maintenance is convenient, and the processing speed is improved.

Fig. 3 is a flow diagram of some embodiments of an application method of a micro-service execution engine according to the present disclosure. The application method of the micro service execution engine of fig. 3 may be executed by the micro service execution engine 101 of fig. 1. As shown in fig. 3, the application method of the micro service execution engine includes the following steps:

step S301, a business process positioning request sent by a micro-service registry is received.

In some embodiments, an execution body of an application method of a micro-service execution engine (e.g., micro-service execution engine 101 shown in fig. 1) may receive a business process location request issued through a micro-service registry using a business service proxy component. The business process location request may be a lookup or generation request for describing the process of the business requirement. Here, the business process includes: XML-described business processes, JSON-described business processes, and intermediate business processes. The above-mentioned intermediate business processes are business processes described in other forms besides XML-described business processes and JSON-described business processes.

Step S302, transmitting the business process positioning request to the process execution component through the business service proxy component of the micro service execution engine.

In some embodiments, the execution body may transmit the business process location request to a process execution component through a business service proxy component of the micro-business execution engine.

Step S303, a flow execution component of the micro service execution engine is controlled to search the business flow in a business flow warehouse based on the business flow positioning request.

In some embodiments, the specific implementation of step S303 and the technical effects thereof may refer to step S202 in those embodiments corresponding to fig. 2, which are not described herein.

In some optional implementations of some embodiments, the method further includes: detecting whether an abnormality occurs in the process of executing the flow executing component; in response to determining that an exception occurs, controlling an exception handling component of the micro-service execution engine to capture the exception; and controlling the exception handling component to handle the exception. Here, an exception may be understood as an analysis exception, a logic handling exception, a flow function conversion exception during execution.

In some optional implementations of some embodiments, the method further includes: determining whether an external service is called in the execution process of the business process; and in response to determining that the external service is invoked in the execution process of the business flow, controlling an external access component of the micro-service execution engine to access the micro-service gateway, and obtaining an external service result.

In some optional implementations of some embodiments, the method further includes: and displaying an execution process browsing page in the target browser in the process of executing the process execution component, wherein the execution process browsing page is displayed with a flow chart containing input and output parameters of the current service node and the service node.

Step S304, in the process of executing the flow executing component, the flow executing component of the micro service executing engine is controlled to analyze the business flow, and the request is completed.

In some embodiments, during execution of the flow execution component, the execution body may determine whether a modification operation for the flow chart is detected. In response to not detecting a modification operation for the flowchart, the execution body may control a flow execution component of the micro-service execution engine to parse the business flow to complete a request. In response to detecting a modification operation for the flowchart, the execution body may modify the flowchart according to the modification operation. Then, based on the modified flow chart, the execution body can control the flow execution component of the micro service execution engine to analyze the new business flow, so as to complete the request.

One of the above embodiments of the present disclosure has the following advantageous effects: the application method of the micro-service execution engine provided by the disclosure can effectively locate, execute and analyze the business process of the micro-service. The flow execution component also has a single step debugging function and a function of checking execution progress, execution parameters and execution results, so that the visualization of the processing process of the business flow is realized, and great convenience is brought for solving the processing progress and debugging conditions. The exception handling component can capture and handle the exception in real time in the executing process, and time and human resource waste caused by the exception are reduced. In addition, in the execution process of the flow execution component, the execution process browsing page of the flow chart containing the current service node and the input and output parameters of the service node is displayed, so that the visualization of the processing progress and the data is realized. And whether the modification operation on the flow chart exists is detected in the process of analyzing the business flow, and the new business flow is analyzed according to the modification operation, so that the development process is greatly simplified, the requirement on the programming language capability of a developer is eliminated, and the method can concentrate on the business development.

Any combination of the above optional solutions may be adopted to form an optional embodiment of the present application, which is not described herein in detail.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not constitute any limitation on the implementation process of the embodiments of the disclosure.

Fig. 4 is a schematic diagram of a computer device 4 provided by an embodiment of the present disclosure. As shown in fig. 4, the computer device 4 of this embodiment includes: a processor 401, a memory 402 and a computer program 403 stored in the memory 402 and executable on the processor 401. The steps of the various method embodiments described above are implemented by processor 401 when executing computer program 403. Alternatively, the processor 401, when executing the computer program 403, performs the functions of the modules/units in the above-described apparatus embodiments.

Illustratively, the computer program 403 may be partitioned into one or more modules/units, which are stored in the memory 402 and executed by the processor 401 to complete the present disclosure. One or more of the modules/units may be a series of computer program instruction segments capable of performing a specific function for describing the execution of the computer program 403 in the computer device 4.

The computer device 4 may be a desktop computer, a notebook computer, a palm computer, a cloud server, or the like. The computer device 4 may include, but is not limited to, a processor 401 and a memory 402. It will be appreciated by those skilled in the art that fig. 4 is merely an example of computer device 4 and is not intended to limit computer device 4, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., a computer device may also include an input-output device, a network access device, a bus, etc.

The processor 401 may be a central processing unit (Central Processing Unit, CPU) or other general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 402 may be an internal storage unit of the computer device 4, for example, a hard disk or a memory of the computer device 4. The memory 402 may also be an external storage device of the computer device 4, for example, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the computer device 4. Further, the memory 402 may also include both internal storage units and external storage devices of the computer device 4. The memory 402 is used to store computer programs and other programs and data required by the computer device. The memory 402 may also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In the embodiments provided in the present disclosure, it should be understood that the disclosed apparatus/computer device and method may be implemented in other manners. For example, the apparatus/computer device embodiments described above are merely illustrative, e.g., the division of modules or elements is merely a logical functional division, and there may be additional divisions of actual implementations, multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present disclosure may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present disclosure may implement all or part of the flow of the method of the above-described embodiments, or may be implemented by a computer program to instruct related hardware, and the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of the method embodiments described above. The computer program may comprise computer program code, which may be in source code form, object code form, executable file or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the content of the computer readable medium can be appropriately increased or decreased according to the requirements of the jurisdiction's jurisdiction and the patent practice, for example, in some jurisdictions, the computer readable medium does not include electrical carrier signals and telecommunication signals according to the jurisdiction and the patent practice.

The above embodiments are merely for illustrating the technical solution of the present disclosure, and are not limiting thereof; although the present disclosure has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the disclosure, and are intended to be included in the scope of the present disclosure.

Claims (1)

1. A micro-service execution engine, comprising: the system comprises a flow registration service component, a flow execution component, a flow analysis component, an exception handling component, an external access component and a business service agent component; the process registration service component is used for supporting the registration function of the business process edited by the visual editing tool; the flow execution component is used for supporting searching the business flow, executing the business flow, analyzing the business flow and calling the component to complete service; the flow analysis component is used for analyzing the business flow; the exception handling component is used for capturing and handling exceptions in the execution process; the external access component is used for accessing the micro-service gateway to acquire an external service result when the service in the business process is external service; the business service agent component is an access entry of the micro-service; the flow execution component also has a single step debugging function and a function of checking execution progress, execution parameters and execution results; the business process comprises the following steps: XML-described business processes, JSON-described business processes and intermediate business processes; the flow parsing component includes: the system comprises a flow function processing part, a flow logic node processing part, a flow asynchronous processing part and a flow service single-step processing part; wherein the flow function processing section includes a conversion function; the flow logic node processing part is used for processing logic branches of the business flow; the flow asynchronous processing part comprises an asynchronous synchronous call mechanism; the single-step processing part of the flow service comprises a single-step debugging mechanism;

after receiving a service flow positioning request sent by a micro service registry, a service proxy component of the micro service execution engine searches a service flow in a service flow warehouse;

during the execution process of the flow execution component, the exception handling component detects whether an exception occurs;

in response to determining that an exception occurred, the exception handling component captures the exception and handles the exception;

in response to determining that the external service is invoked in the execution process of the business flow, the external access component accesses the micro-service gateway to acquire an external service result;

displaying an execution process browsing page on a target browser in the process of execution of the flow execution component, wherein the execution process browsing page displays a flow chart containing input and output parameters of a current service node and a service node;

in response to not detecting a modification operation for the flow chart, the flow execution component parses the business flow to complete a request;

in response to detecting a modification operation for the flowchart, modifying the flowchart in accordance with the modification operation;

based on the modified flow chart, the flow execution component analyzes the new business flow and completes the request;

the exception handling component includes a virtual exception handling container containing non-faulty branches for reporting to services of non-faulty branches, and faulty branches, each faulty branch being able to capture a different fault by directing flow to the faulty branch when executing the fault.

Images