Low-code platform application deployment method and device

Abstract

The invention discloses a low-code platform application deployment method and device. The method comprises the steps of obtaining a JSON template file of a low-code platform application, generating a Hash identifier of the JSON template file and generating a Docker mirror image definition file; matching the Hash identifier of the JSON template with the Hash identifier of a historical Docker mirror image in a preset mirror image library; when the matching fails, generating a Docker mirror image of the JSON template file according to the Docker mirror image definition file; and generating a low-code platform application container according to configuration information of a to-be-deployed server and the Docker mirror image. By means of containerization and dynamic template analysis, one-time design and multi-environment delivery are achieved, the compatibility problem of cross-environment deployment of a traditional low-code platform is solved, and the application deployment efficiency of the low-code platform is improved; meanwhile, the standardized user system docking module reduces the technical threshold of docking a heterogeneous system by an enterprise.

Description

Technical Field

[0001] This application relates to the field of software development and deployment, and particularly to a method and device for deploying low-code platform applications. Background Art

[0002] With the wide application of low-code platforms in the digital transformation of enterprises, problems in the deployment of low-code platform applications have emerged. Existing methods for deploying low-code platform applications need to repeatedly develop and adapt the code when docking with different user centers (such as Keycloak, enterprise SSO), and the deployment process requires manual configuration of application databases, front-end resources, and server-side interfaces, resulting in incompatible deployment environments, low efficiency, and error-prone. Summary of the Invention

[0003] Embodiments of this application provide a method and device for deploying low-code platform applications, which are used to solve the problem of incompatible and inefficient deployment environments of existing low-code platform applications.

[0004] Embodiments of this application adopt the following technical solutions: On the one hand, embodiments of this application provide a method for deploying low-code platform applications, which includes: obtaining a JSON template file of a low-code platform application, generating a hash identifier of the JSON template file, and generating a Docker image definition file; matching the hash identifier of the JSON template with the hash identifiers of historical Docker images in a preset image library; when the matching fails, generating a Docker image of the JSON template file according to the Docker image definition file; and generating a low-code platform application container according to the configuration information of the server to be deployed and the Docker image.

[0005] In one example, the method further includes: when the matching is successful, generating a low-code platform application container according to the configuration information of the preset server to be deployed and the matched Docker image.

[0006] In one example, before generating a low-code platform application container according to the configuration information of the server to be deployed and the Docker image, the method further includes: obtaining the URL and key of the user center through the user service client depending on the user center of the server to be deployed; registering a ClientRegistration instance according to the URL and the key; and constructing a standardized interface of the server to be deployed according to the ClientRegistration instance.

[0007] In one example, according to the configuration information of the server to be deployed and the Docker image, a low-code platform application container is generated, specifically including: reading the JSON template file in the Docker image through a Spring Boot service to determine the initial data table structure and the initial registration interface of the container; filling the initial data table structure and the initial registration interface of the container according to the type of the server to be deployed to obtain the data table structure and the registration interface of the server to be deployed; forwarding the front-end request of the server to be deployed to the static resource directory, and forwarding the data request of the server to be deployed to the back-end Spring Boot service to build a low-code platform application container.

[0008] In one example, after generating a low-code platform application container according to the configuration information of the server to be deployed and the Docker image, the method further includes: when it is detected that the deployed low-code platform application needs to be updated, comparing the version number of the new JSON template file with the version number of the JSON template file; if the version number of the new JSON template file is higher than the version number of the JSON template file, verifying whether the format of the new JSON template file meets the requirements through JSON Schema; if it meets the requirements, determining whether the compatibility of the new JSON template file meets the requirements; when it meets the requirements, replacing the JSON template file with the new JSON template file; when it does not meet the requirements, retaining the JSON template file.

[0009] In one example, determining whether the compatibility of the new JSON template file meets the requirements specifically includes: determining whether there is an operation of deleting fields in the data table structure of the new JSON template file; if so, determining that the compatibility of the new JSON template file meets the requirements; if not, determining that the compatibility of the new JSON template file does not meet the requirements.

[0010] In one example, replacing the JSON template file with the new JSON template file specifically includes: generating a new Docker image according to the new JSON template file, and generating an updated low-code platform application container according to the new Docker image and the configuration information of the server to be deployed; starting the updated low-code platform application container through a container orchestration tool; switching the data request of the server to be deployed to the updated low-code platform application container, and closing the low-code platform application container after determining that there is no server request in the low-code platform application container.

[0011] In one example, before replacing the JSON template file with the new JSON template file, the method further includes: backing up the current JSON template file and the server running status through a database snapshot; storing the backup data in a preset Minio database, where the backup data includes a timestamp and the version number of the current JSON template file.

[0012] In one example, the method further includes: when the replacement fails, restoring and deploying the deployed low-code platform application container according to the backup data in the Minio database.

[0013] On the other hand, an embodiment of the present application provides a low-code platform application deployment device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute a low-code platform application deployment method according to any one of the above.

[0014] The above at least one technical solution adopted by the embodiment of the present application can achieve the following beneficial effects: The present application realizes "one design, multi-environment delivery" through containerization and dynamic template parsing, solves the compatibility problem of cross-environment deployment of traditional low-code platforms, improves the efficiency of low-code platform application deployment. At the same time, the standardized user system docking module reduces the technical threshold for enterprises to dock heterogeneous systems; non-technical background personnel can quickly iterate the business system by modifying the JSON template, reducing the dependence on professional development teams. The containerized deployment and image reuse mechanism reduce server resource consumption and improve hardware utilization. Generally speaking, from template design, image construction, version upgrade to rollback, the full process of low-code platform application is automated, reducing manual intervention and avoiding operation errors. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions of the present application, the following will detail some embodiments of the present application in conjunction with the drawings, where: Figure 1 is a schematic flowchart of a low-code platform application deployment method provided by an embodiment of the present application; Figure 2 is a schematic structural diagram of a low-code platform application deployment device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0016] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.

[0017] The following will refer to the drawings to elaborate on some embodiments of this application in detail.

[0018] Figure 1 It is a schematic flowchart of a method for deploying low-code platform applications provided by an embodiment of this application. This method can be applied to different business fields. Some input parameters or intermediate results in this process allow manual intervention and adjustment to help improve accuracy.

[0019] The implementation of the analysis method involved in the embodiments of this application can be a terminal device or a server, and this application places no special restrictions on this. For the convenience of understanding and description, the following embodiments will be described in detail by taking a controller as an example.

[0020] It should be noted in advance that: In the Spring Security OAuth2 client system, the ClientRegistration instance is the core data carrier for describing the client configuration of third-party authentication / authorization services (such as Keycloak, Auth0, GitHub, WeChat, etc.). Its essence is the encapsulation of "information required for the client to interact with the authentication provider".

[0021] Minio is an open-source high-performance distributed object storage system developed based on the Go language. Its design goal is to provide a lightweight, highly compatible, and scalable object storage solution for private cloud and public cloud environments. Its core advantage lies in being fully compatible with the Amazon S3 interface, supporting the storage and management of large-scale unstructured data (such as files, pictures, videos, logs, binary data, etc.), and is applicable to scenarios such as cloud computing, big data analysis, containerized deployment, and machine learning.

[0022] Based on this, Figure 1 the process in S101: Obtain the JSON template file of the low-code platform application, generate the hash identifier of the JSON template file, and generate the Docker image definition file.

[0023] It should be noted that in some embodiments of the present application, the user uploads a JSON template file containing the front-end layout, server-side logic, database table structure, and user configuration through the platform interface. The system generates a unique hash identifier for the template, and the JSON template files corresponding to applications developed by different low-code platforms are different; and each JSON template file has a unique hash identifier.

[0024] Furthermore, by calling the Docker Engine API, a Docker image definition file and a build context (including front-end static files, server-side JAR packages, and Nginx configurations) for the template file are generated based on the JSON template file.

[0025] S102: Match the hash identifier of the JSON template with the hash identifiers of historical Docker images in the preset image repository.

[0026] It should be noted that in some embodiments of the present application, before generating the Docker image of the JSON template file, it is necessary to search for the hash identifier of the JSON template file in the historical records of the preset image repository to see if there is the same hash identifier in the image repository. If there is the same hash identifier, that is, when the matching is successful, the successfully matched Docker image is directly reused, and a low-code platform application container is generated according to the configuration information of the preset server to be deployed and the matched Docker image.

[0027] S103: When the matching fails, generate the Docker image of the JSON template file according to the Docker image definition file.

[0028] It should be noted that in some embodiments of the present application, if there is no same hash identifier in the image repository, that is, when the matching fails, the system will execute the Docker build command to generate an image with the tag being the hash identifier of the JSON template, and push it to the image repository for storage and record the mapping relationship.

[0029] S104: Generate a low-code platform application container according to the configuration information of the server to be deployed and the Docker image.

[0030] It should be noted that in some embodiments of the present application, before generating a low-code platform application container based on the configuration information of the server to be deployed and the Docker image, the user service client will depend on docking with the user center of the server to be deployed to obtain the URL and key of the user center of the deployment server, and then register a ClientRegistration instance according to the URL and key of the user center. Finally, a standardized interface of the server to be deployed is constructed based on the ClientRegistration instance.

[0031] Furthermore, after the standardized interface of the server to be deployed is constructed, the SpringBoot service reads the JSON template file in the Docker image to determine the initial data table structure and the initial registration interface of the container, and then fills and improves the initial data table structure and the initial registration interface of the container according to the type of the server to be deployed, so as to obtain the data table structure and the registration interface of the server to be deployed.

[0032] Meanwhile, forward the front-end requests of the server to be deployed to the static resource directory, and forward the data requests of the server to be deployed to the back-end SpringBoot service to build a low-code platform application container.

[0033] Furthermore, after the low-code platform application container is deployed, when it is detected that the deployed low-code platform application needs to be updated, compare the version number of the new JSON template file with the version number of this JSON template file. If the version number of the new JSON template file is higher than the version number of this JSON template file, verify whether the format of the new JSON template file meets the requirements through JSON Schema. If it meets the requirements, then determine whether the compatibility of the new JSON template file meets the requirements, that is, determine whether there is an operation of deleting fields in the data table structure of the new JSON template file. If not, it is determined that the compatibility of the new JSON template file meets the requirements. If so, it is determined that the compatibility of the new JSON template file does not meet the requirements. When it meets the requirements, replace this JSON template file with the new JSON template file. When it does not meet the requirements, keep this JSON template file and do not update this JSON template file.

[0034] Furthermore, when updating the JSON template file, generate a new Docker image according to the new JSON template file, and generate an updated low-code platform application container according to the new Docker image and the configuration information of the server to be deployed; start the updated low-code platform application container through the container orchestration tool; Switch the data requests of the server to be deployed to the updated low-code platform application container, and close it after determining that there are no server requests in the low-code platform application container.

[0035] Finally, it should be noted that before replacing the JSON template file, that is, before updating the low-code platform application, the current JSON template file and server running status will be backed up through the database snapshot, and the backup data will be stored in the preset Minio database. The backup data includes but is not limited to the timestamp and the current JSON template file version number. When the replacement fails, that is, when the application update fails, the deployed low-code platform application container will be restored and deployed according to the backup data in the Minio database.

[0036] It should be noted that although the embodiments of this application are based on Figure 1 Steps S101 to S104 are described in sequence, but this does not mean that steps S101 to S104 must be performed in a strict order. Figure 1 The order shown in FIG1 is to introduce and explain step S101 to step S104 in order to facilitate those skilled in the art to understand the technical solution of the embodiment of the present application. In other words, in the embodiment of the present application, the order between step S101 to step S104 can be appropriately adjusted according to actual needs.

[0037] pass Figure 1 The method uses containerization and dynamic template parsing to achieve "one-time design, multi-environment delivery", solving the compatibility issues of traditional low-code platforms deployed across environments and improving the efficiency of low-code platform application deployment. At the same time, the standardized user system docking module lowers the technical threshold for enterprises to dock with heterogeneous systems; non-technical personnel can quickly iterate business systems by modifying JSON templates, reducing dependence on professional development teams. Containerized deployment and image reuse mechanisms reduce server resource consumption and improve hardware utilization. Overall, from template design, image building, version upgrades to rollbacks, the entire low-code platform application process is automated, reducing manual intervention and avoiding operational errors.

[0038] Figure 2 A schematic diagram of the structure of a low-code platform application deployment device provided in an embodiment of the present application includes: at least one processor; and, a memory communicatively connected to at least one processor; wherein, The memory stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable at least one processor to execute any one of the above-mentioned low-code platform application deployment methods.

[0039] A non-volatile computer storage medium for low-code platform application deployment provided by some embodiments of the present application stores computer-executable instructions that can execute a low-code platform application deployment method as described in any one of the above.

[0040] Each embodiment in the present application is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and reference can be made to the corresponding parts of the method embodiments for relevant explanations.

[0041] The devices and media provided by the embodiments of the present application correspond one-to-one with the methods. Therefore, the devices and media also have beneficial technical effects similar to those of their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be elaborated here.

[0042] Those skilled in the art should understand that the embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0043] The present invention is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0044] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0045] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide for implementing the steps in a process Figure 1 a process or multiple processes and / or blocks Figure 1 the steps of the functions specified in a block or multiple blocks.

[0046] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0047] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and non-volatile memory such as read-only memory (ROM) or flash RAM. The memory is an example of computer-readable media.

[0048] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can store information by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0049] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, commodity or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the existence of another identical element in the process, method, commodity or device comprising the element.

[0050] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the technical principle of the present application shall fall within the protection scope of the present application.

Claims

1. A method for deploying applications on a low-code platform, characterized in that, The method includes: Obtain the JSON template file of the low-code platform application, generate the hash identifier of the JSON template file, and generate the Docker image definition file; Match the hash identifier of the JSON template with the hash identifiers of the historical Docker images in the preset image repository; When the matching fails, generate the Docker image of the JSON template file according to the Docker image definition file; the tag of the Docker image is the hash identifier of the JSON template file; Generate the low-code platform application container according to the configuration information of the server to be deployed and the Docker image.

2. The method according to claim 1, wherein The method further includes: When the matching is successful, generate the low-code platform application container according to the configuration information of the preset server to be deployed and the matched Docker image.

3. The method according to claim 1, characterized in that, Before generating the low-code platform application container according to the configuration information of the server to be deployed and the Docker image, the method further includes: Obtain the URL and key of the user center of the server to be deployed through the user service client depending on the docked user center; Register the ClientRegistration instance according to the URL and the key; Construct the standardized interface of the server to be deployed according to the ClientRegistration instance.

4. The method according to claim 1, characterized in that Generating the low-code platform application container according to the configuration information of the server to be deployed and the Docker image specifically includes: Read the JSON template file in the Docker image through the SpringBoot service to determine the initial data table structure of the container and the initial registration interface of the container; Fill the initial data table structure of the container and the initial registration interface of the container according to the type of the server to be deployed to obtain the data table structure and the registration interface of the server to be deployed; Forward the front-end requests of the server to be deployed to the static resource directory, and forward the data requests of the server to be deployed to the back-end SpringBoot service to construct the low-code platform application container.

5. The method according to claim 1, wherein After generating the low-code platform application container according to the configuration information of the server to be deployed and the Docker image, the method further includes: When it is detected that the deployed low-code platform application needs to be updated, compare the version number of the new JSON template file with the version number of the JSON template file; If the version number of the new JSON template file is higher than the version number of the JSON template file, verify whether the format of the new JSON template file meets the requirements through JSON Schema; If it meets the requirements, determine whether the compatibility of the new JSON template file meets the requirements; When it meets the requirements, replace the JSON template file with the new JSON template file; When it does not meet the requirements, keep the JSON template file.

6. The method according to claim 5, characterized in that, Determining whether the compatibility of the new JSON template file meets the requirements specifically includes: Determine whether there is an operation of deleting fields in the data table structure of the new JSON template file; Otherwise, determine that the compatibility of the new JSON template file meets the requirements; If so, determine that the compatibility of the new JSON template file does not meet the requirements.

7. The method according to claim 5, wherein The replacing the JSON template file with the new JSON template file specifically includes: Generating a new Docker image according to the new JSON template file, and generating an updated low-code platform application container according to the configuration information of the new Docker image and the server to be deployed; Starting the updated low-code platform application container through a container orchestration tool; Switching the data requests of the server to be deployed to the updated low-code platform application container, and closing the low-code platform application container after determining that there are no server requests in the low-code platform application container.

8. The method according to claim 5, characterized in that Before replacing the JSON template file with the new JSON template file, the method further includes: Backing up the current JSON template file and the server running status through a database snapshot; Storing the backup data in a preset Minio database, where the backup data includes a timestamp and the version number of the current JSON template file.

9. The method according to claim 8, wherein The method further includes: When the replacement fails, restoring and deploying the deployed low-code platform application container according to the backup data in the Minio database.

10. A low-code platform application deployment device, characterized in that, Including: At least one processor; And, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a low-code platform application deployment method according to any one of claims 1-8 above.

Images