CN116860223A - Cloud-protogenesis-based low-code development and delivery method - Google Patents
Cloud-protogenesis-based low-code development and delivery method Download PDFInfo
- Publication number
- CN116860223A CN116860223A CN202211082374.3A CN202211082374A CN116860223A CN 116860223 A CN116860223 A CN 116860223A CN 202211082374 A CN202211082374 A CN 202211082374A CN 116860223 A CN116860223 A CN 116860223A
- Authority
- CN
- China
- Prior art keywords
- application
- code
- cloud
- development
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000011161 development Methods 0.000 title claims abstract description 75
- 238000002716 delivery method Methods 0.000 title claims abstract description 33
- 238000012360 testing method Methods 0.000 claims abstract description 37
- 238000013461 design Methods 0.000 claims abstract description 30
- 238000007726 management method Methods 0.000 claims abstract description 29
- 230000000007 visual effect Effects 0.000 claims abstract description 22
- 230000010354 integration Effects 0.000 claims abstract description 14
- 238000012795 verification Methods 0.000 claims abstract description 5
- 239000008186 active pharmaceutical agent Substances 0.000 claims description 21
- 238000004458 analytical method Methods 0.000 claims description 12
- 238000012423 maintenance Methods 0.000 claims description 12
- 238000000034 method Methods 0.000 claims description 9
- 238000013499 data model Methods 0.000 claims description 6
- 230000001419 dependent effect Effects 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 claims description 6
- 230000006870 function Effects 0.000 claims description 5
- 230000006978 adaptation Effects 0.000 claims description 3
- 238000012550 audit Methods 0.000 claims description 3
- 238000013475 authorization Methods 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 claims description 3
- 238000004364 calculation method Methods 0.000 claims description 3
- 238000010276 construction Methods 0.000 claims description 3
- 238000012937 correction Methods 0.000 claims description 3
- 230000000694 effects Effects 0.000 claims description 3
- 238000001914 filtration Methods 0.000 claims description 3
- 239000012634 fragment Substances 0.000 claims description 3
- 230000003993 interaction Effects 0.000 claims description 3
- 238000004519 manufacturing process Methods 0.000 claims description 3
- 238000013507 mapping Methods 0.000 claims description 3
- 238000012986 modification Methods 0.000 claims description 3
- 230000004048 modification Effects 0.000 claims description 3
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000007792 addition Methods 0.000 claims description 2
- 238000012217 deletion Methods 0.000 claims description 2
- 230000037430 deletion Effects 0.000 claims description 2
- 230000008520 organization Effects 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 abstract description 5
- 238000000926 separation method Methods 0.000 abstract description 2
- 238000012384 transportation and delivery Methods 0.000 description 3
- 230000009466 transformation Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a cloud-protogenesis-based low-code development and delivery method, which comprises a cloud protogenesis platform building step, a cloud protogenesis platform application management step, a cloud protogenesis platform application visual design step, a cloud protogenesis platform application integration development step, a cloud protogenesis platform application test verification step and a cloud protogenesis platform application release online step. The cloud-protogenesis-based low-code development and delivery method provided by the invention has the advantages that by means of the thought of low codes and combining with the cloud protogenesis technology, a micro-service architecture and front-end and rear-end separation development and delivery method is provided for developers, application codes can be generated on a low-code development platform after visual design, secondary development, debugging and release can be carried out, and privately-deployed independent of the platform can be carried out, so that the technical problems of complex service logic development, integration and flexible deployment among applications of programs and the like are solved, an application system meeting the requirements of user service scenes can be quickly developed conveniently and efficiently, and the development efficiency and quality are improved.
Description
Technical Field
The invention relates to a cloud-protogenesis-based low-code development and delivery method.
Background
In the process of enterprise digital transformation, in order to solve various pain points in the process of software development projects and improve the project delivery efficiency, the enterprise digital transformation speed is accelerated, and more enterprises select low-code platforms as technical tools so as to rapidly cope with the high-speed growth and the complexity increase of the business. The building mode of the visual self-defined form and flow design provided by the low-code platform can solve part of application scenes, but is limited to a certain specific industry field, and can not meet scene requirements when facing scenes with high business complexity, high integration level between applications and flexible deployment. Even after the appearance of a general-purpose low code platform on the market, the situation of "not enough" and "not applicable" often occurs.
Disclosure of Invention
The invention aims to overcome the defects of the prior art, and provides a cloud-protogenesis-based low-code development and delivery method, which is convenient, fast and efficient by means of the thought of low codes and combining with the cloud protogenesis technology, can rapidly develop an application system meeting the requirements of user business scenes, and improves the development efficiency and quality.
The technical scheme for achieving the purpose is as follows: a low-code development and delivery method based on cloud protogenesis comprises the following steps:
s1, a cloud native platform building step: based on the racher framework, a cloud native platform is built through a script, a host is managed through an infrastructure interface, IP addresses of available resources are configured, and then the following application supporting service is built through an application interface:
constructing Yun Yuansheng operation and maintenance support service based on the cloud original open source framework;
constructing a cloud native middleware service based on a cloud native open source framework;
constructing a cloud native integrated development environment IDE tool based on a cloud native open source framework, and deploying module services of a platform application management interface, a platform application design interface, a platform application test interface and a platform application release interface related to a cloud native platform;
s2, cloud native platform application management: through a platform application management interface, managing items, applications and application items in the development process, configuring a code warehouse, a product warehouse, a service address and an account number of middleware such as caching, message queues, micro-service management and the like, and then creating the items, the applications and the application items, wherein one item corresponds to one micro-service, one application corresponds to one menu catalog, and one application item corresponds to one menu-associated group of pages;
s3, a cloud native platform application visual design step: generating an application code by a platform application design interface, an on-line design application UI interface, an API interface and a data model; configuring an application-adapted terminal, dragging a visual design form of a control, referencing a component library of a cloud native platform, and setting a data layer field bound by a form field; configuring field names, field types and field IDs of the data layer tables through a data model, and setting associated fields of multiple tables; after the form is configured, the cloud native platform stores the configuration description as application metadata, and the application code is automatically generated by analyzing the metadata and the code template through a code engine of the cloud native platform;
s4, cloud native platform application integration development steps: the method comprises the steps of performing secondary development on application codes of imported projects through cloud native integrated development environment IDE tools, performing online code editing, code analysis, code compiling, debugging programs and pushing codes, introducing application integrated dependent packages, setting starting environment variables of different environments, editing application integration and complex business logic aiming at interface codes, automatically analyzing writing specifications and correction prompts of the codes through the analysis tools, and performing debugging programs after compiling the project codes; pushing codes to a code warehouse by an integrated code warehouse client through a cloud native integrated development environment IDE tool after debugging is completed;
s5, testing and verifying the cloud native platform application: based on the random API, deploying and applying to a testing environment through a platform application testing interface, performing unit testing, functional testing, performance pressure testing and vulnerability scanning on the project, and automatically generating a testing report; configuring an application deployment file of a test environment, and setting resources such as CPU core number, memory size, application domain name, and application and access ports of a container; constructing a test environment, automatically pulling codes from a code warehouse, pulling a dependent package from a product warehouse, compiling, packaging and uploading a program package to the test environment; the application test is automatically integrated with cloud native platform operation service and comprises a micro-service application, a micro-service gateway, an authentication service, a dynamic form component, a workflow component, a chart component and a user management authority system;
s6, the cloud native platform application release online step: based on the rancher API, the application is deployed to the production environment through a platform application release interface, and the project is checked, operated and monitored, and is configured and operated in the same step S5.
In the foregoing low code development and delivery method based on cloud protogenesis, in step S1, the Yun Yuansheng operation and maintenance support service is a code management service, a program construction service and a containerization management service, and specifically includes a code warehouse, a product warehouse, a code scanning service, a DevOps construction deployment service, a mirror warehouse, a K8S container management service, a virtual machine management service, an operation and maintenance monitoring alarm service, and an operation and maintenance security audit service;
the cloud native middleware service is distributed storage, calculation and load balancing service, and specifically comprises a database, a cache, a message queue, a search engine, a spring group micro-service management, web load balancing, web service, task scheduling, log collection and application monitoring alarm.
The cloud native-based low-code development and delivery method comprises registration and discovery, configuration, load balancing and fusing and current limiting.
In the above-mentioned low code development and delivery method based on cloud native, in step S3, the data layer field bound by the form field is set to be the mapping of the data layer table field by default, or an API interface or constant character set with custom data source is adopted.
In the foregoing low code development and delivery method based on cloud native, in step S3, application metadata = { version class, terminal class, object class, authority class, rule class }, and defining a structure of application metadata according to document namespaces xmlns;
the version class mainly comprises a version and release date of release of application metadata, and the terminal class comprises a PC end, adaptation of a mobile end, a menu, a page, a list, a query field, a custom button, a form field, a layout, a control, a form event and a button event;
the object class mainly comprises names, data sources, APIs, table names, field types, fields to be aggregated and a field dictionary list of objects;
the permission class mainly comprises functional permissions and data access permissions;
the rule classes mainly comprise workflow configuration, API updating, field updating and custom business rules.
The cloud-protogenesis-based low-code development and delivery method comprises the steps that the function authority comprises an API and an authorization policy, and the data access authority comprises the addition, deletion and modification of fields, the role of allowing operation and the organization data filtering authority.
In the foregoing low code development and delivery method based on cloud protogenesis, in step S3, the code templates are divided into a frame class template, an online class template and an application class template according to application scenes, wherein:
the frame class template comprises front and back end frame codes, compiling operation configuration files and starting configuration files;
the online class templates are divided into flow design classes and dynamic forms, secondary development is not needed, and the online class templates are used for online previewing of design effects of flows and forms;
the application templates are divided into a flow form template, an application page template, a report form template and a portal template according to functions; the templates are divided into front-end and back-end code application class templates;
the front-end code application class template comprises a page route configuration code, a page display fragment code, a page interaction code and an interface calling code; the back-end code application class template comprises a controller interface code, a service business logic code, a DAO data layer access code, a mapper.xml data layer configuration, a DO data layer entity model code, a DTO data transmission layer model code and a VO display layer model code, and the back-end code application class template is added with a swagger annotation so as to output a standard restful interface document when the program runs.
In the foregoing low-code development and delivery method based on cloud native, in step S3, the code engine parses the code template based on metadata and generates a corresponding application, and the code engine is divided into a front-end editor and a back-end code parsing engine, where:
the front-end editor comprises a page visual editor, a form editor and a flow editor; the page visual editor comprises a left operating area, a middle canvas area and a right attribute configuration area, a dragged assembly is copied through a mouse dragging event of the page assembly, the current area position of the assembly is calculated, the dragged page assembly is dynamically rendered to the middle canvas area, and then the attribute and the event of the assembly are set; the form editor sets a form field ID, a field name, a field type, a read-write attribute, a verification rule of the field, a bound data access layer field and a data source; the flow editor is realized based on a flow open source framework flow definition module;
the back-end code analysis engine comprises a page engine, a form engine and a flow engine, wherein the page engine corresponds to a page visual editor at the front end, and front-end codes and back-end codes after analysis are generated according to stored metadata and code templates corresponding to applications; the form engine corresponds to a form editor at the front end and generates a form structure corresponding to a data source and an add-delete-modify-examine part code of an application according to the stored metadata; the flow engine is realized based on a flow open source framework flow engine module.
In the low-code development and delivery method based on the cloud native, in step S3, the application codes and the application metadata are generated after the visual design form, so that secondary development and application can be performed, and the problems of complex business logic development and integration between applications are solved.
The cloud-protogenesis-based low-code development and delivery method provided by the invention has the advantages that by means of the thought of low codes and combining with the cloud protogenesis technology, a micro-service architecture and front-end and rear-end separation development and delivery method is provided for developers, application codes can be generated on a low-code development platform after visual design, secondary development, debugging and release can be carried out, and privately-deployed independent of the platform can be carried out, so that the technical problems of complex service logic development, integration and flexible deployment among applications of programs and the like are solved, an application system meeting the requirements of user service scenes can be quickly developed conveniently and efficiently, and the development efficiency and quality are improved.
Drawings
FIG. 1 is a flow chart of a cloud native based low code development delivery method of the present invention.
Detailed Description
In order to enable those skilled in the art to better understand the technical scheme of the present invention, the following detailed description is provided with reference to the accompanying drawings:
referring to fig. 1, in a preferred embodiment of the present invention, a cloud native-based low-code development and delivery method includes the following steps:
s1, a cloud native platform building step: based on the racher framework, a cloud native platform is built through a script, a host is managed through an infrastructure interface, IP addresses of available resources are configured, and then the following application supporting service is built through an application interface:
constructing Yun Yuansheng operation and maintenance support services such as code management, program construction and containerization management services based on a cloud primary open source framework, wherein the operation and maintenance support services comprise code warehouse, product warehouse, code scanning, devOps construction deployment, mirror warehouse, K8S container management, virtual machine management, operation and maintenance monitoring alarm and operation and maintenance security audit;
based on a cloud primary open source framework, cloud primary middleware services such as distributed storage, calculation and load balancing services are built, and specifically comprise a database, a cache, a message queue, a search engine, a spring group micro-service management, web load balancing, web services, task scheduling, log collection and application monitoring alarm; the spring closed micro-service management comprises registration and discovery, configuration, load balancing and fusing and current limiting;
and constructing a cloud native integrated development environment IDE tool based on the cloud native open source framework, and deploying module services of a platform application management interface, a platform application design interface, a platform application test interface and a platform application release interface related to the cloud native platform.
S2, cloud native platform application management: and managing items, applications and application items in the development process, configuring a code warehouse, a product warehouse, a service address and an account number of middleware such as caching, message queues, micro-service management and the like through a platform application management interface, and then creating the items, the applications and the application items, wherein one item corresponds to one micro-service, one application corresponds to one menu catalog, and one application item corresponds to one menu-associated group of pages.
S3, a cloud native platform application visual design step: generating an application code by a platform application design interface, an on-line design application UI interface, an API interface and a data model; configuring an application-adapted terminal, dragging a visual design form of a control, referencing a component library of a cloud native platform, and setting a data layer field bound by a form field to default to mapping of the data layer field, or adopting an API interface or constant character set of a custom data source; configuring field names, field types and field IDs of the data layer tables through a data model, and setting associated fields of multiple tables; after the form is configured, the cloud native platform stores the configuration description as application metadata, and the application code is automatically generated by analyzing the metadata and the code template through a code engine of the cloud native platform;
application metadata = { version class, terminal class, object class, rights class, rule class }, defining the structure of application metadata according to document namespaces xmlns; the version class mainly comprises a version and release date of release of application metadata, and the terminal class comprises a PC end, adaptation of a mobile end, a menu, a page, a list, a query field, a custom button, a form field, a layout, a control, a form event and a button event; the object class mainly comprises names, data sources, APIs, table names, field types, fields to be aggregated and a field dictionary list of the objects; the authority class mainly comprises a functional authority and a data access authority, wherein the functional authority comprises an API and an authorization policy, and the data access authority comprises the functions of adding, deleting and modifying fields, allowing operation and organizing data filtering authorities; the rule class mainly contains workflow configuration, API update and field update.
S4, cloud native platform application integration development steps: the method comprises the steps of performing secondary development on application codes of imported projects through cloud native integrated development environment IDE tools, performing online code editing, code analysis, code compiling, debugging programs and pushing codes, introducing application integrated dependent packages, setting starting environment variables of different environments, editing application integration and complex business logic aiming at interface codes, automatically analyzing writing specifications and correction prompts of the codes through the analysis tools, and performing debugging programs after compiling the project codes; and pushing codes to the code warehouse by the integrated code warehouse client through the cloud native integrated development environment IDE tool after the debugging is completed.
S5, testing and verifying the cloud native platform application: based on the random API, deploying and applying to a testing environment through a platform application testing interface, performing unit testing, functional testing, performance pressure testing and vulnerability scanning on the project, and automatically generating a testing report; configuring an application deployment file of a test environment, and setting resources such as CPU core number, memory size, application domain name, and application and access ports of a container; constructing a test environment, automatically pulling codes from a code warehouse, pulling a dependent package from a product warehouse, compiling, packaging and uploading a program package to the test environment; the application is automatically integrated with platform running services, and comprises a micro-service application, a micro-service gateway, an authentication service, a dynamic form component, a workflow component, a chart component and a user management authority system.
S6, the cloud native platform application release online step: based on the rancher API, the application is deployed to the production environment through a platform application release interface, and the project is checked, operated and monitored, and is configured and operated in the same step S5.
In step S3, the code templates are divided into a frame class template, an online class template and an application class template according to the application scene, wherein:
the frame class template comprises front and back end frame codes, compiling operation configuration files and starting configuration files;
the online class templates are divided into flow design classes and dynamic forms, secondary development is not needed, and the online class templates are used for online previewing of design effects of flows and forms;
the application templates are divided into a flow form template, an application page template, a report form template and a portal template according to functions; the templates are divided into front-end and back-end code application class templates;
the front-end code application class template comprises a page route configuration code, a page display fragment code, a page interaction code and an interface calling code; the back-end code application class template comprises a controller interface code, a service logic code, a DAO data layer access code, a mapper.xml data layer configuration, a DO data layer entity model code, a DTO data transmission layer model code and a VO display layer model code, and the back-end application class template is added with a swagger annotation so as to output a standard restful interface document when the program runs.
The code engine parses the code template based on the metadata and generates a corresponding application, the code engine being divided into a front-end editor and a back-end code parsing engine, wherein:
the front-end editor comprises a page visual editor, a form editor and a flow editor; the page visual editor comprises a left operating area, a middle canvas area and a right attribute configuration area, a dragged assembly is copied through a mouse dragging event of the page assembly, the current area position of the assembly is calculated, the dragged page assembly is dynamically rendered to the middle canvas area, and then the attribute and the event of the assembly are set; the form editor sets a form field ID, a field name, a field type, a read-write attribute, a verification rule of the field, a bound data access layer field and a data source; the flow editor is realized based on a flow open source framework flow definition module;
the back-end code analysis engine comprises a page engine, a form engine and a flow engine, wherein the page engine corresponds to a page visual editor at the front end, and front-end codes and back-end codes after analysis are generated according to stored metadata and code templates corresponding to applications; the form engine corresponds to a form editor at the front end and generates a form structure corresponding to a data source and an add-delete-modify-examine part code of an application according to the stored metadata; the flow engine is realized based on a flow open source framework flow engine module.
Step S3 is the core of the cloud-protogenesis-based low-code development and delivery method, and application codes and application metadata are generated after a visual design form is formed, so that secondary development and application can be performed, and the problems of complex business logic development and integration between applications are solved.
The cloud-protogenesis-based low-code development and delivery method comprises the software development and delivery processes of project creation, application design, integrated development, test verification, project delivery online operation and the like, and provides a micro-service architecture and front-end and back-end separated development and delivery method for developers by combining a cloud protogenesis technology, wherein application codes can be generated on a low-code development platform after visual design, secondary development, debugging and release can be carried out, and proprietary deployment can be carried out without depending on the platform, so that the technical problems of complex service logic development, integration and flexible deployment among applications of a program are solved.
In summary, the cloud-protogenesis-based low-code development and delivery method disclosed by the invention has the advantages that by means of the thought of low codes and by combining with the cloud protogenesis technology, an application system meeting the service scene requirements of users can be quickly developed, and the development efficiency and quality are improved.
It will be appreciated by persons skilled in the art that the above embodiments are provided for illustration only and not for limitation of the invention, and that variations and modifications of the above described embodiments are intended to fall within the scope of the claims of the invention as long as they fall within the true spirit of the invention.
Claims (9)
1. The low-code development and delivery method based on the cloud protogenesis is characterized by comprising the following steps of:
s1, a cloud native platform building step: based on the racher framework, a cloud native platform is built through a script, a host is managed through an infrastructure interface, IP addresses of available resources are configured, and then the following application supporting service is built through an application interface:
constructing Yun Yuansheng operation and maintenance support service based on the cloud original open source framework;
constructing a cloud native middleware service based on a cloud native open source framework;
constructing a cloud native integrated development environment IDE tool based on a cloud native open source framework, and deploying module services of a platform application management interface, a platform application design interface, a platform application test interface and a platform application release interface related to a cloud native platform;
s2, cloud native platform application management: through a platform application management interface, managing items, applications and application items in the development process, configuring a code warehouse, a product warehouse, a service address and an account number of middleware such as caching, message queues, micro-service management and the like, and then creating the items, the applications and the application items, wherein one item corresponds to one micro-service, one application corresponds to one menu catalog, and one application item corresponds to one menu-associated group of pages;
s3, a cloud native platform application visual design step: generating an application code by a platform application design interface, an on-line design application UI interface, an API interface and a data model; configuring an application-adapted terminal, dragging a visual design form of a control, referencing a component library of a cloud native platform, and setting a data layer field bound by a form field; configuring field names, field types and field IDs of the data layer tables through a data model, and setting associated fields of multiple tables; after the form is configured, the cloud native platform stores the configuration description as application metadata, and the application code is automatically generated by analyzing the metadata and the code template through a code engine of the cloud native platform;
s4, cloud native platform application integration development steps: the method comprises the steps of performing secondary development on application codes of imported projects through cloud native integrated development environment IDE tools, performing online code editing, code analysis, code compiling, debugging programs and pushing codes, introducing application integrated dependent packages, setting starting environment variables of different environments, editing application integration and complex business logic aiming at interface codes, automatically analyzing writing specifications and correction prompts of the codes through the analysis tools, and performing debugging programs after compiling the project codes; pushing codes to a code warehouse by an integrated code warehouse client through a cloud native integrated development environment IDE tool after debugging is completed;
s5, testing and verifying the cloud native platform application: based on the random API, deploying and applying to a testing environment through a platform application testing interface, performing unit testing, functional testing, performance pressure testing and vulnerability scanning on the project, and automatically generating a testing report; configuring an application deployment file of a test environment, and setting resources such as CPU core number, memory size, application domain name, and application and access ports of a container; constructing a test environment, automatically pulling codes from a code warehouse, pulling a dependent package from a product warehouse, compiling, packaging and uploading a program package to the test environment; the application test is automatically integrated with cloud native platform operation service and comprises a micro-service application, a micro-service gateway, an authentication service, a dynamic form component, a workflow component, a chart component and a user management authority system;
s6, the cloud native platform application release online step: based on the rancher API, the application is deployed to the production environment through a platform application release interface, and the project is checked, operated and monitored, and is configured and operated in the same step S5.
2. The cloud-protogenesis-based low-code development and delivery method according to claim 1, wherein in step S1, the Yun Yuansheng operation and maintenance support service is a code management, program construction and containerization management service, and specifically comprises a code warehouse, a product warehouse, a code scanning, a DevOps construction deployment, a mirror warehouse, a K8S container management, a virtual machine management, an operation and maintenance monitoring alarm, and an operation and maintenance security audit;
the cloud native middleware service is distributed storage, calculation and load balancing service, and specifically comprises a database, a cache, a message queue, a search engine, a spring group micro-service management, web load balancing, web service, task scheduling, log collection and application monitoring alarm.
3. The cloud-native based low-code development delivery method of claim 3, wherein said spring closed micro-service governance comprises registration and discovery, configuration, load balancing and fused current limiting.
4. The cloud-protogenesis-based low-code development and delivery method according to claim 1, wherein in step S3, the data layer field bound by the form field is set to be a data layer table field mapping by default or an API interface or a constant character set of a custom data source is adopted.
5. The cloud-protogenesis-based low-code development and delivery method according to claim 1, wherein in step S3, application metadata = { version class, terminal class, object class, authority class, rule class }, a structure of application metadata is defined according to document naming space xmlns;
the version class mainly comprises a version and release date of release of application metadata, and the terminal class comprises a PC end, adaptation of a mobile end, a menu, a page, a list, a query field, a custom button, a form field, a layout, a control, a form event and a button event;
the object class mainly comprises names, data sources, APIs, table names, field types, fields to be aggregated and a field dictionary list of objects;
the permission class mainly comprises functional permissions and data access permissions;
the rule classes mainly comprise workflow configuration, API updating, field updating and custom business rules.
6. The cloud-native based low-code development delivery method of claim 5, wherein the functional rights comprise APIs and authorization policies, and the data access rights comprise field additions, deletions, modifications, roles of allowed operations, and organization data filtering rights.
7. The cloud-protogenesis-based low-code development and delivery method according to claim 1, wherein in step S3, the code templates are classified into a frame class template, an online class template, and an application class template according to application scenes, wherein:
the frame class template comprises front and back end frame codes, compiling operation configuration files and starting configuration files;
the online class templates are divided into flow design classes and dynamic forms, secondary development is not needed, and the online class templates are used for online previewing of design effects of flows and forms;
the application templates are divided into a flow form template, an application page template, a report form template and a portal template according to functions; the templates are divided into front-end and back-end code application class templates;
the front-end code application class template comprises a page route configuration code, a page display fragment code, a page interaction code and an interface calling code; the back-end code application class template comprises a controller interface code, a service business logic code, a DAO data layer access code, a mapper.xml data layer configuration, a DO data layer entity model code, a DTO data transmission layer model code and a VO display layer model code, and the back-end code application class template is added with a swagger annotation so as to output a standard restful interface document when the program runs.
8. The cloud-native based low-code development delivery method according to claim 1 or 7, wherein in step S3, the code engine parses the code template based on metadata and generates a corresponding application, the code engine is divided into a front-end editor and a back-end code parsing engine, wherein:
the front-end editor comprises a page visual editor, a form editor and a flow editor; the page visual editor comprises a left operating area, a middle canvas area and a right attribute configuration area, a dragged assembly is copied through a mouse dragging event of the page assembly, the current area position of the assembly is calculated, the dragged page assembly is dynamically rendered to the middle canvas area, and then the attribute and the event of the assembly are set; the form editor sets a form field ID, a field name, a field type, a read-write attribute, a verification rule of the field, a bound data access layer field and a data source; the flow editor is realized based on a flow open source framework flow definition module;
the back-end code analysis engine comprises a page engine, a form engine and a flow engine, wherein the page engine corresponds to a page visual editor at the front end, and front-end codes and back-end codes after analysis are generated according to stored metadata and code templates corresponding to applications; the form engine corresponds to a form editor at the front end and generates a form structure corresponding to a data source and an add-delete-modify-examine part code of an application according to the stored metadata; the flow engine is realized based on a flow open source framework flow engine module.
9. The cloud-protogenesis-based low-code development and delivery method according to claim 1, wherein in step S3, secondary development and application can be performed by generating application codes and application metadata after visualizing a design form, and the problems of complex business logic development and integration between applications are solved.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211082374.3A CN116860223A (en) | 2022-09-06 | 2022-09-06 | Cloud-protogenesis-based low-code development and delivery method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211082374.3A CN116860223A (en) | 2022-09-06 | 2022-09-06 | Cloud-protogenesis-based low-code development and delivery method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116860223A true CN116860223A (en) | 2023-10-10 |
Family
ID=88220381
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211082374.3A Pending CN116860223A (en) | 2022-09-06 | 2022-09-06 | Cloud-protogenesis-based low-code development and delivery method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116860223A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117252180A (en) * | 2023-11-16 | 2023-12-19 | 太平金融科技服务（上海）有限公司 | Report generation method and device, electronic equipment and storage medium |
| CN117289916A (en) * | 2023-11-24 | 2023-12-26 | 美云智数科技有限公司 | Digital intelligent PaaS platform system |
| CN117667063A (en) * | 2024-02-01 | 2024-03-08 | 深圳代码兄弟技术有限公司 | Control method and device for low-code development platform and readable storage medium |
| CN117687681A (en) * | 2024-02-02 | 2024-03-12 | 浩鲸云计算科技股份有限公司 | Version management method and system for low-code application |
| CN117931159A (en) * | 2024-03-22 | 2024-04-26 | 鱼快创领智能科技(南京)有限公司 | Cloud native security-based low-code platform building system |
-
2022
- 2022-09-06 CN CN202211082374.3A patent/CN116860223A/en active Pending
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117252180A (en) * | 2023-11-16 | 2023-12-19 | 太平金融科技服务（上海）有限公司 | Report generation method and device, electronic equipment and storage medium |
| CN117252180B (en) * | 2023-11-16 | 2024-02-23 | 太平金融科技服务（上海）有限公司 | Report generation method and device, electronic equipment and storage medium |
| CN117289916A (en) * | 2023-11-24 | 2023-12-26 | 美云智数科技有限公司 | Digital intelligent PaaS platform system |
| CN117667063A (en) * | 2024-02-01 | 2024-03-08 | 深圳代码兄弟技术有限公司 | Control method and device for low-code development platform and readable storage medium |
| CN117667063B (en) * | 2024-02-01 | 2024-04-05 | 深圳代码兄弟技术有限公司 | Control method and device for low-code development platform and readable storage medium |
| CN117687681A (en) * | 2024-02-02 | 2024-03-12 | 浩鲸云计算科技股份有限公司 | Version management method and system for low-code application |
| CN117687681B (en) * | 2024-02-02 | 2024-05-14 | 浩鲸云计算科技股份有限公司 | Version management method and system for low-code application |
| CN117931159A (en) * | 2024-03-22 | 2024-04-26 | 鱼快创领智能科技(南京)有限公司 | Cloud native security-based low-code platform building system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11023834B2 (en) | Collaborative design systems, apparatuses, and methods | |
| US11789715B2 (en) | Systems and methods for transformation of reporting schema | |
| CN116860223A (en) | Cloud-protogenesis-based low-code development and delivery method | |
| US10673932B2 (en) | System and method for abstraction of objects for cross virtual universe deployment | |
| JP6634188B1 (en) | User interface extender | |
| US20200167143A1 (en) | Systems and methods for automated retrofitting of customized code objects | |
| US20160299745A1 (en) | Development method for web development system, and web development system | |
| CN111178023A (en) | Visual self-defined report design system | |
| US10885087B2 (en) | Cognitive automation tool | |
| US20110145735A1 (en) | Model driven content development | |
| US20210103863A1 (en) | Cross-enterprise workflow adaptation | |
| US10956868B1 (en) | Virtual reality collaborative workspace that is dynamically generated from a digital asset management workflow | |
| JP2013518321A (en) | Pattern-based user interface | |
| US8788533B2 (en) | Read access logging | |
| Foster | CodeIgniter web application blueprints | |
| WO2020242591A1 (en) | Ingesting and processing content types | |
| CN114546563A (en) | Multi-tenant page access control method and system | |
| AU2021411481B2 (en) | System and method for real-time, dynamic creation, delivery, and use of customizable web applications | |
| TWI620134B (en) | Integration device and integration method thereof | |
| CN114679366B (en) | Tenant-oriented operation and maintenance tool opening method, system and medium in multi-cloud environment | |
| US20220311772A1 (en) | Security Mechanisms for Content Management Systems | |
| CN115883353A (en) | Routing plug-in arranging and executing system based on Spring Cloud Gateway in trusted environment | |
| Tarkhanov | Access Control Model for Collaborative Environments in ECM | |
| DSI et al. | AXMEDIS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |