Low-code application publishing method and system, electronic equipment and storage medium

Abstract

The invention discloses a low-code application publishing method and system, electronic equipment and a storage medium. The method comprises the steps that an application data whole library is migrated to a development environment database through an application publishing workbench; exporting a development environment execution script from the development environment database, executing the development environment execution script, and importing an execution result file of the development environment execution script into the test environment database; exporting a test environment execution script from the test environment database, executing the test environment execution script, and importing an execution result file of the test environment execution script into the production environment database; and verifying the execution result file of the imported test environment execution script in the production environment database, completing application release after successful verification, and regularly backing up the whole database data of the production environment database. According to the publishing method, data are automatically imported and exported through whole library migration and execution scripts, the publishing process is simplified, the development efficiency is improved, and rapid and accurate publishing of low-code applications is achieved.

Description

Technical Field

[0001] The present invention relates to the field of software development technology, and specifically to a method, system, electronic device and storage medium for publishing low-code applications. Background Art

[0002] For traditional pure coding development applications, the main release methods include manual release, blue-green release, canary release, and rolling release. The release tool technologies mainly include development tool packaging, Jenkins, Docker containers, etc. The overall approach is based on the packaging of source code and operation control actions.

[0003] With the rapid development of information technology, the software development industry is undergoing unprecedented changes. The traditional software development model relies on a lot of manual coding and complex development processes, which is not only time-consuming and costly, but also difficult to respond quickly to market changes. In order to overcome these challenges, low-code development platforms came into being.

[0004] Low-code development platform (LCAP for short) mainly refers to a development platform that can quickly develop and deploy customized applications with little or no programming. For example, template-driven or scripted graphical drag-and-drop programming can be used to develop a complete application consisting of a user interface, business logic, workflow, and data services. Low-code platforms greatly reduce the development threshold by providing a graphical interface, pre-built components, and automation tools, allowing non-professional developers and even business personnel to participate in application development, thereby accelerating the innovation and iteration of applications.

[0005] The construction of software products, from native code development to SaaS rental to low-code platforms, is all to reduce development costs, control project risks, and improve development efficiency, in the hope of finding more general and efficient software development solutions.

[0006] Whether the low-code platform is form-driven or model-driven, its essence is to replace the front-end interface and dynamic interface components represented by some source code with the storage of the underlying database. Compared with traditional application release, it has a natural hot deployment feature, that is, if the configuration in the database is modified accordingly, the interface will reflect the modification effect in real time. But because of this, low-code has a series of problems compared with traditional release, including low release efficiency, often there is a model comparison process between different environments; release accuracy, different configurations in different environments, such as different service interface API addresses in different environments; release anti-fragility is weak, it is difficult to form application version control based on the model, and it is impossible to deal with application launch failure or rollback required by the business. Summary of the invention

[0007] In response to the shortcomings in the prior art, the present invention provides a method, system, electronic device and storage medium for publishing low-code applications. By migrating the entire database and executing scripts to automatically import and export data, the publishing process is simplified, development efficiency is improved, and low-code applications can be quickly and accurately published.

[0008] The first object of the present invention is to provide a method for publishing a low-code application, comprising the steps of:

[0009] Migrate the entire application data library to the development environment database through the application release workbench;

[0010] Exporting a development environment execution script from a development environment database, executing the development environment execution script, and importing an execution result file of the development environment execution script into a test environment database;

[0011] Exporting the test environment execution script from the test environment database, executing the test environment execution script, and importing the execution result file of the test environment execution script into the production environment database;

[0012] The execution result file of the imported test environment execution script is verified in the production environment database. After successful verification, the application is released and the entire database data of the production environment database is backed up regularly.

[0013] As a further improvement of the present invention, the publishing method further includes:

[0014] After the execution result file of the script executed in the test environment is imported into the production environment database, the data in the production environment database is backed up;

[0015] If there are any problems with the application release, roll back the released application to the state before release based on the backup of the production environment database.

[0016] As a further improvement of the present invention, backing up the data in the production environment database includes:

[0017] Export the production environment backup execution script from the production environment database and save the production environment backup execution script to the specified directory.

[0018] As a further improvement of the present invention, rolling back the published application to the state before the publication according to the backup of the production environment database includes:

[0019] Execute the production environment backup execution script, and import the execution result file of the production environment backup execution script into the production environment database.

[0020] As a further improvement of the present invention, the production environment backup execution script only includes the table data to be published.

[0021] As a further improvement of the present invention, the executing the test environment execution script includes changing the environment dynamic variables.

[0022] The second object of the present invention is to provide a low-code application publishing system, which is used to implement the above-mentioned publishing method, including:

[0023] Application data migration module, used to migrate the entire application data library to the development environment database;

[0024] The script export and execution module is used to export the development environment execution script from the development environment database, execute the development environment execution script, and import the execution result file of the development environment execution script into the test environment database; and to export the test environment execution script from the test environment database, execute the test environment execution script, and import the execution result file of the test environment execution script into the production environment database;

[0025] The application release module is used to verify the execution result file imported into the production environment database, complete the application release after successful verification, and regularly back up the entire database data of the production environment database.

[0026] As a further improvement of the present invention, the publishing system further includes:

[0027] The backup and rollback module is used to back up the data in the production environment database after the execution result file of the script executed in the test environment is imported into the production environment database; if there is a problem with the application release, the released application will be rolled back to the state before release based on the backup of the production environment database.

[0028] The third object of the present invention is to provide an electronic device, comprising at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program, and when the program is executed by the processing unit, the processing unit executes the above-mentioned publishing method.

[0029] A fourth object of the present invention is to provide a storage medium storing a computer program executable by an electronic device, wherein when the program runs on the electronic device, the electronic device executes the above-mentioned publishing method.

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

[0031] Through the application release workbench, the entire library of application data (i.e., content delivered by developers) is migrated to the development environment database, thus avoiding the tedious model comparison process. At the same time, the use of execution scripts to automatically export and import data greatly shortens the release cycle and meets the needs of rapid iteration.

[0032] During the release process, strict script execution is used to ensure data consistency among the development environment, test environment, and production environment, thus ensuring the accuracy of application release.

[0033] The data in the production environment database is backed up through the production environment backup execution script. Once there is a problem with the application release (failure to go online or business needs to be rolled back), the execution result file of the production environment backup execution script is imported into the production environment database to quickly restore the application to the previous version, thereby reducing the release risk, achieving effective control over the application version, and enhancing the anti-fragility of application release. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 A flowchart of the release methodology for low-code applications;

[0035] Figure 2 A specific operation flow chart of the application publishing method;

[0036] Figure 3 A schematic diagram of the structure of the publishing system for low-code applications. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0038] The present invention is further described in detail below in conjunction with the accompanying drawings:

[0039] See also Figure 1 , this embodiment provides a method for publishing a low-code application, comprising the steps of:

[0040] Migrate the entire database of application data (i.e., content delivered by developers) to the private development environment database through the application publishing workbench;

[0041] Exporting a development environment execution script from a privatized development environment database, executing the development environment execution script, and importing an execution result file of the development environment execution script into a test environment database;

[0042] Export the test environment execution script from the test environment database, execute the test environment execution script, change the environment dynamic variables, and import the execution result file of the test environment execution script into the production environment database;

[0043] Verify the execution result file of the imported test environment execution script in the production environment database. Complete the application release after successful verification, and regularly back up the entire database data of the production environment database. When executing the release operation, record the detailed information of the release, including the release time, release version, etc.

[0044] The publishing method provided in this embodiment migrates the entire database of application data (i.e., content delivered by developers) to the development environment database through the application publishing workbench, thereby avoiding the tedious model comparison process. At the same time, the automated export and import of data using execution scripts greatly shortens the publishing cycle and meets the needs of rapid iteration.

[0045] During the release process, strict script execution is used to ensure data consistency among the development environment, test environment, and production environment, thus ensuring the accuracy of application release.

[0046] Furthermore, in order to achieve effective control over the application version and enhance the anti-fragility of application release, the release method further includes:

[0047] After the execution result file of the script executed in the test environment is imported into the production environment database, the data in the production environment database is backed up;

[0048] If there are any problems with the application release, roll back the released application to the state before release based on the backup of the production environment database.

[0049] The specific backup method is:

[0050] Export the production environment backup execution script from the production environment database, and save the production environment backup execution script to a specified directory, wherein the production environment backup execution script only includes the table data to be published;

[0051] If there is a problem with the application release (failure to go online or business needs to be rolled back), execute the production environment backup execution script, obtain the execution result file of the production environment backup execution script, import the execution result file of the production environment backup execution script into the production environment database, and roll back the released application to the state before release.

[0052] Each data exported from the test environment database must be backed up after being imported into the production environment database to achieve effective control of the application version. Once there is a problem with the application release (failure to go online or business needs to be rolled back), select the backup file of the corresponding backup version (the execution result file of the production environment backup execution script) to quickly restore the application to the previous version, effectively reducing the release risk and enhancing the anti-fragility of the application release.

[0053] The following, combined Figure 2, use specific examples to illustrate the specific implementation process of the above method.

[0054] Action 1: Publish application data to the workbench: Publish developer deliverables to the private development environment database through whole-library migration.

[0055] Action 2: Export table data: Export the development environment execution script from the private development environment database.

[0056] Method 1: Execute the script <2.amec-deploy_export_dev@win.sh> and use git Bash to execute the script on the local Windows operating system.

[0057] Method 2: Execute the script <2.amec-deploy_export_dev.sh> on the local Linux operating system.

[0058] The default directory where the script is executed is: D: / deploy-export-dev / today's date

[0059] Action 3: Import execution scripts: import the execution result file of the development environment execution script into the test environment database.

[0060] Method 1: Execute the script <3.amec_deploy_import_test@win>. There may be a problem with the \n character conversion.

[0061] Method 2: Execute the script <3.amec_deploy_import_test> and upload the execution result file to the corresponding directory of the Linux host.

[0062] The default directory for executing scripts: D: / deploy-export-dev / today's date

[0063] Action 4: Export table data: Export the test environment execution script from the test environment database.

[0064] Method: By executing the script <4.amec_deploy_export_test.sh>

[0065] Default storage directory: / oncon / deploy-export-test / today's date

[0066] Action 5: Execute backup export: Export the production environment backup execution script from the production environment database. The script only contains the table data to be published.

[0067] Method: Execute the script <5.amec_deploy_export_prod.sh>

[0068] Default storage directory: / oncon / deploy-export-prod / today's date

[0069] Action 6, import execution script: execute the output result file of action 4 (i.e. execute the test environment execution script), including changing the environment dynamic variables, and import the execution result file of the test environment execution script into the production environment database.

[0070] Method: Execute the script <6.amec_deploy_import_prod.sh>

[0071] Default acquisition directory: / oncon / deploy-export-test / today's date

[0072] Action 7, execute the rollback backup script import: execute the output result file of action 5 (that is, execute the production environment backup execution script), and import the execution result file of the production environment backup execution script into the production environment database.

[0073] Method: Execute the script <7.amec_deploy_rollback_prod.sh>

[0074] Default acquisition directory: / oncon / deploy-export-prod / today's date

[0075] Action 8: Perform a full database backup: Perform a full database backup of the production environment database every day.

[0076] Method: Execute the script <8.amec_whole_backup_prod>

[0077] Default acquisition directory: / oncon / whole-backup-prod / today's date

[0078] See also Figure 3 This embodiment provides a low-code application publishing system, which is used to implement the above publishing method, including:

[0079] Application data migration module, used to migrate the entire application data library to the development environment database;

[0080] The script export and execution module is used to export the development environment execution script from the development environment database, execute the development environment execution script, and import the execution result file of the development environment execution script into the test environment database; and to export the test environment execution script from the test environment database, execute the test environment execution script, and import the execution result file of the test environment execution script into the production environment database;

[0081] The application release module is used to verify the execution result file imported into the production environment database, complete the application release after successful verification, and regularly back up the entire database data of the production environment database;

[0082] The backup and rollback module is used to import the execution result file of the test environment execution script into the production environment database, and then back up the data in the production environment database; if there is a problem with the application release, the released application will be rolled back to the state before release based on the backup of the production environment database.

[0083] This embodiment provides an electronic device, including at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program, and when the program is executed by the processing unit, the processing unit executes the above-mentioned publishing method.

[0084] This embodiment provides a storage medium storing a computer program executable by an electronic device. When the program runs on the electronic device, the electronic device executes the above-mentioned publishing method.

[0085] The above are only preferred embodiments of the present invention and are 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 method for publishing a low-code application, characterized in that: Includes steps: Migrate the entire application data library to the development environment database through the application release workbench; Exporting a development environment execution script from a development environment database, executing the development environment execution script, and importing an execution result file of the development environment execution script into a test environment database; Exporting the test environment execution script from the test environment database, executing the test environment execution script, and importing the execution result file of the test environment execution script into the production environment database; The execution result file of the imported test environment execution script is verified in the production environment database. After successful verification, the application is released and the entire database data of the production environment database is backed up regularly.

2. A method for publishing a low-code application according to claim 1, characterized in that: Publishing methods also include: After the execution result file of the script executed in the test environment is imported into the production environment database, the data in the production environment database is backed up; If there are any problems with the application release, roll back the released application to the state before release based on the backup of the production environment database.

3. A method for publishing a low-code application according to claim 2, characterized in that: Backing up data in the production environment database includes: Export the production environment backup execution script from the production environment database and save the production environment backup execution script to the specified directory.

4. A method for publishing a low-code application according to claim 3, characterized in that: Rolling back a published application to its pre-release state based on the production environment database backup includes: Execute the production environment backup execution script, and import the execution result file of the production environment backup execution script into the production environment database.

5. A method for publishing a low-code application according to claim 3 or 4, characterized in that: The production environment backup execution script only includes the table data to be published.

6. A method for publishing a low-code application according to claim 1, characterized in that: The executing the test environment execution script includes changing the environment dynamic variables.

7. A low-code application publishing system, used to implement the publishing method according to any one of claims 1 to 6, characterized in that: include: Application data migration module, used to migrate the entire application data library to the development environment database; The script export and execution module is used to export the development environment execution script from the development environment database, execute the development environment execution script, and import the execution result file of the development environment execution script into the test environment database; Used to export the test environment execution script from the test environment database, execute the test environment execution script, and import the execution result file of the test environment execution script into the production environment database; The application release module is used to verify the execution result file imported into the production environment database, complete the application release after successful verification, and regularly back up the entire database data of the production environment database.

8. A low-code application publishing system according to claim 7, characterized in that: The publishing system also includes: The backup and rollback module is used to back up the data in the production environment database after the execution result file of the script executed in the test environment is imported into the production environment database; if there is a problem with the application release, the released application will be rolled back to the state before release based on the backup of the production environment database.

9. An electronic device, characterized in that: The invention comprises at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program, and when the program is executed by the processing unit, the processing unit executes the publishing method according to any one of claims 1 to 6.

10. A storage medium, characterized in that: It stores a computer program executable by an electronic device. When the program runs on the electronic device, the electronic device executes the publishing method according to any one of claims 1 to 6.

Images