CN116880824A

CN116880824A - System and method for automatically generating and constructing zero code back-end service

Info

Publication number: CN116880824A
Application number: CN202310899382.5A
Authority: CN
Inventors: 杜伟; 杨华冬; 谢玉鑫; 邵明腾; 赵鹏程
Original assignee: Jinxiandai Information Industry Co ltd
Current assignee: Jinxiandai Information Industry Co ltd
Priority date: 2023-07-21
Filing date: 2023-07-21
Publication date: 2023-10-13

Abstract

The invention relates to the field of zero code software development, and provides a system and a method for automatically generating and constructing zero code back-end business, wherein the system comprises the following steps: the interface layer is used for receiving all interfaces and obtaining corresponding interface information by matching prestored interface url paths; the interface information includes the name of the arrangement; the arrangement layer is used for arranging the unit layer nodes into an arrangement chain and naming the arrangement chain to obtain an arrangement name; the unit layer is used for executing the parameter information of the unit layer node corresponding to the interface information and the solidified layer information to be called according to the interface information, and transmitting the parameter information to the adaptation layer; the adaptation layer is used for processing the parameter information and converting the parameter information into a parameter structure required by a curing method of the curing layer; according to the routing information transmitted by the unit layer, a corresponding curing method is called, the parameter structure is processed, and the processed data are transmitted to the curing layer; and the solidification layer is used for carrying out database operation processing on the received data.

Description

System and method for automatically generating and constructing zero code back-end service

Technical Field

The invention relates to the field of zero code software development, in particular to a system and a method for automatically generating and constructing zero code back-end business.

Background

The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.

The traditional web development mode is that the back end writes api interface and business logic, then packages and constructs, and finally deploys on a server. The front end invokes the interface to render the data onto the page.

In the use scene of the zero code, the design and the application are integrated, the application needs to respond immediately after the design is finished, and if the zero code uses the development mode, the back-end service needs to be redeployed each time the design is finished. It can be seen that the traditional web development approach has failed to meet the requirements of the zero code usage scenario.

Disclosure of Invention

In order to solve the defects of the prior art, the invention provides a system and a method for automatically generating and constructing zero-code back-end business, which can automatically generate and construct business logic, and reduce development work by 90%; the back-end service can apply a new service system without restarting, thereby saving 100% of service deployment time.

In order to achieve the above purpose, the present invention adopts the following technical scheme:

the first aspect of the invention provides a system for automatically generating and constructing zero-code back-end service.

A system for automatically generating and constructing zero code back-end service comprises: the interface layer, the arrangement layer, the unit layer, the adaptation layer and the solidification layer;

the interface layer is used for receiving all interfaces and obtaining corresponding interface information by matching prestored interface url paths; the interface information comprises a name of the arrangement;

the arrangement layer is used for arranging the unit layer nodes into an arrangement chain, and naming the arrangement chain to obtain an arrangement name;

the unit layer is used for executing the parameter information of the unit layer node corresponding to the interface information and the solidified layer information to be called according to the interface information, and transmitting the parameter information to the adaptation layer;

the adaptation layer is used for processing the parameter information and converting the parameter information into a parameter structure required by a curing method of the curing layer; according to the routing information transmitted by the unit layer, a corresponding curing method is called, the parameter structure is processed, and the processed data are transmitted to the curing layer;

the solidification layer is used for carrying out database operation processing on the received data and providing a third party interface call.

Further, the interface layer is further configured to verify the parameters after the matching, terminate the request if the parameter verification is illegal, and enter the orchestration layer if not.

Further, the orchestration layer is further configured to add, delete, modify, and query data models.

Furthermore, the arrangement layer is further used for binding the input parameters, the output parameters and the local parameters of the chain of the unit layer nodes according to the relation among the unit layer nodes, and the output of the arrangement layer is the output parameters of the chain.

Further, the unit layer is further used for storing parameter information of the unit layer node and solidification layer information to be called, and the parameter information comprises query conditions and ordering conditions of page configuration.

Further, the unit layer is further used for providing a calling method for routing to a third party interface, or the unit layer is further used for providing a method for expanding routing, or the unit layer is further used for automatically generating logic data of a service.

Further, the solidification layer is further used for performing addition, deletion, modification and query operations on the data model, wherein the data model comprises a single-table model, a main sub-model, a flow single-table model and a flow main sub-model.

Further, the system also includes a support layer for providing metadata management, model information, api connectors, and data upgrades for the interface layer, orchestration layer, adaptation layer, and curing layer.

Further, the metadata management comprises the management of the association relationship between the data table structure dynamically created by the zero codes and the main sub table;

further, the model information comprises a layer of data structure encapsulation based on metadata, and a table corresponds to a piece of metadata;

further, the api connector is configured to store an authentication template and information required by the third party interface, where one connector represents an authentication manner;

further, the data upgrades include both homoversioning upgrades and trans-versioning upgrades.

The second aspect of the invention provides a method for automatically generating and constructing zero code back-end service.

A method for automatically generating and constructing zero code back-end service includes:

the interface layer receives all interfaces and obtains corresponding interface information by matching prestored interface url paths; the interface information comprises a name of the arrangement;

the arrangement layer arranges the unit layer nodes into an arrangement chain, and names the arrangement chain to obtain an arrangement name;

the unit layer executes parameter information of the unit layer node corresponding to the interface information and solidification layer information to be called according to the interface information, and transmits the parameter information to the adaptation layer;

the adaptation layer processes the parameter information and converts the parameter information into a parameter structure required by a curing method of the curing layer; according to the routing information transmitted by the unit layer, a corresponding curing method is called, the parameter structure is processed, and the processed data are transmitted to the curing layer;

and the solidification layer performs database operation processing on the received data and provides a third party interface call.

Compared with the prior art, the invention has the beneficial effects that:

the invention solves the problems that the traditional web development mode needs to write service interfaces and logic manually, then restarts back-end service and cannot meet the integral use of zero code design and application, can automatically generate and construct service logic, and reduces the development work by 90%; the back-end service can apply a new service system without restarting, thereby saving 100% of service deployment time.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention.

FIG. 1 is a block diagram of a system for automatic generation and construction of zero code backend services shown in the present invention;

FIG. 2 is a frame diagram of an interface layer shown in the present invention;

FIG. 3 is a frame diagram of an orchestration layer shown in the present invention;

FIG. 4 is a frame diagram of a cell layer of the present invention;

FIG. 5 is a frame diagram of an adaptation layer shown in the present invention;

FIG. 6 is a frame diagram of a cured layer shown in the present invention;

fig. 7 is a frame diagram of a support layer according to the present invention.

Detailed Description

The invention will be further described with reference to the drawings and examples.

It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the invention. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments according to the present invention. As used herein, the singular is also intended to include the plural unless the context clearly indicates otherwise, and furthermore, it is to be understood that the terms "comprises" and/or "comprising" when used in this specification are taken to specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof.

Embodiments of the invention and features of the embodiments may be combined with each other without conflict.

Example 1

As shown in fig. 1, embodiment 1 of the present invention provides a system for automatically generating and constructing a zero code backend service.

In the embodiment, interface data, service data and model data are automatically generated in a design stage, interface information is analyzed in real time in an operation stage, corresponding sql statements are generated, a database is called for execution, a return result is packaged, and the whole process is not required to be restarted.

The embodiment is a layered architecture, which is divided into 6 layers: interface layer, orchestration layer, unit layer, adaptation layer, solidification layer and supporting layer, the following is specifically introduced to this embodiment:

1. an interface layer, as shown in fig. 2.

The interface layer receives all the unmatched interfaces through the regular expression, matches the interfaces which are being requested through the interface information stored during release, performs parameter verification, and if the parameter verification is illegal, terminates the request and returns error information. If the parameters are legal, the next layer is entered. The interface layer enables the back-end service to apply a new service system interface without restarting, is suitable for a scene of integrating zero code design and application, and saves 100% of service deployment time.

2. The layers are laid out as shown in fig. 3.

The orchestration layer is an integration of existing functionality and also a support for visually orchestrated functionality. Multiple logical nodes can be arbitrarily combined and organized into a chain.

The logical nodes can be addition, deletion and modification of the data model, for example, a plurality of methods exist for a data model newly built on a certain platform by default: according to id query, list query, paging query, single data addition, batch data addition, single data modification, batch data modification, single data deletion and batch data deletion; or may be a call to a third party interface, such as an interface to query weather, an interface to query air quality, etc.

The logic nodes need to form chains and also need to process the relation among the nodes, the nodes consist of 3 parts, namely an input parameter, an output parameter and a logic body, and each node needs to be kept to obtain the parameters in the correct format. This requires the introduction of parameters of the chain: input parameters, output parameters, and local parameters. All the input parameters and the output parameters of the logic nodes are bound with the parameters of the chain, and when the logic execution of the whole chain is completed, the output parameters of the chain are parameters which need to be returned by the arrangement layer.

3. The cell layer is shown in fig. 4.

The unit layer mainly stores parameter information and called solidified layer information, wherein the parameter information comprises query conditions, sorting conditions and the like configured on a page, and when the unit layer is applied, the conditions are taken out and transmitted to the next layer. The unit layer can be regarded as a router, the solidification layer has multiple functions, and the unit layer can route the service call to the corresponding solidification layer, such as a solidification method capable of being routed to a database model or a method capable of being invoked by a third party interface. Meanwhile, some expansion routes are preset for subsequent service expansion, such as workflow expansion, custom sql model expansion, component method expansion of logic arrangement and the like. The unit layer can automatically generate the structure data of each service, does not need handwriting codes, directly analyzes the data during operation, carries out corresponding logic processing, and reduces development work by 90%.

Specifically, the unit layer may automatically generate structural data of the service according to a small amount of information. The structure data is converted according to a table structure in a database, and in the design stage, the unit layer can automatically acquire the model structure from the model information of the support layer, and acquire all field information including field names, field types, field translation, field encryption and decryption and the like. According to the information, the front end can automatically construct structural data without providing all parameter structures, for example, the front end only needs to provide table names to be queried for all users with the age of more than 20, the fields to be filtered can acquire the structure of a user table according to the table names, automatically generate the fields to be queried and type data corresponding to each field, and if the type data is handwriting codes, the DTO class of handwriting receiving parameters, the entity class corresponding to the table and the like are needed.

4. An adaptation layer as shown in fig. 5.

The adaptation layer is mainly the parameter information of the unit layer to be processed into the parameter needed by the solidified layer, and because the capability of the solidified layer is various, the adaptation layer also needs to have an interface matched with the solidified layer. The solidification method such as data adding, deleting, modifying and checking needs to convert the parameters into corresponding sql grammar tree, for example, the grammar tree corresponding to the query method needs to construct elements such as query fields, query conditions, sequencing and the like. An adaptation layer must be provided between the cell layer and the cured layer for the connection.

5. The layer is cured as shown in fig. 6.

The cured layer includes:

(1) Adding, deleting and checking a model, wherein the model comprises a single-form model, a main sub-model, a flow single-form model and a flow main sub-model; meanwhile, database operations of a multi-layer data model with unlimited levels are supported, wherein the database operations comprise full addition and deletion, incremental addition and deletion and cross-node addition and deletion, the distance between a model of a first layer node and a model of a leaf node is very far along with the deep extension of a model level, and the data operations of all levels cannot be displayed on a page at the same time, so that the cross-node addition and deletion greatly simplifies a parameter transmission structure of the front end.

(2) The third party interface call comprises an interface without authentication and an interface needing authentication, wherein the interface needing authentication mainly supports four protocols of oauth 2.0.

The solidified layer may provide more support for logical orchestration. The design of the solidification layer is very convenient to expand, different functions can be expanded on the solidification layer like expansion plug-ins, various business logics are automatically generated and constructed by the unit layer, and code development work in more business fields is reduced.

6. A support layer, as shown in fig. 7.

The support layer is a generic layer, which is used in all 5 levels above. The support layer includes metadata management, api connectors, model information, and data upgrades.

The metadata management is the association relationship between the data table structure dynamically created by the zero codes and the main sub table, and is the basis of model information.

Model information is a package of a layer of data structure based on metadata, and a table corresponds to a piece of metadata and possibly corresponds to a plurality of models. The parts of the cell layer, adaptation layer and curing layer with respect to database operations are based on model information.

The api connector is the basis for the invocation of the third party interface, because some third party interfaces need to authenticate, and these authentication templates and information are stored in the connector, and one connector represents an authentication mode, such as a WeChat interface authentication, a Payment interface authentication, etc.

In the version upgrading process of the embodiment, the data upgrading is a framework for processing data compatibility, version numbers are used as sequence nodes, and data and methods of each version to be upgraded are expanded, so that the embodiment has the capacity of cross-version upgrading.

Example 2

The embodiment 2 of the invention provides a method for automatically generating and constructing zero code back-end service.

The interface layer stores interface information during the design phase, including url paths of the interfaces. When the interface layer is applied, the interface layer receives all interfaces through the regular expression, and finds out corresponding interface information through matching the stored url paths.

The interface information stores the names of the arranging chains, then an arranging layer is arranged according to the names of the chains to find out the corresponding arranging chains, each node on the arranging chains corresponds to a unit layer node, for example, two nodes are arranged on the chains, 1, the user information is stored; 2. acquiring user information with all ages more than 20; the first node corresponds to a unit layer save logic and the second node corresponds to a unit layer query logic.

The nodes on the compiling chain are executed one by one according to the sequence, and each node information stores the main key of the corresponding unit layer, so that the corresponding unit layer information is found.

The unit layer stores the parameter information of the logic and the solidification layer information to be called. For example, the unit node of "save user information", a structure of storing user information at the unit layer, and a required curing method "form save", the user information structure is used for de-adapting layer processing actual parameters, and the curing layer information is used for routing to the curing method corresponding to the curing layer.

The unit layer transmits the parameter information to the adaptation layer, and the adaptation layer processes the parameters into a parameter structure required by a curing method of the cured layer. For example, the "list query" method of the solidified layer, the required parameter structure contains the fields of query, where condition and ordering condition, etc., and the adaptation layer will convert the parameters transmitted from the unit layer into this structure.

And the adaptation layer calls a specific solidified layer method according to the routing information transmitted by the unit layer and transmits the processed parameters.

The solidified layer is fixed business logic, which comprises database operations such as saving, inquiring, modifying, deleting and the like, and also comprises interface forwarding capabilities such as third-party interface calling and the like.

The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. The system for automatically generating and constructing the zero code back-end service is characterized by comprising the following components: the interface layer, the arrangement layer, the unit layer, the adaptation layer and the solidification layer;

2. The system for automatically generating and constructing the zero-code back-end service according to claim 1, wherein the interface layer is further configured to verify the parameters after the matching, terminate the request if the parameter verification is illegal, and enter the orchestration layer if the parameter verification is illegal.

3. The system for automatic generation and construction of zero-code back-end services according to claim 1, wherein said orchestration layer is further configured to add, delete, modify, and query data models.

4. The system for automatically generating and constructing the zero-code back-end service according to claim 1, wherein the arrangement layer is further configured to bind the input parameters, the output parameters and the local parameters of the chain with the input parameters, the output parameters and the local parameters of the chain by the input parameters, the output parameters and the logic bodies of the unit layer nodes according to the relationship between the unit layer nodes.

5. The system for automatically generating and constructing the zero-code back-end service according to claim 1, wherein the unit layer is further configured to store parameter information of a unit layer node and solidification layer information to be called, and the parameter information includes a query condition and a ranking condition of page configuration.

6. The system for automatically generating and constructing zero-code backend services according to claim 1, wherein the unit layer is further configured to provide a calling method for routing to a third party interface, or the unit layer is further configured to provide a method for expanding routing, or the unit layer is further configured to automatically generate logic data of a service.

7. The system for automatically generating and building a zero-code back-end service according to claim 1, wherein the solidified layer is further configured to perform addition, deletion, modification and query operations on a data model, and the data model includes a single-table model, a main sub-model, a flow single-table model and a flow main sub-model.

8. The system for automatic generation and construction of zero-code backend services according to any one of claims 1-7, further comprising a support layer for providing metadata management, model information, api connectors and data upgrades for an interface layer, an orchestration layer, an adaptation layer and a curing layer.

9. The system for automatically generating and constructing the zero-code back-end service according to claim 8, wherein the metadata management includes managing an association relationship between a data table structure dynamically created by the zero code and a main sub-table;

or alternatively, the first and second heat exchangers may be,

the model information comprises a layer of data structure package based on metadata, and a table corresponds to a piece of metadata;

or alternatively, the first and second heat exchangers may be,

the api connector is used for storing authentication templates and information required by a third party interface, and one connector represents an authentication mode;

or alternatively, the first and second heat exchangers may be,

the data upgrades include both homoversioning upgrades and trans-versioning upgrades.

10. The method for automatically generating and constructing the zero code back-end service is characterized by comprising the following steps of: