Business development execution method and system based on analysis engine component

Abstract

The invention provides a service development and execution method and system based on an analysis engine component, and relates to the technical field of software development, the analysis engine component comprises four levels, namely an interface layer, a logic arrangement layer, a logic unit layer and a solidification bottom layer implementation layer from top to bottom in sequence, and the method comprises the specific steps that based on the level design of the analysis engine component, the logic unit layer and the solidification bottom layer implementation layer are designed; splitting a target service into a plurality of logic units, and performing development implementation of the target service through an interface layer according to interfaces published by a logic arrangement layer and a logic unit layer; when the developed target business is executed, the interface issued by the logic arrangement layer and the logic unit layer is called through the interface layer, and the interface executes bottom layer operation through the solidification bottom layer implementation layer; according to the invention, a newly defined architecture mode is utilized to construct an analysis engine component comprising four levels, layered development and analysis execution are carried out on the target business, and the reusability, maintainability and robustness of codes are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of software development, and in particular relates to a business development execution method and system based on a parsing engine component. Background Art

[0002] The statements in this section merely provide background information related to the present invention and do not necessarily constitute prior art.

[0003] A large number of database operations are required during the software development process, including DML and DDL operations. The code duplication rate is particularly high and the reusability is poor, making it impossible to uniformly modify the common logic. For the same technical problem, different developers may use different technologies in different business modules, resulting in a large number of technologies being used to solve the same type of problem in the software system. In addition, the coding levels of different developers vary, resulting in insufficient code robustness.

[0004] Therefore, the existing business development methods have poor code reusability, maintainability, and robustness. Summary of the invention

[0005] In order to overcome the shortcomings of the above-mentioned prior art, the present invention provides a business development and execution method and system based on a parsing engine component, which utilizes a newly defined architecture to construct a parsing engine component consisting of four levels, and performs layered development and parsing execution on the target business, thereby improving the reusability, maintainability and robustness of the code.

[0006] To achieve the above objectives, one or more embodiments of the present invention provide the following technical solutions:

[0007] A first aspect of the present invention provides a business development execution method based on a parsing engine component.

[0008] A business development execution method based on a parsing engine component, wherein the parsing engine component includes four layers, namely, an interface layer, a logic arrangement layer, a logic unit layer, and a solidified bottom layer implementation layer from top to bottom. The specific steps of the method are as follows:

[0009] Based on the hierarchical design of the parsing engine components, the target business is divided into multiple logical units. According to the interfaces published by the logical orchestration layer and the logical unit layer, the target business is developed and implemented through the interface layer.

[0010] When executing the developed target business, the interface layer calls the interfaces published by the logic orchestration layer and the logic unit layer, and the interfaces perform the underlying operations by solidifying the underlying implementation layer.

[0011] Furthermore, each of the four levels includes several interfaces for implementing different encapsulations, specifically:

[0012] The solidified underlying implementation layer is used to encapsulate underlying operations, including data operation query languages and commands;

[0013] The logic unit layer is used to encapsulate common logic units and call the underlying operations encapsulated in the solidified underlying implementation layer by passing parameters;

[0014] The logic orchestration layer is used to encapsulate common logic unit orchestrations to obtain the orchestration information of logic units and the input and output parameter information of their orchestrations;

[0015] The interface layer is used to encapsulate a number of interfaces published by the logic orchestration layer and the logic unit layer, and interfaces that are not published cannot be called.

[0016] Further, the interface layer encapsulates and defines a number of interfaces published by the logic orchestration layer and the logic unit layer, including defining the input and output parameters of the interfaces.

[0017] Further, the logic orchestration layer contains an executor and orchestration chain information. The executor is used to execute the orchestration chain information, and the orchestration chain information stores the orchestration information of logic units and the input and output parameter information of their orchestrations.

[0018] Further, the logic unit layer is based on the solidified underlying implementation layer to implement business units with business logics, including preset solidified relational database operations, preset extension operations, and extended solidified operations.

[0019] Further, the solidified underlying implementation layer includes relational database solidification, api interface call solidification, and solidified code extension.

[0020] Further, the splitting of the target business into multiple logic units is specifically as follows:

[0021] According to the operation classifications included in the target business, the logic units are split, where the operation classifications include database operations, branch judgments, and api calls.

[0022] The second aspect of the present invention provides a business development execution system based on a parsing engine component.

[0023] A business development execution system based on a parsing engine component, the parsing engine component includes four levels, from top to bottom are the interface layer, the logic orchestration layer, the logic unit layer, and the solidified underlying implementation layer. The system includes:

[0024] A development module, configured to: based on the hierarchical design of the parsing engine component, split the target business into multiple logic units, and based on the interfaces published by the logic orchestration layer and the logic unit layer, implement the development of the target business through the interface layer;

[0025] The execution module is configured to: when executing the developed target business, call the interface published by the logic orchestration layer and the logic unit layer through the interface layer, and the interface performs the underlying operation by solidifying the underlying implementation layer.

[0026] A third aspect of the present invention provides a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements the steps in a business development execution method based on a parsing engine component as described in the first aspect of the present invention.

[0027] The fourth aspect of the present invention provides an electronic device, including a memory, a processor, and a program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps in a business development execution method based on a parsing engine component as described in the first aspect of the present invention are implemented.

[0028] One or more of the above technical solutions have the following beneficial effects:

[0029] The present invention introduces a parsing engine component for parsing and executing data operation query languages ​​and commands, which brings the following advantages:

[0030] (1) Reusability: The concept of logic unit is introduced to provide reusable business logic. Only the parameters passed in need to be changed.

[0031] (2) Easy expansion: It can be expanded horizontally through AOP and mybatis interceptors; it can also be expanded vertically by adding services for one or some actions; this expansion method is similar to the plug-in method, and developers only need to simply understand the interface of the original business to expand according to the expansion specification; it can achieve zero or minimal intrusion on the original business code; introduce business orchestration functions, and through business orchestration, mature businesses or implementations can be functionally solidified;

[0032] (3) Configurable: Combined with Tianfu, business actions are configurable, action parameters are configurable, and extended business logic is configurable;

[0033] (4) Easier to learn: There are fewer data tables than the original architecture, which reduces the learning difficulty and provides clear architectural hierarchy logic.

[0034] (5) Componentization: The entire architecture is divided into components to reduce coupling.

[0035] (6) Solidification: Provides original solidification logic, such as single-table model, master-child model and other relational solidification logic; business orchestration can perform solidification operations; other extended businesses and complex business logic implementations can perform solidification operations.

[0036] Advantages of additional aspects of the present invention will be given in part in the following description, and in part will become obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0038] Figure 1 This is a flow chart of the method of the first embodiment.

[0039] Figure 2 This is a diagram of the parsing engine architecture of the first embodiment. DETAILED DESCRIPTION

[0040] It should be noted that the following detailed descriptions are illustrative and are intended to provide further explanation of the present application. Unless otherwise specified, all technical and scientific terms used in the present invention have the same meanings as those commonly understood by those skilled in the art to which the present application belongs.

[0041] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprise" and / or "include" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0042] Terminology explanation:

[0043] Data source metadata management: mainly data source connection information management, as well as metadata management of data tables, including relational and non-relational, and information calls throughout the entire parsing engine architecture.

[0044] Api connector management: mainly external api connection management, maintaining connector basic information, authentication interface details, and connection interface details.

[0045] Embodiment 1

[0046] In one embodiment of the present disclosure, a business development execution method based on a parsing engine component is provided. The parsing engine component includes four layers, which are, from top to bottom, an interface layer, a logic arrangement layer, a logic unit layer, and a solidified bottom layer implementation layer. Each of the four layers includes several interfaces for implementing different encapsulations, specifically:

[0047] The solidified bottom layer implementation layer is used to encapsulate bottom layer operations, including data operation query language and commands;

[0048] The logic unit layer is used to encapsulate commonly used logic units and call the underlying operations encapsulated in the solidified underlying implementation layer by passing parameters;

[0049] The logic arrangement layer is used to encapsulate commonly used logic unit arrangements, obtain arrangement information of the logic unit and input and output parameter information of the arrangement;

[0050] The interface layer is used to encapsulate several interfaces published by the logic orchestration layer and the logic unit layer. Unpublished interfaces cannot be called.

[0051] Furthermore, the interface layer encapsulates and defines several interfaces published by the logic orchestration layer and the logic unit layer, including defining input parameters and output parameters of the interfaces.

[0052] Furthermore, the logic orchestration layer includes an executor and orchestration chain information. The executor is used to execute the orchestration chain information. The orchestration chain information stores the orchestration information of the logic unit and the input and output parameter information of the orchestration.

[0053] Furthermore, the logic unit layer is based on the solidified underlying implementation layer to implement business units with business logic, including preset solidified relational database operations, preset extended operations and extended solidified operations.

[0054] Furthermore, the solidification of the underlying implementation layer includes relational database solidification, API interface call solidification and solidification code extension.

[0055] Based on the above analysis engine, business development and execution are carried out, such as Figure 1 As shown, the following steps are included:

[0056] Step S1: Based on the hierarchical design of the parsing engine component, the target business is divided into multiple logical units, and the target business is developed and implemented through the interface layer according to the interfaces published by the logical orchestration layer and the logical unit layer;

[0057] Furthermore, the target business is split into multiple logical units, specifically:

[0058] The logical units are split according to the operation categories included in the target business, wherein the operation categories include database operations, branch judgments, and API calls.

[0059] Step S2: When executing the developed target business, the interface layer calls the interface published by the logic orchestration layer and the logic unit layer, and the interface performs the underlying operation by solidifying the underlying implementation layer.

[0060] The following is a detailed description of the implementation process of a business development execution method based on a parsing engine component in this embodiment.

[0061] The parsing engine component is a newly defined architecture that is used to parse and execute data operation query languages ​​and commands. The specific technical issues that need to be solved are as follows:

[0062] How to make code reusable?

[0063] Make it easy to expand;

[0064] Freely configurable;

[0065] Easier to learn and get started;

[0066] Componentization: The underlying code technology is componentized;

[0067] Solidifiable, separation of underlying technology and business.

[0068] Based on the consideration of the above problems, this embodiment provides a specific example, using the Tianfu platform as a development platform, combined with the parsing engine component, to develop and execute the target business; Figure 2 As shown, the parsing engine components mainly include the interface layer, the logic orchestration layer, the logic unit layer, and the solidified underlying implementation layer. The complex business is divided into various logical units. The logic orchestration layer orchestrates the split logical units and implements complex business functions through orchestration.

[0069] Complex business includes database operations, branch judgments, API calls and other operation categories. When split into logical units, they are split into different logical units according to the categories included in the complex business. The logical units only perform execution at the business level. The specific execution of classified operations is implemented by solidifying the underlying implementation layer. The solidified underlying implementation layer differentiates operations of different categories, including database operations, BPM (workflow operations), and API call-related operations.

[0070] Each layer contains input parameters, output parameters, and method names, and is called from top to bottom. There will be no cross-layer calls. During the calling process, the parameters of the lower layer are encapsulated through parameter binding before the call is made.

[0071] The parsing engine extends other business method operations by implementing the interfaces exposed by the solidified underlying implementation layer and the logic unit layer. During the startup process, the parsing engine saves the interface methods, input parameters, and output parameters of the solidified underlying implementation and the logic unit layer in the database, and orchestrates the corresponding logic unit nodes in the logic orchestration layer. During the execution process, the logic orchestration layer executes the logic unit nodes through the executor, and the logic unit executes operations of different categories through the solidified underlying implementation layer.

[0072] Among them, the logical unit is a business-related method, and the solidified underlying implementation layer has no business-related attributes. In other words, business and technology are separated. Business-related operations refer to the logical unit layer, and technology-related implementations are implemented through the solidified underlying implementation layer. Simply put, the logical unit layer is a single business method or capability, and the solidified underlying implementation layer is the technical implementation that supports the business.

[0073] The following is a detailed description of each layer:

[0074] 1. Interface layer

[0075] It is mainly published (i.e. exposed) to other system-callable interfaces or business service interfaces, that is, to expose the complex business logic of the orchestration to other systems or business systems through interfaces for calling. The business capability interface of the logic orchestration layer is not published to the interface layer and cannot be called by other business systems.

[0076] The interface layer stores the interface execution information (methods, input and output parameters) published by the logic orchestration layer. When the interface is called, it queries the relevant information of the logic orchestration layer based on the interface execution information for execution. When publishing the interface, the business interface of the logic orchestration layer is published to the interface layer; the business system calls the interface layer method and then calls the logic of the logic orchestration layer.

[0077] The functions of the interface layer are summarized as follows:

[0078] (1) Provide the business system with interface declarations of each model and the business methods provided by the model;

[0079] (2) Providing a parsing engine to generate a callable interface for the business system;

[0080] (3) Interface orchestration layer parameter binding: This is mainly to perform parameter mapping and value assignment when the interface layer calls the logic orchestration layer, and to generate the input parameter information of the interface to be called.

[0081] 2. Logical Orchestration Layer

[0082] Complex business logic is orchestrated through the (3) logic unit layer. If the complex business logic constructed subsequently is universal, this complex logic can be solidified into the (3) logic unit layer as a logic unit, and this complex business logic can be converted into a logic unit layer method, which can be used for calling the logic orchestration layer. The logic orchestration layer can configure the operation mode of the global pre-interceptor and post-interceptor for expansion.

[0083] The logical orchestration layer contains the executor and the XML information of the orchestration chain (or the database saves the connector information). The executor is mainly used to execute the information of the orchestration chain. The information of the orchestration chain mainly saves the orchestration information of the logical unit and its input and output parameter information.

[0084] Executor: Executes the orchestration chain information, mainly including the input parameter context and output parameter context, and executes the business logic of the logical orchestration.

[0085] Orchestration chain XML information: complex business chain information orchestrated by logical units, which is persisted in XML or database, and records the complex logic including the input and output parameters of the logical units and their orchestration layer.

[0086] The complex business logic constructed by the logic orchestration layer can be solidified into a solidified orchestration service unit in the logic unit through solidification. When building complex business functions, the logic unit solidification orchestration service unit can be directly used. It can also be solidified to the solidified underlying implementation layer in the form of code, and then the solidified code is loaded into the logic unit layer solidification logic orchestration service during the platform startup process.

[0087] 3. Logical Unit Layer

[0088] The logical unit is the basic unit for building logical orchestration. During execution, the logical unit requires (4) support from the solidified underlying implementation layer, such as the mapper file for solidified relational database operations, custom sqlmapper files, API calls, API authentication processing, the underlying execution operations of non-relational databases, BPM built-in method services, and solidified business code support.

[0089] The <Logical Unit Layer> is mainly divided into the following categories:

[0090] 1) Pre-set factorized relational database operations: support single-table and multi-table general database operation methods, support multiple association methods for multiple tables, and dynamically process return values ​​and query conditions.

[0091] 2) Preset extended operations (following the extended specifications): Extend the business methods related to the solidified layer, such as BPM, custom SQL, API operations, and non-relational database operations. The extension here is for non-user extensions.

[0092] 3) Extended and solidified business component operations: mainly the solidified operations of logically orchestrated general business and the extension of its orchestration logic unit. The extension for users here mainly includes: general business logic solidification and logic unit component extension. Users implement the corresponding interface and then solidify the general orchestration logic into <general business logic solidification> by writing code. It mainly includes the following general business logic operations: master-sub-model, single-table workflow model, master-sub-workflow model, solidification of general complex servi ce, script processing, and solidification of logic orchestration servi ce;

[0093] The components of the logical unit are divided according to different businesses. The components mainly include: common business components, conditional components, front components, post components, asynchronous execution components, transaction components, exception handling components, and other extended components.

[0094] The logic unit layer is mainly the basic unit for building logical orchestration, which includes preset solidified relational database operations, preset extension operations, and extended solidified business component operations - general business logic solidification, logic unit component extension, and preset API operations.

[0095] In fact, the logic unit already has business-related functions, such as solidifying the newly added method of single-table operations. At this time, business-related information has been assigned to the logic unit, such as solidifying the newly added method of the user model single table. The assigned business function is the business logic of the user model.

[0096] The data of the logic unit is saved when the interface is released. When constructing the orchestration information, the corresponding preset operation information is selected, the corresponding business information is selected, and a logic unit is generated with the business information of the bottom layer of the solidified layer. In other words, the logic unit is the business unit that gives the bottom layer of the solidified layer business logic.

[0097] Preset solidified relational database operations: It is a common business component in the logical unit component extension, mainly including single-table and multi-table association-related preset operations.

[0098] Preset extension operations: They are common business components in the logical unit component extension, mainly including bpm operations, custom extensions, custom sql, and non-relational operations.

[0099] Preset API operation: It is a common business component in the logical unit component extension, which calls the logic related to the interface list in the API connector.

[0100] General business logic solidification: It is a common business component in the extension of the logic unit component. It solidifies the commonly used and common operations on the current platform, including single-table O-type, master-sub-model, single-table workflow model, master-sub-table workflow model, and API model.

[0101] Solidified general complex service: It is a common business component in the extension of the logical unit component. It solidifies the complex business through code and then saves the class name, method name, and input and output parameters related to the code in this type.

[0102] Solidified logic orchestration service: It is a common business component in the extension of the logic unit component. The chain name and method name of the common logic chain of the orchestration layer are saved in this type.

[0103] Logical unit component extension: mainly to enrich the classification of logical units for logical arrangement. In fact, the business units described above are just ordinary business components in the logical unit component. Logical unit extension also includes conditional components, pre-components, post-components, asynchronous execution components, transaction components, exception handling components, and other extension components.

[0104] 4. Solidify the underlying implementation layer

[0105] This layer is mainly a technical implementation layer and does not have business functions. It extracts the passing technology of the logical unit layer and encapsulates the solidified underlying implementation layer / support layer, including preset solidified relational database operations, preset extended operation implementation layer, extended solidified operation implementation layer, code extension, and other custom extensions, including:

[0106] Preset and solidify relational database operations: implement relational database mapper, customize mapper, solidify relational database operation mapper by dynamically passing parameters, and the logic unit layer selects different mappers according to the corresponding operation entity to perform the underlying operations of the database.

[0107] Preset extension implementation layer: BPM, API call, other custom extensions, non-relational operations, etc. Developers use this layer to extend and solidify the underlying implementation layer. For example, the external API call logic is extended through this layer, which mainly implements API calls and authentication interface calls. The API interface and authentication interface calls are called through the RMI technology component.

[0108] Extended and solidified operation implementation layer: Users extend and solidify the underlying implementation layer / support layer through this layer. The master-sub-model, single-table model, single-table workflow, master-sub-workflow model, and solidified general complex business are all extended in this way.

[0109] During logic orchestration, if there is no business unit that meets the requirements in the logic unit layer, the logic unit layer is generated by binding the solidified underlying implementation and business-related parameters. In simple terms, solidified underlying implementation layer + business parameters = logic unit layer.

[0110] There are currently three ways to implement solidification of the underlying layer: relational database solidification, API interface call solidification, and solidification code extension. The solidification code extension includes master-sub model, single-table workflow model, single-table model, master-sub table workflow model, etc. The following is a detailed description of the implementation method:

[0111] 1. The underlying implementation method of relational database solidification

[0112] (1) Through data-related add, delete, modify and query operations, the SQL is split into table entities, column entities, set entities, order entities, where entities, join entities and on entities. Through this entity combination, the corresponding query entity, update entity, delete entity and insert entity are obtained. The solidifiable code in the corresponding query-related operations is solidified in the solidified bottom layer, and the dynamic part is passed through the encapsulation parameter method to dynamically execute the curd operations of different tables and different fields.

[0113] (2) Analyze and obtain the corresponding mapper and the methods and input and output parameters in the mapper. The solidified preset operations are divided into single-table and multi-table operations. The preset methods, prevention parameters and return values ​​are fixed. The methods and parameters in this code will be saved in the table of the solidified layer.

[0114] The Mapper solidifies the upper layer and there is an implementation of the service corresponding to the mapper. The data stored in the database table of the solidification layer are the methods and parameters of the exposed service.

[0115] 2. How to implement the API interface call solidification

[0116] The api model mainly includes the api connector and the api calling process. The api connector mainly records the authentication information, interface list information, parameter information of the authentication information and interface list, HTTP configuration information, and public variable information required in the api calling process.

[0117] Authentication information: When calling a third-party API interface, authentication is required. Only after obtaining legal credentials can the API interface information be called. The authentication information contains authentication-related information, such as authentication type and authentication method.

[0118] Interface list information: The interface list information that can be called through the connector, and the interface methods exposed by the third-party system.

[0119] Parameter information: record the input parameters of the calling interface list and authentication interface.

[0120] http configuration input parameters: when calling the third party, configure and bind the input parameters, for example, whether the interface input parameters should be bound to the body or query scope.

[0121] Public variable information: only for the public variables of the api connector, such as the token information returned by the authentication interface. This token information is required when calling the interface list. At this time, it can be obtained directly in the public variables through expressions in the http configuration.

[0122] Authentication Template: The API model pre-sets some common authentication methods for third parties, solidifies these authentication methods to generate an authentication template, and the authentication template includes the authentication type, authentication method, and its template name.

[0123] In the API diagram, it can be clearly seen that the API connector includes connector basic information, connection template, authentication interface details, input and output parameters of the authentication interface, connector API interface, input and output parameters of the connection API interface, and input parameters of the interface HTTP settings. Among them, the authentication interface details, input and output parameters of the authentication interface, connector API interface, and input and output parameters of the connection API interface are stored in the tables at the solidified underlying implementation layer. When the interface is released, the data is saved to the logical unit layer.

[0124] The API call process is implemented through the RMI technology component. The RMI technology component is a Java HTTP client framework that can bind all HTTP request information (including URL, Header, and Body information) to the custom Interface method, and can send HTTP requests by calling the local interface method. The RMI technology component generates a specific implementation class through the dynamic proxy method for the defined interface, then organizes and validates the HTTP request information, binds dynamic data, converts the data form, performs SSL signature verification, calls the backend HTTP API (such as httpclient and other APIs) to execute the actual request, waits for the response, retries in case of failure, and converts the response data to the Java type, etc., to achieve unified processing logic through the implementation class of the dynamic proxy. When the request sender calls this interface, it is actually calling the implementation class of the dynamic proxy.

[0125] 3. Implementation Method for Solidified Code Extension

[0126] The solidified code extension includes master-slave models, single-table workflow models, single-table models, master-slave table workflow models, etc.

[0127] Single-Table Model: Supports the single-table operation model and provides solidified single-table operation code.

[0128] Master-Slave Model: On the basis of the single-table model, it supports the multi-table operation model and provides solidified multi-table operation code.

[0129] Single-Table Workflow Model: Aggregates the workflow model in the single-table model and provides the code for business capabilities related to the workflow under the single-table model.

[0130] Master-Slave Table Workflow Model: Aggregates the workflow model in the master-slave model and provides the code for business capabilities related to the workflow under the multi-table model.

[0131] Example 2

[0132] In one embodiment of the present disclosure, a business development execution system based on a parsing engine component is provided. The parsing engine component includes four layers, which are, from top to bottom, an interface layer, a logic arrangement layer, a logic unit layer, and a solidified bottom layer implementation layer. The system includes:

[0133] The development module is configured to: split the target business into multiple logical units based on the hierarchical design of the parsing engine component, and develop and implement the target business through the interface layer according to the interfaces published by the logical orchestration layer and the logical unit layer;

[0134] The execution module is configured to: when executing the developed target business, call the interface published by the logic orchestration layer and the logic unit layer through the interface layer, and the interface performs the underlying operation by solidifying the underlying implementation layer.

[0135] Embodiment 3

[0136] The purpose of this embodiment is to provide a computer-readable storage medium.

[0137] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps in a business development execution method based on a parsing engine component as described in the first embodiment of the present disclosure.

[0138] Embodiment 4

[0139] The purpose of this embodiment is to provide an electronic device.

[0140] An electronic device includes a memory, a processor, and a program stored in the memory and executable on the processor. When the processor executes the program, the steps in a business development execution method based on a parsing engine component as described in the first embodiment of the present disclosure are implemented.

[0141] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A business development execution method based on a parsing engine component, characterized in that: The parsing engine component includes four layers, from top to bottom, namely, the interface layer, the logic arrangement layer, the logic unit layer, and the solidified bottom layer implementation layer. The specific steps of the method are as follows: Based on the hierarchical design of the parsing engine components, the target business is divided into multiple logical units. According to the interfaces published by the logical orchestration layer and the logical unit layer, the target business is developed and implemented through the interface layer. When executing the developed target business, the interface layer calls the interfaces published by the logic orchestration layer and the logic unit layer, and the interfaces perform the underlying operations by solidifying the underlying implementation layer.

2. A method for executing business development based on a parsing engine component as claimed in claim 1, characterized in that: Each of the four levels includes several interfaces for implementing different encapsulations, specifically: The solidified bottom layer implementation layer is used to encapsulate bottom layer operations, including data operation query language and commands; The logic unit layer is used to encapsulate commonly used logic units and call the underlying operations encapsulated in the solidified underlying implementation layer by passing parameters; The logic arrangement layer is used to encapsulate commonly used logic unit arrangements, obtain arrangement information of the logic unit and input and output parameter information of the arrangement; The interface layer is used to encapsulate several interfaces published by the logic orchestration layer and the logic unit layer. Unpublished interfaces cannot be called.

3. A method for executing business development based on a parsing engine component as claimed in claim 2, characterized in that: The interface layer encapsulates and defines several interfaces published by the logic orchestration layer and the logic unit layer, including defining input parameters and output parameters of the interfaces.

4. A method for executing business development based on a parsing engine component as claimed in claim 2, characterized in that: The logic orchestration layer includes an executor and orchestration chain information. The executor is used to execute the orchestration chain information. The orchestration chain information stores the orchestration information of the logic unit and the input and output parameter information of the orchestration.

5. A method for executing business development based on a parsing engine component as claimed in claim 2, characterized in that: The logic unit layer implements a business unit with business logic based on the solidified underlying implementation layer, including preset solidified relational database operations, preset extended operations and extended solidified operations.

6. A method for executing business development based on a parsing engine component as claimed in claim 2, characterized in that: The solidified bottom layer implementation layer includes relational database solidification, API interface call solidification and solidified code extension.

7. A method for executing business development based on a parsing engine component as claimed in claim 1, characterized in that: The target business is split into multiple logical units, specifically: The logical units are split according to the operation categories included in the target business, wherein the operation categories include database operations, branch judgments, and API calls.

8. A business development execution system based on a parsing engine component, characterized in that: The parsing engine component includes four layers, from top to bottom, namely, the interface layer, the logic arrangement layer, the logic unit layer, and the solidified bottom layer implementation layer. The system includes: The development module is configured to: split the target business into multiple logical units based on the hierarchical design of the parsing engine component, and develop and implement the target business through the interface layer according to the interfaces published by the logical orchestration layer and the logical unit layer; The execution module is configured to: when executing the developed target business, call the interface published by the logic orchestration layer and the logic unit layer through the interface layer, and the interface performs the underlying operation by solidifying the underlying implementation layer.

9. An electronic device, comprising: a memory for non-transitory storage of computer readable instructions; a processor for executing the computer-readable instructions; Wherein, when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 7 is executed.

10. A storage medium, characterized in that: The computer-readable instructions are non-transitorily stored, wherein when the computer-readable instructions are executed by a computer, the method of any one of claims 1 to 7 is performed.

Images