CN115955408A - Application arrangement service system and method based on Conductor framework - Google Patents

Abstract

The invention provides an application arrangement service system and method based on a factor framework, which comprises the following steps: and (3) a data layer: the database and the data table are used for storing data required by the application arrangement process; a logic arrangement layer: forming service interfaces for different service scenes by assembling a plurality of node modules; an application layer: accessing corresponding service interfaces, databases and/or data tables through pages, thereby providing corresponding arrangement services; the node module is different node templates which are packaged, is the minimum execution unit in the arrangement service and bears execution logic.

Description

Conductor framework-based application orchestration service system and method

technical field

The present invention relates to the technical field of application service arrangement, in particular, it relates to the application arrangement system and method based on the Conductor framework, and more specifically, it relates to the integrated front-end application operation interface and the application service of the monitoring system designed based on the Netflix Conductor open source micro-service arrangement engine orchestration system.

Background technique

Microservices are currently a popular software architecture style. After the underlying common technical services and middle-end business service capabilities are available, upper-layer applications should be quickly built based on these services. However, it is impossible to simply call a service for all scenarios. When there are certain business rules that need to be processed, it often involves the invocation of multiple services, and basic data processing is also involved in the middle, so that logical judgment can be completed.

If you let the front-end application handle this combination, you need to write a lot of script code, and you need to adjust it from time to time, and there is a problem of external leakage of common domain service logic. Second, in the scenario where the front-end and back-end are separated, the front-end does not care about the complex back-end logic.

Application service orchestration is the process of logically combining basic business services according to certain business rules, and providing an encapsulated combined service interface to the front end.

Application service orchestration can perform visual business process orchestration to reduce these repetitive and non-technical front-end scripts and improve the visualization of service call logic.

Patent document CN107343018B (application number: 201710005170.2) discloses a PaaS cloud platform application service arrangement method and system. The steps of the method are as follows: S1. The user selects the specific service that needs to be arranged in the Catalog service list according to the business; S2. The necessary parameters are set; S3, the platform interface is called after writing the service in sequence, and the arrangement file is transferred to the platform; S4, the platform arranges the service according to the arrangement file of different services.

Contents of the invention

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.

According to the present invention, an application arrangement service system based on the Conductor framework includes:

Data layer: the database and data table that store the data required for the application orchestration process;

Logical arrangement layer: By assembling multiple node modules to form service interfaces for different business scenarios;

Application layer: access the corresponding service interface, database and/or data table through the page, so as to provide the corresponding orchestration service;

The node modules are different node templates that have been packaged, and are the smallest execution unit in the orchestration service, carrying execution logic.

Preferably, the logical orchestration layer includes: using the Netflix Conductor orchestration engine to construct a workflow, and reassembling the functions of the node modules based on the constructed workflow.

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.

Preferably, it needs to rely on the underlying resource configuration when performing orchestration services;

The underlying resource configuration includes certificates, encryption and decryption rules, and database connection passwords.

Preferably, different data operation permissions are set on the data layer; the application layer uses corresponding data based on the corresponding data operation permissions.

Preferably, access rights are set for the orchestration service.

Preferably, based on the underlying framework capabilities of the conductor, each time the orchestration service is called by an external application, the corresponding service ID will be formed to mark the data execution status of this call; for each call, the service monitoring will monitor the call result; the corresponding service will be displayed in detail call records and execution results;

Monitoring will monitor each node under the service at the same time; monitor the execution of the node through the detailed log information of the node operation.

According to the present invention, an application orchestration service method based on the Conductor framework includes:

Step S1: the data layer stores the database and data table for the data required by 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, so as to provide the corresponding orchestration service;

The node modules are different node templates that have been packaged, and are the smallest execution unit in the orchestration service, carrying execution logic.

Preferably, the logic arrangement layer includes: using Netflix Conductor arrangement engine to construct a workflow, and based on the constructed workflow, the functions of the node modules are reassembled;

The node template includes: start/end node, judgment node, call node, wait node, output node, polling node and parallel start/end node.

Preferably, based on the underlying framework capabilities of the conductor, each time the orchestration service is called by an external application, the corresponding service ID will be formed to mark the data execution status of this call; for each call, the service monitoring will monitor the call result; the corresponding service will be displayed in detail call records and execution results;

Monitoring will monitor each node under the service at the same time; monitor the execution of the node through the detailed log information of the node operation.

Compared with the prior art, the present invention has the following beneficial effects:

1. Based on the conductor open source framework, the present invention provides application services applicable to upper-layer page scenarios, achieves low-code effects by abstracting multiple types of standard processing nodes, and realizes the encapsulation of bottom-level processing logic to facilitate business applications;

2. The present invention can assemble multi-type node logic through a visual interface to realize service call logic in different business scenarios;

3. By abstracting and encapsulating nodes into different standardized execution logics, the present invention can quickly complete data acquisition schemes in different ways such as http, HTTPS, and data access; integrate various regular rules, inequality configuration, and operation logic processing, etc., through The interface can be configured and used directly, without the need for code development every time;

4. The present invention supports the user to directly construct the service process through the interactive mode of dragging and dropping the canvas, and the interface is friendly and easy to use.

Description of drawings

Other characteristics, objects and advantages of the present invention will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

Figure 1 is a schematic diagram of an application orchestration service system based on the Conductor framework.

Figure 2 is a schematic diagram of the application orchestration service system based on the Conductor framework

Figure 3 is a flowchart of node execution.

Detailed ways

The present invention will be described in detail below in conjunction with specific embodiments. The following examples will help those skilled in the art to further understand the present invention, but do not limit the present invention in any form. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

Example 1

According to the present invention, an application arrangement service system based on the Conductor framework includes:

Data layer: the database and data table that store the data required for the application orchestration process;

Logical arrangement layer: By assembling multiple node modules to form service interfaces for different business scenarios;

Application layer: access the corresponding service interface, database and/or data table through the page, so as to provide the corresponding orchestration service;

The node modules are different node templates that have been packaged, and are the smallest execution unit in the orchestration service, carrying execution logic.

Specifically, the logical orchestration layer includes: using the Netflix Conductor orchestration engine to construct a workflow, and reassembling the functions of the node modules based on the constructed workflow.

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.

Specifically, it needs to rely on the underlying resource configuration when orchestrating services;

The underlying resource configuration includes certificates, encryption and decryption rules, and database connection passwords.

Specifically, different data operation permissions are set on the data layer; the application layer uses corresponding data based on the corresponding data operation permissions.

Specifically, set access rights to the orchestration service.

Specifically, based on the capabilities of the underlying framework of the conductor, each time the orchestration service is called by an external application, it will form the corresponding service ID to mark the data execution status of this call; for each call, the service monitoring will monitor the call result; the corresponding service will be displayed in detail call records and execution results;

Monitoring will monitor each node under the service at the same time; monitor the execution of the node through the detailed log information of the node operation.

According to the present invention, an application orchestration service method based on the Conductor framework includes:

Step S1: the data layer stores the database and data table for the data required by 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, so as to provide the corresponding orchestration service;

The node modules are different node templates that have been packaged, and are the smallest execution unit in the orchestration service, carrying execution logic.

Specifically, the logic arrangement layer includes: using the Netflix Conductor arrangement engine to construct a workflow, and reassembling the functions of the node modules based on the constructed workflow;

The node template includes: start/end node, judgment node, call node, wait node, output node, polling node and parallel start/end node.

Specifically, based on the capabilities of the underlying framework of the conductor, each time the orchestration service is called by an external application, it will form the corresponding service ID to mark the data execution status of this call; for each call, the service monitoring will monitor the call result; the corresponding service will be displayed in detail call records and execution results;

Monitoring will monitor each node under the service at the same time; monitor the execution of the node through the detailed log information of the node operation.

The essence of the nodes corresponds to the micro-service architecture system, and the specific execution logic is disassembled into services that can be independently output and provided. The essence of centralization is an aggregated service item that can solve a single business scenario. Service orchestration can form the corresponding mid-stage capability through the combination and orchestration of multiple nodes; the present invention quickly responds to different scenario demands of the business layer from bottom to top by combining the micro-service architecture and mid-stage capability.

Example 2

Embodiment 2 is a preferred example of embodiment 1

According to the present invention, an application service orchestration system based on Netflix Conductor open-source micro-service orchestration engine design and integrated front-end application operation interface and monitoring system is provided. As shown in Figure 1-2, the core of the system includes a three-layer structure: data layer , logical orchestration layer and application layer.

The data layer refers to a database and a data table that store data required by the application orchestration process. The data layer contains three basic data modules: application data module, service orchestration module, and resource parameter module.

The logical orchestration layer refers to mainly using the Netflix Conductor orchestration engine to build a workflow, and realize multiple template applications through the secondary assembly of the function of the node (Task). Specifically, it can be abstracted as defining each interface capability as a separate node template, each node will have corresponding data processing capabilities, and service interfaces for different business scenarios can be formed by assembling multiple nodes.

The application layer refers to the front-end application that is actually operated by the user and needs to perform account login control. The application layer provides the ability to access the corresponding logical layout layer and data layer by providing corresponding pages.

The service flow (WorkFlow) module refers to the overall functional module including the front-end visual interface provided to users for service process arrangement and management. The module provides multiple types of encapsulated nodes (TASK) built-in, supports the definition of different microservice interfaces through node (Task) templates, and completes the assembly through the canvas application to realize the creation of service workflows. The packaged services can be directly exposed to external applications for use.

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 piece of execution logic, such as sending HTTP requests. This application orchestration system mainly encapsulates and gives 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 through the assembly of nodes (TASK).

The resource (Source) module refers to the configuration of the underlying resources that are relied upon for service orchestration. The underlying resources that depend on can be mainly divided into the following categories: certificates, encryption and decryption rules, and database connection passwords

Access permission (Access) refers to the permission to control whether a user can access an application in the software (or website) after logging in. Specifically, when a user does not have access rights to an application, the application's entrance will be hidden or unclickable for the user.

Data permission (Data) refers to the permission to control the range of data that a user can operate (add, delete, modify, check) in an application. In an application involving data permissions, when a user does not have permission for a piece of data, the piece of data will be hidden or inoperable to the user.

The system completes an application service orchestration process including:

Step 1: Open the system usage authority, allowing customers to log in to the corresponding background for configuration operations.

Step 2: Create a service and complete the service basic information, including: service basic information definition, service request parameter definition, and service return parameter definition.

Step 3: Construct 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.

Step 4: Complete the overall logic debugging and release of the service through the debugging function. The published services will be uniformly encapsulated into a restful interface to provide external services, which can be called by application-side services.

The service can be extended to define service basic information, service debugging, and service monitoring. As a higher-level encapsulation of multiple nodes, services can be directly invoked by upper-level application services. Logical processing and return can be performed according to the application service scenario. At the same time, it has the corresponding debugging ability to test and debug in conjunction with business scenarios to ensure that the processing logic reviews business demands:

The definition of basic service information includes the definition of service name, service code, service type, request method, message format, request parameters, and return parameters. The basic information defines how the encapsulated service will be provided externally.

Service debugging: The system provides debugging capabilities, which are similar to postman initiating simulation calls to debug services, and confirm that the services that have been orchestrated return corresponding processing results according to business requirements.

Service monitoring: Based on the capabilities of the underlying framework of the conductor, every time a service is called by an external application, the corresponding service ID will be generated to mark the data execution status of this call. For each call, the service monitor will monitor the result of the call. Display the call records and execution results of the corresponding services in detail.

Monitoring will also monitor each node under the service. Monitor node execution by printing detailed log information of node operation.

The node can be expanded into different node templates. By encapsulating different execution logics into corresponding templates, the corresponding capabilities can be used directly. 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, it will determine how to execute the logic corresponding to the node and output the corresponding results according to the process shown in Figure 3;

The encapsulation core node template is detailed as follows:

Call node: data acquisition and processing node. Node encapsulation supports the ability to access data sources such as HTTP, HTTPS, web sercive, socket, databaseToAPI, etc. 1. It supports directly establishing a docking mechanism with downstream data sources by configuring the request method, request format, request address, encryption and decryption rules, certificates and other information of the corresponding data source to obtain corresponding data. 2. For the data source acquisition results, secondary processing can be carried out to meet the upstream business demands (including assignment operation, field mapping, code value mapping, and operation processing). 3. Handling of exception mechanism. The data acquisition processing node can configure the exception handling mechanism. It supports defining the retry mechanism when the downstream interface is abnormal, including parameters such as timeout mechanism, timeout period, and number of retries.

Among them, DatabaseToApi supports the mode of directly configuring and accessing database tables, performs combined query processing on multiple database tables to obtain corresponding parameter results, and encapsulates the results into restful standard interfaces for service provision.

Judgment node: processing branch judgment logic based on different data results. Through the configuration of conditional expressions, conditions such as AND or NOT, greater than, less than, equal to, etc. are supported to judge the parameter value and then go further with different processing logic.

Concurrent start/end node: perform concurrent data acquisition processing. Multiple call nodes can be configured under the concurrent node to implement parallel data acquisition and processing mechanisms. Support synchronous processing and result output of multiple data sources.

Transformation node: configuration of data mapping relationship. Code value conversion, data format conversion, field name conversion, etc. can be performed.

Polling node: Asynchronous data source acquisition processing mechanism. Define the trigger mechanism and processing logic of the scheduled task.

The resource module can expand the overall management of underlying data resources including databases, servers, certificate management, and data source interfaces, and expand the acquisition and processing capabilities of multiple types of underlying data sources:

The database can be configured with parameters such as database name, database type (supporting access to oracle, MQL, and PG relational databases), user name, password, and JDBC URL. Complete connection access to the underlying database tables.

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.

Certificate management supports the calling of the HTTPS interface by adding certificates.

The data permissions can be further combined with user roles to encapsulate different system operation roles, and each role will correspond to specific operable data permissions. Ensure that the system is used under a mechanism with corresponding authority control.

Example 3

Embodiment 3 is a preferred example of embodiment 1 and/or embodiment 2

A docking solution for fund over-the-counter trading system provided according to the present invention

The investment management system refers to the asset management system owned by the investment manager, and the general asset management system is a system deployed within the financial institution. Investment managers use this system to issue trading orders.

The fund sales system refers to the system connecting the fund sales infrastructure with investment institutions, which is responsible for executing inquiries, transactions and other instructions issued by the investment management system, and providing fund investment institutions with the execution results of fund transaction orders required for business development according to the agreement. information.

Investment managers, that is, use the investment management system to issue trading orders. And use the investment management system to track the overall transaction link.

The end-to-end connection of the system refers to the data interaction between the investment management system and the fund sales system directly through the API interface. Over-the-counter fund transactions can be carried out without changing the original interface usage habits of investment managers.

In the context of the comprehensive digital reform of financial institutions, it has become a standard solution to complete the full link of OTC fund transactions through system docking. Generally, financial institutions will connect 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 is expected to be able to complete the access of multiple sales systems through a set of standard interfaces. Through the application orchestration service, the interfaces provided by different sales organizations can be standardized and encapsulated through the service flow module, and the standard interface request method, request format, request input parameters, request output parameters and other information can be formulated.

When the interface has special processing and changes of certain parameters, it can be edited and adjusted through the application layout system to reduce adjustments at the code level.

Those skilled in the art know that, in addition to realizing the system, device and each module thereof provided by the present invention in a purely computer-readable program code mode, the system, device and each module thereof provided by the present invention can be completely programmed by logically programming the method steps. The same program is implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers, among others. Therefore, the system, device and each module provided by the present invention can be regarded as a hardware component, and the modules included in it for realizing various programs can also be regarded as the structure in the hardware component; A module for realizing various functions can be regarded as either a software program realizing a method or a structure within a hardware component.

Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art may make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. In the case of no conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims (10)

1. An application orchestration service system based on the Conductor framework, characterized in that it comprises: Data layer: the database and data table that store the data required for the application orchestration process; Logical arrangement layer: By assembling multiple node modules to form service interfaces for different business scenarios; Application layer: access the corresponding service interface, database and/or data table through the page, so as to provide the corresponding orchestration service; The node modules are different node templates that have been packaged, and are the smallest execution unit in the orchestration service, carrying execution logic. 2. The application orchestration service system based on the Conductor framework according to claim 1, wherein the logical orchestration layer includes: using the Netflix Conductor orchestration engine to construct a workflow, and performing two functions of the node module based on the constructed workflow secondary assembly. 3. The application orchestration service system based on the Conductor framework according to claim 1, wherein the node template includes: start/end node, judgment node, call node, wait node, output node, polling node and parallel start/end node. 4. The application orchestration service system based on the Conductor framework according to claim 1, wherein it needs to rely on underlying resource configuration when performing orchestration services; The underlying resource configuration includes certificates, encryption and decryption rules, and database connection passwords. 5. The application orchestration service system based on the Conductor framework according to claim 1, wherein different data operation permissions are set on the data layer; the application layer uses corresponding data based on the corresponding data operation permissions. 6. The application orchestration service system based on the Conductor framework according to claim 1, characterized in that access rights are set for the orchestration service. 7. The application orchestration service system based on the Conductor framework according to claim 2, characterized in that, based on the underlying framework capabilities of the conductor, each time the orchestration service is called by an external application, the corresponding service ID will be formed to mark the data execution status of this call ;For each call, the service monitoring will monitor the call result; display the call record and execution result of the corresponding service in detail; Monitoring will monitor each node under the service at the same time; monitor the execution of the node through the detailed log information of the node operation. 8. An application orchestration service method based on the Conductor framework, characterized in that it comprises: Step S1: the data layer stores the database and data table for the data required by 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, so as to provide the corresponding orchestration service; The node modules are different node templates that have been packaged, and are the smallest execution unit in the orchestration service, carrying execution logic. 9. The application orchestration service method based on the Conductor framework according to claim 8, wherein the logic orchestration layer includes: using the Netflix Conductor orchestration engine to construct a workflow, and performing two functions of the node module based on the constructed workflow secondary assembly; The node template includes: start/end node, judgment node, call node, wait node, output node, polling node and parallel start/end node. 10. The application orchestration service method based on the Conductor framework according to claim 9, characterized in that, based on the capabilities of the underlying framework of the conductor, each time the orchestration service is called by an external application, the corresponding service ID will be formed to mark the data execution status of this call ;For each call, the service monitoring will monitor the call result; display the call record and execution result of the corresponding service in detail; Monitoring will monitor each node under the service at the same time; monitor the execution of the node through the detailed log information of the node operation.

Images