Application orchestration service system and method based on Conductor framework
Through the application orchestration system based on the Conductor framework, the workflow and node modules are built using the Netflix Conductor engine, which solves the problems of front-end applications in the microservice architecture handling complex business rules and multi-service calls, and realizes low-code service orchestration and monitoring, improving Visualization and efficiency of business processes.
Patent Information
- Application Number
- CN202211663279.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-23
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2042-12-23
AI Technical Summary
In the microservice architecture, front-end applications need to deal with complex business rules and multi-service calls, resulting in a large number of script code writing and logical complexity. The service logic in common areas may be leaked, and the front-end does not care about complex back-end in the scenario of separation of front-end and back-end. Logical, it is difficult to implement simple service calls.
Using the application orchestration system based on the Conductor framework, through the design of the data layer, logical orchestration layer and application layer, the Netflix Conductor orchestration engine is used to build a workflow, assemble node modules to form a service interface, provide a visual interface for business process orchestration, and realize the node template. Encapsulation and monitoring to reduce the complexity of front-end scripting.
It realizes low-code application service orchestration, assembles multi-class node logic through the visual interface, quickly completes service calls in different business scenarios, encapsulates underlying processing logic, reduces code development, and improves the visualization and monitoring capabilities of service call logic.
Smart Images

Figure CN115955408B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of application service orchestration, and in particular, to an application orchestration system and method based on a Conductor framework, and more particularly, to an application service orchestration system that integrates a front-end application operation interface and a monitoring system designed based on the Netflix Conductor open source microservice orchestration engine. Background Art
[0002] Microservices are a popular software architecture style. After the underlying common technical services and mid-tier business service capabilities are in place, upper-layer applications should be quickly built based on these services. However, it is not possible to implement all scenarios by simply calling one service. When there are certain business rules that need to be processed, it often involves calling multiple services, and basic data processing and logical judgment are also involved in the middle to complete.
[0003] If the front-end application is used to handle this combination, a large amount of script code needs to be written, which needs to be adjusted from time to time, and there is a problem of common domain service logic being leaked to the outside. Secondly, in the scenario where the front-end and back-end are separated, the front-end does not care about the complex back-end logic.
[0004] Application service orchestration is the process of logically combining basic business services according to certain business rules and providing a packaged combined service interface to the front end.
[0005] Application service orchestration can perform visual business process orchestration to reduce the large number of repetitive and non-technical front-end scripts and improve the visualization of service call logic.
[0006] Patent document CN107343018B (application number: 201710005170.2) discloses an application service orchestration method and system for a PaaS cloud platform. The steps of the method are as follows: S1. The user selects the specific service that needs to be orchestrated in the Catalog service list according to the business; S2. The required parameters in the service are set; S3. After writing the services in sequence, the platform interface is called to pass the orchestration file to the platform; S4. The platform orchestrates the service according to the orchestration files of different services. Summary of the invention
[0007] In view of the defects in the prior art, the object of the present invention is to provide an application orchestration service system and method based on the Conductor framework.
[0008] According to the present invention, an application orchestration service system based on a Conductor framework is provided, comprising:
[0009] Data layer: databases and data tables that store data required for application orchestration processes;
[0010] Logical orchestration layer: forms service interfaces for different business scenarios by assembling multiple node modules;
[0011] Application layer: Access corresponding service interfaces, databases and / or data tables through web pages to provide corresponding orchestration services;
[0012] The node module is a packaged template of different nodes, which is the smallest execution unit in the orchestration service and carries the execution logic.
[0013] Preferably, the logic orchestration layer includes: using Netflix Conductor orchestration engine to build a workflow, and reassembling the functions of the node modules based on the built workflow.
[0014] Preferably, the node template includes: a start / end node, a judgment node, a call node, a wait node, an output node, a polling node and a parallel start / end node.
[0015] Preferably, the orchestration service needs to rely on the underlying resource configuration;
[0016] The underlying resource configuration includes certificates, encryption and decryption rules, and database connection passwords.
[0017] Preferably, different data operation permissions are set on the data layer; and the application layer uses corresponding data based on the corresponding data operation permissions.
[0018] Preferably, access rights are set for the orchestration service.
[0019] Preferably, based on the underlying framework capabilities of conductor, each time the orchestration service is called by an external application, a corresponding service ID will be generated to mark the data execution status of this call; each time the call is made, the service monitoring will monitor the call results; the call records and execution results of the corresponding service will be displayed in detail;
[0020] The monitoring will also monitor each node under the service; the node execution status will be monitored through the detailed log information of the node operation.
[0021] According to the present invention, an application orchestration service method based on a Conductor framework is provided, comprising:
[0022] Step S1: The data layer stores the database and data tables required for the application orchestration process;
[0023] Step S2: The logic orchestration layer forms service interfaces for different business scenarios by assembling multiple node modules;
[0024] Step S3: The application layer accesses the corresponding service interface, database and / or data table through the page, thereby providing corresponding orchestration services;
[0025] The node module is a packaged template of different nodes, which is the smallest execution unit in the orchestration service and carries the execution logic.
[0026] Preferably, the logic orchestration layer includes: using Netflix Conductor orchestration engine to build a workflow, and reassembling the functions of the node modules based on the built workflow;
[0027] The node template includes: a start / end node, a judgment node, a call node, a wait node, an output node, a polling node and a parallel start / end node.
[0028] Preferably, based on the underlying framework capabilities of conductor, each time the orchestration service is called by an external application, a corresponding service ID will be generated to mark the data execution status of this call; each time the call is made, the service monitoring will monitor the call results; the call records and execution results of the corresponding service will be displayed in detail;
[0029] The monitoring will also monitor each node under the service; the node execution status will be monitored through the detailed log information of the node operation.
[0030] Compared with the prior art, the present invention has the following beneficial effects:
[0031] 1. The present invention provides application services suitable for upper-level page scenarios based on the conductor open source framework, achieves low-code effects by abstracting multiple types of standard processing nodes, and implements the encapsulation of underlying processing logic to facilitate business applications;
[0032] 2. The present invention can assemble multiple types of node logics to realize service call logic in different business scenarios through a visual interface;
[0033] 3. The present invention can quickly complete data acquisition solutions in different ways such as http, HTTPS, and data access by abstracting and encapsulating nodes into different standardized execution logics; it integrates multiple regular rules, inequality configuration, and operation logic processing methods, and can be directly configured and used through the interface without the need for code development each time;
[0034] 4. The present invention supports users to directly build service processes through an interactive method of dragging and dropping the canvas, and the interface is friendly and easy to use. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:
[0036] Figure 1 This is a schematic diagram of the application orchestration service system based on the Conductor framework.
[0037] Figure 2 Diagram of the orchestration service system for applications based on the Conductor framework
[0038] Figure 3 Executes the flowchart for the node. DETAILED DESCRIPTION
[0039] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.
[0040] Example 1
[0041] According to the present invention, an application orchestration service system based on a Conductor framework is provided, comprising:
[0042] Data layer: databases and data tables that store data required for application orchestration processes;
[0043] Logical orchestration layer: forms service interfaces for different business scenarios by assembling multiple node modules;
[0044] Application layer: Access corresponding service interfaces, databases and / or data tables through web pages to provide corresponding orchestration services;
[0045] The node module is a packaged template of different nodes, which is the smallest execution unit in the orchestration service and carries the execution logic.
[0046] Specifically, the logic orchestration layer includes: using the Netflix Conductor orchestration engine to build a workflow, and reassembling the functions of the node modules based on the built workflow.
[0047] Specifically, the node template includes: a start / end node, a judgment node, a call node, a wait node, an output node, a polling node, and a parallel start / end node.
[0048] Specifically, when orchestrating services, it is necessary to rely on the underlying resource configuration;
[0049] The underlying resource configuration includes certificates, encryption and decryption rules, and database connection passwords.
[0050] Specifically, different data operation permissions are set on the data layer; and the application layer uses corresponding data based on the corresponding data operation permissions.
[0051] Specifically, access rights are set for the orchestration service.
[0052] Specifically, based on the underlying framework capabilities of conductor, each time the orchestration service is called by an external application, a corresponding service ID will be generated to mark the data execution status of this call; each time a call is made, the service monitoring will monitor the call results; the call records and execution results of the corresponding service will be displayed in detail;
[0053] The monitoring will also monitor each node under the service; the node execution status will be monitored through the detailed log information of the node operation.
[0054] According to the present invention, an application orchestration service method based on a Conductor framework is provided, comprising:
[0055] Step S1: The data layer stores the database and data tables required for the application orchestration process;
[0056] Step S2: The logic orchestration layer forms service interfaces for different business scenarios by assembling multiple node modules;
[0057] Step S3: The application layer accesses the corresponding service interface, database and / or data table through the page, thereby providing corresponding orchestration services;
[0058] The node module is a packaged template of different nodes, which is the smallest execution unit in the orchestration service and carries the execution logic.
[0059] Specifically, the logic orchestration layer includes: using Netflix Conductor orchestration engine to build workflows, and reassembling the functions of node modules based on the built workflows;
[0060] The node template includes: a start / end node, a judgment node, a call node, a wait node, an output node, a polling node and a parallel start / end node.
[0061] Specifically, based on the underlying framework capabilities of conductor, each time the orchestration service is called by an external application, a corresponding service ID will be generated to mark the data execution status of this call; each time a call is made, the service monitoring will monitor the call results; the call records and execution results of the corresponding service will be displayed in detail;
[0062] The monitoring will also monitor each node under the service; the node execution status will be monitored through the detailed log information of the node operation.
[0063] The node actually corresponds to the microservice architecture system, which breaks down the specific execution logic into services that can be independently output and provided. The essence of the middle platform is an aggregated service item that can solve a single business scenario. Service orchestration can form corresponding middle platform capabilities through the combined orchestration of multiple nodes; the present invention combines the microservice architecture and the middle platform capabilities to quickly respond to different scenario demands of the business layer from the bottom up.
[0064] Example 2
[0065] Embodiment 2 is a preferred embodiment of Embodiment 1
[0066] According to the present invention, an application service orchestration system with a front-end application operation interface and a monitoring system is provided based on the Netflix Conductor open source microservice orchestration engine. Figure 1-2 As shown, the core of the system includes three layers: data layer, logic orchestration layer and application layer.
[0067] The data layer refers to the database and data table that store the data required for the application orchestration process. The data layer includes three basic data modules: application data module, service orchestration module, and resource parameter module.
[0068] The logical orchestration layer mainly uses the Netflix Conductor orchestration engine to build workflows, and implements multiple template applications through secondary assembly of node (Task) functions. Specifically, it can be abstracted to define each interface capability as a separate node template, each node will have corresponding data processing capabilities, and multiple nodes are assembled to form service interfaces for different business scenarios.
[0069] The application layer refers to the front-end application that users actually operate and requires account login control. The application layer provides the ability to access the corresponding logic orchestration layer and data layer by providing corresponding pages.
[0070] The WorkFlow module refers to an overall functional module that includes a front-end visual interface and is provided to users for service process orchestration and management. The module provides multiple types of encapsulated nodes (TASK) through built-in support for defining different microservice interfaces through node (Task) templates, and then completes the assembly through canvas applications to achieve the creation of service workflows. The packaged services can be directly exposed to external applications for use.
[0071] The node (TASK) module refers to different node templates that have been packaged. It is the smallest execution unit in the overall service and carries a section of execution logic, such as sending an HTTP request. This application orchestration system mainly encapsulates 7 major node templates (start / end node, judgment node, call node, wait node, output node, polling node, parallel start / end node). The corresponding service flow (WorkFlow) can be formed by assembling nodes (TASK).
[0072] The Source module refers to the configuration of the underlying resources that are relied upon when performing service orchestration. The underlying resources that are relied upon can be mainly divided into the following categories: certificates, encryption and decryption rules, database connection passwords
[0073] Access permissions refer to the permissions that control whether a user can access an application in a software (or website) after logging in. Specifically, when a user does not have access permissions to an application, the entrance to the application will be hidden or unavailable to the user.
[0074] Data permissions refer to permissions that control the range of data that a user can operate (add, delete, modify, and query) in an application. In applications involving data permissions, if a user does not have permission for a piece of data, the data will be hidden from the user or cannot be operated.
[0075] The system completes the process of an application service orchestration, including:
[0076] Step 1: Activate system access permissions to allow customers to log in to the corresponding backend to perform configuration operations.
[0077] Step 2: Create a service and complete the basic service information, including: service basic information definition, service request parameter definition, and service return parameter definition.
[0078] Step 3: Build the specific application orchestration logic under the service, and complete the corresponding data processing by adding different processing nodes based on the data flow processing logic.
[0079] Step 4: Use the debugging function to complete the overall logic debugging of the service and release it. The released services will be uniformly encapsulated as restful interfaces to provide services to the outside world, which can be called by application-side services.
[0080] The service can be extended to define basic service information, debug services, and monitor services. As a higher-level encapsulation of multiple nodes, the service can be directly called by upper-level application services. The logic can be processed and returned according to the application service scenario. At the same time, it has the corresponding debugging capabilities and can be tested and debugged in conjunction with business scenarios to ensure that the processing logic reviews business requirements:
[0081] The basic service information definition includes the service name, service code, service type, request method, message format, request parameters, and return parameter definitions. The basic information defines how the encapsulated service will be provided to the outside world.
[0082] Service debugging: The system provides debugging capabilities, similar to the way Postman initiates simulated calls to debug services, and confirms that the orchestrated services return corresponding processing results according to business requirements.
[0083] Service monitoring: Based on the underlying framework capabilities of conductor, each time a service is called by an external application, a corresponding service ID will be generated to mark the data execution status of this call. For each call, service monitoring will monitor the call results. The call records and execution results of the corresponding service are displayed in detail.
[0084] The monitoring will monitor each node under the service at the same time, and monitor the node execution status by printing the detailed log information of the node operation.
[0085] The nodes can be expanded into different node templates. Different execution logics are encapsulated into corresponding templates to provide corresponding capabilities for direct use. The secondary encapsulation of standard logic reduces the complexity of upstream calls and improves performance. By assembling applications with different node capabilities, more complex service processes can be established to cope with different business processing scenarios. For each node in the overall orchestration service, Figure 3 The process shown determines how to execute the corresponding logic of the node and output the corresponding result;
[0086] The encapsulated core node template is described as follows:
[0087] Calling node: data acquisition and processing node. The node encapsulation supports the ability to access data sources through HTTP, HTTPS, web sercive, socket, databaseToAPI, etc. 1. Supports directly configuring the request method, request format, request address, encryption and decryption rules, certificates and other information of the corresponding data source to establish a docking mechanism with the downstream data source to obtain the corresponding data. 2. For the data source acquisition results, secondary processing can be performed to meet the upstream business requirements (including assignment operations, field mapping, code value mapping, and operation processing). 3. Handling of exception mechanisms. The data acquisition processing node can configure the exception handling mechanism. Supports defining a retry mechanism in the event of an abnormal downstream interface, including timeout mechanism, timeout time, number of retries and other parameters.
[0088] DatabaseToApi supports direct configuration of access modes to database tables, performs combined query processing on multiple database tables to obtain corresponding parameter results and encapsulates the results into a restful standard interface for service provision.
[0089] Judgment node: handles branch judgment logic based on different data results. Through the configuration of conditional expressions, it supports the judgment of parameter values by AND, OR, NOT, greater than, less than, equal to, etc., and then further performs different processing logic.
[0090] Concurrent start / end nodes: perform concurrent data acquisition and processing. Multiple call nodes can be configured under the concurrent node to implement parallel data acquisition and processing mechanisms. Supports synchronous processing of multiple data sources and result output.
[0091] Conversion node: configuration of data mapping relationship. It can perform code value conversion, data format conversion, field name conversion, etc.
[0092] Polling node: asynchronous data source acquisition processing mechanism. Define the triggering mechanism and processing logic of scheduled tasks.
[0093] The resource module can be expanded to include the overall management of underlying data resources such as databases, servers, certificate management, and data source interfaces, and expand the acquisition and processing capabilities for multiple types of underlying data sources:
[0094] The database can be configured with parameters such as database name, database type (supports access to Oracle, MQL, PG relational databases), user name, password, JDBC URL, etc. Complete the connection access to the underlying database table.
[0095] By configuring the server address, user name, and password, the server can establish a connection with the corresponding server to obtain non-relational data sources such as files.
[0096] Certificate management supports calling the HTTPS interface by adding certificates.
[0097] The data permissions can be further combined with the user's role to encapsulate different system operation roles, and each role will correspond to specific operable data permissions to ensure that the system is used under a mechanism with corresponding permission control.
[0098] Example 3
[0099] Embodiment 3 is a preferred embodiment of Embodiment 1 and / or Embodiment 2.
[0100] A solution for interfacing with an over-the-counter fund trading system provided by the present invention
[0101] The investment management system is the asset management system owned by the investment manager. Generally, the asset management system is deployed within the financial institution. The investment manager uses this system to issue trading instructions.
[0102] The fund sales system refers to the system that connects the fund sales infrastructure with investment institutions. It is responsible for executing the query, transaction and other instructions issued by the investment management system, and providing fund investment institutions with information such as the results of fund transaction instruction execution required for business operations according to the agreement.
[0103] Investment managers use the investment management system to issue trading instructions and use the investment management system to track the entire transaction chain.
[0104] End-to-end system connection refers to the data interaction between the investment management system and the fund sales system directly through the API interface. OTC fund transactions can be carried out without changing the original interface usage habits of investment managers.
[0105] In the context of financial institutions' comprehensive digital reform, completing the full chain of over-the-counter fund transactions through system docking has become a standard solution. Generally, financial institutions will dock with multiple sales agencies, and the sales systems of different sales agencies will follow different interface rules, that is, the investment management system will face the current situation of multiple sets of interface development and docking. As an upstream application system, the investment management system expects that it can complete the access of multiple sales systems through a set of standard interfaces. Through the application orchestration service, the interfaces provided by different sales agencies can be standardized and encapsulated through the service flow module, and standard interface request methods, request formats, request input parameters, request output parameters and other information can be formulated.
[0106] When there is special processing and changes to certain parameters in the interface, editing and adjustment can be performed through the application orchestration system to reduce adjustments at the code level.
[0107] Those skilled in the art know that, in addition to implementing the system, device and its various modules provided by the present invention in a purely computer-readable program code, it is entirely possible to implement the same program in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded microcontrollers by logically programming the method steps. Therefore, the system, device and its various modules provided by the present invention can be considered as a hardware component, and the modules included therein for implementing various programs can also be considered as structures within the hardware component; the modules for implementing various functions can also be considered as both software programs for implementing the method and structures within the hardware component.
[0108] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.
Claims
1. An application orchestration service system based on the Conductor framework, characterized in that: include: Data layer: databases and data tables that store data required for application orchestration processes; Logical orchestration layer: forms service interfaces for different business scenarios by assembling multiple node modules; Application layer: Access corresponding service interfaces, databases and / or data tables through web pages to provide corresponding orchestration services; The node module is a packaged node template of different nodes, which is the smallest execution unit in the orchestration service and carries the execution logic; The logic orchestration layer includes: using Netflix Conductor orchestration engine to build workflows, and reassembling the functions of node modules based on the built workflows; The node template includes: start / end node, judgment node, call node, wait node, output node, polling node and parallel start / end node; When orchestrating services, you need to rely on the underlying resource configuration; The underlying resource configuration includes certificates, encryption and decryption rules, and database connection passwords; Different data operation permissions are set on the data layer; the application layer uses corresponding data based on the corresponding data operation permissions; Setting access permissions for the orchestration service; Based on the capabilities of the conductor underlying framework, each time the orchestration service is called by an external application, a corresponding service ID will be generated to mark the data execution status of this call; each time a call is made, the service monitoring will monitor the call results; the call records and execution results of the corresponding service will be displayed in detail; The monitoring will also monitor each node under the service; the node execution status will be monitored through the detailed log information of the node operation.
2. An application orchestration service method based on the Conductor framework, characterized in that: include: Step S1: The data layer stores the database and data tables required for the application orchestration process; Step S2: The logic orchestration layer forms service interfaces for different business scenarios by assembling multiple node modules; Step S3: The application layer accesses the corresponding service interface, database and / or data table through the page, thereby providing corresponding orchestration services; The node module is a packaged node template of different nodes, which is the smallest execution unit in the orchestration service and carries the execution logic; The logic orchestration layer includes: using Netflix Conductor orchestration engine to build workflows, and reassembling the functions of node modules based on the built workflows; The node template includes: start / end node, judgment node, call node, wait node, output node, polling node and parallel start / end node; When orchestrating services, you need to rely on the underlying resource configuration; The underlying resource configuration includes certificates, encryption and decryption rules, and database connection passwords; Different data operation permissions are set on the data layer; the application layer uses corresponding data based on the corresponding data operation permissions; Setting access permissions for the orchestration service; Based on the capabilities of the conductor underlying framework, each time the orchestration service is called by an external application, a corresponding service ID will be generated to mark the data execution status of this call; each time a call is made, the service monitoring will monitor the call results; the call records and execution results of the corresponding service will be displayed in detail; The monitoring will also monitor each node under the service; the node execution status will be monitored through the detailed log information of the node operation.
