Construction method and equipment of low-code application and storage medium

Receive application construction requests for low-code platforms through container cloud platform, generate application images and deployment packages, store them in preset data warehouses, decouple the application construction and release process, and solves the strong coupling problem in the application development and construction process of low-code platforms. , realizes lightweight application delivery and deployment across cloud and networks, and improves deployment flexibility and efficiency.

CN119045805AInactive Publication Date: 2024-11-29ZHEJIANG DAHUA TECH CO LTD

Patent Information

Application Number
CN202411481327.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-23
Publication Date
2024-11-29
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing low-code platforms have strong coupling in the application development and construction process, which leads to the complex and inflexible application release and deployment process, making it difficult to achieve lightweight delivery and deployment across cloud and networks.

Method used

Receive application construction requests sent by low-code platforms through container cloud platforms, generate application images and deployment packages, and store them in preset data warehouses, decouple the application construction and release process, making application construction and deployment independent and supporting cross-border Deployment of container cloud and network.

Benefits of technology

It realizes lightweight cross-cloud and cross-network delivery and deployment of low-code applications, reduces dependence on low-code platforms, ensures the independence of application release and business construction, and improves deployment flexibility and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119045805A_ABST
    Figure CN119045805A_ABST
Patent Text Reader

Abstract

The invention discloses a low-code application construction method and device and a storage medium. The low-code application construction method comprises the steps that a container cloud platform receives an application construction request corresponding to a target application sent by a low-code platform; in response to the application construction request, obtaining application construction data on which the target application depends; constructing an application mirror image corresponding to the target application by utilizing a mirror image creation file in the application construction data; packaging resources and configurations required for deploying the target application by using an application deployment template file in the application construction data to obtain an application deployment package corresponding to the target application; and taking the application mirror image and the application deployment package as an application construction result of the target application, and sending the application construction result to a preset data warehouse for storage. The low-code application is decoupled from a low-code platform, lightweight cross-container cloud and cross-network application delivery and deployment can be realized, and if different container clouds can share a preset data warehouse.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of low-code platform technology, and in particular to a method, device and storage medium for constructing a low-code application. Background Art

[0002] Low Code is a visual application development method with zero or low code. The low-code platform is a digital technology tool platform that utilizes the low-code development method. It uses a visual graphical interface to quickly build low-code applications through intuitive and efficient methods such as drag-and-drop, parameterized configuration, etc., thus overcoming the limitations of traditional application software such as long development cycle and high technical barriers.

[0003] At present, low-code applications are completely implemented on low-code platforms from the initial page construction to service launch. Summary of the invention

[0004] The present application at least provides a method, device and storage medium for building a low-code application to decouple the relationship between application development and application construction, thereby facilitating the delivery and deployment of lightweight applications across clouds and networks.

[0005] The first aspect of the present application provides a method for building a low-code application, which is applied to a container cloud platform, and the method includes: receiving an application building request corresponding to a target application sent by a low-code platform; wherein the low-code platform is used to edit the target application to generate application building data that the target application depends on, and the application building data contains an image creation file and an application deployment template file, and the image creation file contains instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies and resource configurations of the target application; in response to the application building request, obtaining the application building data that the target application depends on; using the image creation file in the application building data to build an application image corresponding to the target application; and using the application deployment template file in the application building data to package the resources and configurations required for deploying the target application to obtain an application deployment package corresponding to the target application; using the application image and the application deployment package as the application building results of the target application, and sending them to a preset data warehouse for storage.

[0006] In one embodiment, the container cloud platform is deployed with a cloud-native workflow engine; after receiving an application build request corresponding to a target application sent by a low-code platform, the method further includes: obtaining a predefined workflow template; the cloud-native workflow engine generates an application build workflow based on the workflow template, and the application build workflow consists of multiple task instances; wherein, a task instance is used to obtain application build data that the target application depends on, a task instance is used to use an image creation file in the application build data to build an application image corresponding to the target application, and a task instance is used to use an application deployment template file in the application build data to package the resources and configurations required to deploy the target application to obtain an application deployment package corresponding to the target application.

[0007] In one embodiment, the method also includes: in response to the failure of a task instance to execute, deleting the file data generated during the execution of the failed task instance, and recreating the failed task instance; in response to the cumulative number of failed executions of any task instance being greater than a failure number threshold, terminating the application building workflow, and generating an exception log based on the task execution information of the failed task instance.

[0008] In one embodiment, the method also includes: obtaining workflow template modification parameters based on the received template modification instructions, or analyzing the exception log generated by the failed execution of the task instance corresponding to the workflow template to obtain the workflow template modification parameters; using the workflow template modification parameters to modify the workflow template to obtain an updated workflow template; generating an application construction workflow based on the updated workflow template.

[0009] In one embodiment, the low-code platform sends application build data to a file server for storage, and the application build request carries the storage path of the application build data; in response to the application build request, the application build data that the target application depends on is obtained, including: extracting the storage path of the application build data corresponding to the target application carried in the application build request; and obtaining the application build data that the target application depends on from the file server based on the storage path.

[0010] In one embodiment, the method further includes: in response to an application deployment request of the target application, obtaining an application image and an application deployment package of the target application from a preset data warehouse, and sending the application image and the application deployment package of the target application to an application deployment end for deployment.

[0011] The second aspect of the present application provides another method for building a low-code application, which is applied to a low-code platform. The method includes: editing a target application based on the received application editing instructions, generating application build data that the target application depends on, the application build data containing an image creation file and an application deployment template file, the image creation file containing instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies and resource configurations of the target application; based on the received application build instructions, sending an application build request corresponding to the target application to the container cloud platform, so that the container cloud platform responds to the application build request, obtains the application build data that the target application depends on, uses the image creation file in the application build data to build an application image corresponding to the target application, and uses the application deployment template file in the application build data to package the resources and configurations required to deploy the target application, obtains an application deployment package corresponding to the target application, uses the application image and the application deployment package as the application build results of the target application, and sends them to a preset data warehouse for storage.

[0012] In one embodiment, after editing the target application based on the received application editing instruction and generating the application build data that the target application depends on, the method also includes: performing data compression processing on the application build data to obtain an application build data compressed package; sending the application build data compressed package to a file server for storage, and obtaining the storage path of the application build data compressed package; based on the received application build instruction, sending an application build request corresponding to the target application to the container cloud platform, including: generating an application build request carrying the storage path of the application build data compressed package, and sending the application build request to the container cloud platform, so that the container cloud platform obtains the application build data compressed package from the file server based on the storage path, and decompresses the application build data compressed package to obtain the application build data.

[0013] The third aspect of the present application provides a container cloud platform application construction device, which is applied to a container cloud platform, and the device includes: a construction request receiving module, which is used to receive an application construction request corresponding to a target application sent by a low-code platform; wherein the low-code platform is used to edit the target application to generate application construction data that the target application depends on, and the application construction data contains an image creation file and an application deployment template file, and the image creation file contains instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies and resource configurations of the target application; a data acquisition module, which is used to respond to the application construction request and obtain the application construction data that the target application depends on; a file generation module, which is used to use the image creation file in the application construction data to build an application image corresponding to the target application; and, using the application deployment template file in the application construction data to package the resources and configurations required for deploying the target application to obtain an application deployment package corresponding to the target application; a file storage module, which is used to use the application image and the application deployment package as the application construction results of the target application, and send them to a preset data warehouse for storage.

[0014] The fourth aspect of the present application provides a low-code platform application construction device, which is applied to a low-code platform. The device includes: an application editing module, which is used to edit the target application based on the received application editing instructions, and generate application construction data that the target application depends on, the application construction data contains an image creation file and an application deployment template file, the image creation file contains instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies and resource configuration of the target application; a construction instruction sending module, which is used to send an application construction request corresponding to the target application to the container cloud platform based on the received application construction instructions, so that the container cloud platform responds to the application construction request, obtains the application construction data that the target application depends on, uses the image creation file in the application construction data to build the application image corresponding to the target application, and uses the application deployment template file in the application construction data to package the resources and configurations required for deploying the target application, obtains the application deployment package corresponding to the target application, uses the application image and the application deployment package as the application construction results of the target application, and sends them to a preset data warehouse for storage.

[0015] The fifth aspect of the present application provides an electronic device including a memory and a processor, the processor being used to execute program instructions stored in the memory to implement the above-mentioned method for constructing a low-code application.

[0016] The sixth aspect of the present application provides a computer-readable storage medium on which program instructions are stored, and when the program instructions are executed by a processor, the method for constructing the above-mentioned low-code application is implemented.

[0017] The above scheme receives an application build request corresponding to the target application sent by the low-code platform through the container cloud platform; in response to the application build request, obtains the application build data that the target application depends on; uses the image creation file in the application build data to build the application image corresponding to the target application; and uses the application deployment template file in the application build data to package the resources and configurations required for deploying the target application to obtain the application deployment package corresponding to the target application; uses the application image and the application deployment package as the application build results of the target application, and sends them to the preset data warehouse for storage, so that the application build container, the low-code platform and the application deployment container are independent of each other, ensuring the independence between the application publishing business and the application build business, and compared with the low-code platform in the related technology, the form of exporting, importing and redeploying the application is strongly bound and strongly coupled. In this application, the container cloud platform is used to build the application, so as to decouple the low-code application from the low-code platform. Subsequently, by delivering the application image and application deployment package of the low-code application, lightweight cross-container cloud and cross-network application delivery and deployment can be achieved. If different container clouds can share the preset data warehouse, the low-code application can be directly deployed online through the preset data warehouse without paying attention to the existence of the low-code platform.

[0018] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and are used together with the specification to illustrate the technical solution of the present application.

[0020] Figure 1 It is a schematic diagram of an implementation environment of a solution provided by an embodiment of the present application; Figure 2 is a flowchart of a method for building a low-code application shown in an exemplary embodiment of the present application; Figure 3 is a schematic diagram of application construction based on application construction workflow shown in an exemplary embodiment of the present application; Figure 4 is a schematic diagram of implementing an application construction workflow shown in an exemplary embodiment of the present application; Figure 5 is a flowchart of a method for building a low-code application shown in another exemplary embodiment of the present application; Figure 6 is a block diagram of a container cloud platform application construction device shown in an exemplary embodiment of the present application; Figure 7 is a block diagram of a low-code platform application building device shown in an exemplary embodiment of the present application; Figure 8 is a schematic structural diagram of an electronic device shown in an exemplary embodiment of the present application; Fig. 9 It is a schematic diagram of the structure of a computer-readable storage medium shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0021] The scheme of the embodiment of the present application is described in detail below in conjunction with the drawings of the specification.

[0022] In the following description, for the purpose of explanation rather than limitation, specific details such as specific system structures, interfaces, and technologies are provided to facilitate a thorough understanding of the present application.

[0023] The term "and / or" in this article is only an association information describing the associated objects, indicating that there may be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the previous and next associated objects are in an "or" relationship. In addition, "many" in this article means two or more than two. In addition, the term "at least one" in this article means any combination of at least two of any one or more of a plurality of, for example, including at least one of A, B, and C, can mean including any one or more elements selected from the set consisting of A, B, and C.

[0024] The embodiments of this application involve the following technical terms: Component: The basic element that constitutes the User Interface (UI). It can be divided into four categories according to the complexity of its functions: basic components, layout components, form components, and advanced components. Basic components such as input boxes, text boxes, buttons, and dialog boxes have properties, style configurations, event triggering, and response configurations.

[0025] Editor: Visual operations and configuration pages for the specific display of application content. On the configuration page, you can drag and drop components, configure components, configure application pages, preview applications, publish applications, build applications, and perform other operations.

[0026] Application: For application users, the application in the low-code platform has the general meaning of an application program. For platform developers, it specifically refers to the entity after the developed application is released. The application that can be processed by the editor, that is, the definition data of the application, is generally called schema.

[0027] Image: is a read-only file system snapshot that contains all the files, configurations, and dependencies required to run an application. It can be regarded as an executable software package that contains the application code, libraries, operating environment, and configuration. Images are the basis of containers, and one image can be used to create multiple container instances.

[0028] Container: A running instance created based on an image. A container can be considered an independently running, isolated process with its own file system, network, and process space. Container technology (such as Docker) uses operating system-level virtualization technology to achieve efficient and fast startup of containers by sharing the kernel of the host operating system.

[0029] Application runtime service image (runtime): used to build the basic image of the application service container, using Node.js as the server technology, and integrating the application interface rendering engine, process engine, business logic processing engine, permission interception management and other basic dependencies. It can automatically enable the corresponding functions according to the schema configuration, which is flexible and reliable. In addition, the basic dependencies can eliminate risks such as vulnerabilities in advance, and have high security.

[0030] Workflow: It is a component in the Argo project, which is used for container-native workflow orchestration. It provides the functions of workflow definition, operation and automation. Among them, Argo is an open source project for container-native workflow orchestration. Its workflow uses container cloud (Kubernetes, K8s)-based resources such as Pods, Jobs and CronJobs, and provides powerful control, monitoring and scheduling functions. Among them, Pod is the most basic element of the entire Kubernetes platform. Pod is a logical container of a group of container instances and is the smallest unit for Kubernetes scheduling.

[0031] Application release (published): The final step of application development. After this step, the application development is completed and officially deployed online to provide application functional services to application users. The application can be released multiple times, and each release will update the application in the service to the current configuration form. Cancel the release, that is, stop the application online service.

[0032] Application build: Generate standardized images and templates by building images for the completed applications.

[0033] The following describes the method for constructing a low-code application provided in an embodiment of the present application.

[0034] Please refer to Figure 1, which shows a schematic diagram of the implementation environment of the solution provided by an embodiment of the present application, such as Figure 1 As shown, the low-code platform and the applications created by the low-code platform are all deployed based on the same container cloud base. The low-code platform is divided into business modules and middleware modules such as front-end (web), internal gateway (gateway), application preview (runtime), application development (platform), application release (devops), and application construction (build) according to functions. Each module is an independent Pod load instance, which complies with the microservice-oriented principle of the cloud-native architecture and can perform load balancing, elastic scaling, and rolling upgrades through K8s.

[0035] The main modules of the low-code platform are described as follows: Front-end (web): contains application components and page rendering engine (referred to as application rendering engine, which can be implemented based on Vue.js, Angular.js, React.js technical framework), which renders and configures the corresponding application page UI and event response triggering between components according to the specific application schema information; Internal gateway: mainly used for filtering, interception, routing, and access control of low-code platforms; Application development (platform): The main service module of the low-code platform, responsible for business functions such as account management, permission management, application management, and data source management; Application release (devops): responsible for the dynamic deployment of low-code applications, service online and offline, application access management, and service status detection, etc., to achieve containerized deployment, upgrade, and management of application instances; Application build: The existing application build process is strongly coupled in the low-code platform, that is, the resources of the low-code platform are needed to implement application build. However, this application submits the application build process to the base K8s, so as to generate standardized images and templates for the built applications through image build, and then realize lightweight delivery and deployment of applications in the form of import and export; this application can support multiple applications to trigger builds at the same time, and support application build termination operations.

[0036] Application runtime service (runtime): Integrates hot update plug-in technology and provides an application programming interface (API) based on RESTful format to receive plug-in management client requests to dynamically iterate and update custom interface functions. At the same time, it solves the problem of insufficient resource utilization through load monitoring and the use of LRU (Least Recently Used) cache technology to enhance the agility of the low-code development model. In addition, the runtime service image integrates additional dependencies such as NodeJs on the web image, so the application runtime service can come with an independent application rendering engine.

[0037] like Figure 1 As shown, the low-code platform displays the application editing page to the application developer through the front end. The application editing page configures the properties and styles of the components in a visual manner, and performs other functional configurations such as permissions and processes to realize application development. Optionally, an application building entry is deployed on the application editing page, and the application editing page receives the developer's application configuration operation, which can be used to configure the application version number, application service central processing unit (CPU), memory specification parameters, etc., and in response to the application building entry of the application editing page being triggered, the application building process of the application is started, and the low-code platform sends an application building request to the container cloud platform. The container cloud platform builds the application image and application deployment package by obtaining the application building data of the application's dependencies, so as to decouple the application building and the low-code platform. Subsequently, by exporting the application image and application deployment package, the lightweight cross-cloud and cross-network delivery of the application and its deployment to the container cloud on the application user side are realized.

[0038] See also Figure 2 , Figure 2 is a flowchart of a method for constructing a low-code application shown in an exemplary embodiment of the present application. The method for constructing a low-code application can be applied to Figure 1 The implementation environment shown is specifically executed by the container cloud platform in the implementation environment.

[0039] like Figure 2 As shown, the method for constructing a low-code application includes at least steps S210 to S240, which are described in detail as follows: Step S210: Receive an application build request corresponding to the target application sent by the low-code platform; wherein the low-code platform is used to edit the target application to generate application build data that the target application depends on, and the application build data contains an image creation file and an application deployment template file. The image creation file contains instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies and resource configurations of the target application.

[0040] Among them, the image creation file is the Dockerfile file, which contains instructions for building an application image; the application deployment template file is the Helm template file. Helm is an open source package manager. The Helm template file is used to describe the properties, dependencies, and resource configuration of the target application.

[0041] Of course, the application construction data may also include other data, such as schema, function methods, fonts, pictures and other resource data that the target application depends on, and this application does not limit this.

[0042] Step S220: In response to the application building request, obtain application building data that the target application depends on.

[0043] Exemplarily, the low-code platform can directly send the application build data to the container cloud platform, or the low-code platform can pre-store the application build data in a file server, and the container cloud platform obtains the application build data from the file server. This application does not limit this.

[0044] Step S230: using the image creation file in the application building data to build an application image corresponding to the target application; and using the application deployment template file in the application building data to package the resources and configurations required to deploy the target application to obtain an application deployment package corresponding to the target application.

[0045] The Dockerfile file defines an image based on the application runtime service image (runtime), and uses the COPY command to copy the resource data in the application build data to the specified working directory corresponding to the application runtime service. Finally, the ENTRYPOINT instruction in the Dockerfile declares the startup script of the application runtime service. The main function of the ENTRYPOINT instruction is to configure the command to be run when the container starts.

[0046] Among them, it can be to execute the Dockerfile file of the target application by calling Kaniko to build the application image corresponding to the target application. Among them, Kaniko is a tool for building container images from Dockerfile. Of course, the Dockerfile file of the target application can also be executed in other ways, and this application does not limit this.

[0047] In addition, the Helm template file is executed through the Helm tool to package the resources and configurations required for deploying the target application to obtain the application deployment package (Chart) corresponding to the target application.

[0048] Helm Chart packages all the resources and configurations required for an application into a unit, which is called an application deployment package, or Chart. Chart contains all the resources and configurations required to deploy an application.

[0049] Based on the Helm specification, the corresponding application Helm Chart package is built, so that the application can be deployed and used on other container cloud platforms. This not only further expands the scope of application use, but also reduces the difficulty of operation and maintenance, and provides a variety of application deployment methods.

[0050] Step S240: The application image and the application deployment package are used as the application construction result of the target application, and sent to a preset data warehouse for storage.

[0051] Optionally, the preset data warehouse can select the Harbor warehouse. Harbor is an open source image warehouse service for secure hosting and efficient distribution of files that meet preset standards, such as container images and Helm Charts.

[0052] Of course, other data warehouses may also be selected to store application images and application deployment packages, and this application does not limit this.

[0053] In some embodiments, the container cloud platform is deployed with a cloud-native workflow engine; after receiving an application build request corresponding to the target application sent by the low-code platform, the method also includes: obtaining a predefined workflow template; the cloud-native workflow engine generates an application build workflow based on the workflow template, and the application build workflow consists of multiple task instances; wherein, a task instance is used to obtain application build data that the target application depends on, a task instance is used to use the image creation file in the application build data to build an application image corresponding to the target application, and a task instance is used to use the application deployment template file in the application build data to package the resources and configurations required for deploying the target application to obtain an application deployment package corresponding to the target application.

[0054] The cloud-native workflow engine may be Argo Workfows (hereinafter referred to as Argo), which is an open source cloud-native workflow engine designed for parallel job orchestration and management in a K8s environment. It can define workflows in a declarative manner.

[0055] cGenerate an application building workflow through a workflow template to obtain application building data and execute low-code application building operations.

[0056] Exemplarily, the low-code platform sends application build data to a file server for storage, and the application build request carries the storage path of the application build data; in response to the application build request, the application build data that the target application depends on is obtained, including: extracting the storage path of the application build data corresponding to the target application carried in the application build request; and obtaining the application build data that the target application depends on from the file server based on the storage path.

[0057] For example, see Figure 3 , Figure 3 FIG. 1 is a schematic diagram of an exemplary embodiment of the present application showing application construction based on an application construction workflow, such as Figure 3 As shown in the figure, the application building service in the low-code platform will compress the schema, function methods, fonts, images and other resource information that the current application depends on, as well as the related Helm template files, Dockerfile files and other application building data, according to the specified directory hierarchy structure to generate an application building data compression package, and upload the application building data compression package to the file server (such as File Transfer Protocol Server, FTP server), and send an application building request to the container cloud platform. The container cloud platform submits an application building request to the K8s service through the Kubernetes connector client to request workflow creation. The request parameters carry parameters such as the storage path of the application building data compression package. K8s forwards the application building request to the cloud native workflow engine (Argo service component). Argo generates an application building workflow (workflow) based on the pre-defined workflow template (workflow Template) and the application building request parsing. The application building workflow consists of multiple task instances, so as to obtain the application building data compression package from the file server and decompress it by executing the task instance to obtain the application building data, implement application building based on the application building data, and send the application building results to the preset data warehouse for storage.

[0058] Among them, each task instance can be executed serially. Of course, some embodiments can also be executed in parallel, which is not limited in this application.

[0059] For example, see Figure 4 , Figure 4 FIG. 1 is a schematic diagram of implementing an application construction workflow shown in an exemplary embodiment of the present application. Figure 4 As shown in the figure, the workflow creates a group of task instance Pods that are executed serially, including the first task instance (Pod1), the second task instance (Pod2), and the third task instance (Pod3). The task instances are mounted with volume resources (Volum).

[0060] Each task instance is executed serially. Different task instances are responsible for executing corresponding application construction tasks. After the current task instance is completed, the occupied K8s resources will be released in time, and the next task instance will be created at the same time to continue executing the next application construction task.

[0061] For example, the first task instance is used to obtain application build data that the target application depends on. For example, the first task instance obtains the storage address of the application build data by passing it in the environment variable. If the application build data exists under the specified path corresponding to the storage address, the application build data is directly obtained. If the application build data does not exist under the specified path corresponding to the storage address, the application build data is re-downloaded and decompressed through the download address of the application build data. After the decompression is completed, the application build data is verified, such as determining the integrity of the related Dockerfile file.

[0062] After the first task instance is executed, the first task instance is destroyed and a second task instance is created.

[0063] The second task instance is used to use the image creation file in the application build data to build the application image corresponding to the target application. Specifically, in the second task instance, the build tool Kaniko is called to execute the application Dockerfile file, and after detecting that Kaniko has built the application image, the application image is pushed to the Harbor warehouse for storage.

[0064] After the second task instance is executed, the second task instance is destroyed and a third task instance is created.

[0065] The third task instance is used to use the application deployment template file in the application build data to package the resources and configurations required to deploy the target application, and obtain the application deployment package corresponding to the target application. Specifically, the application deployment package (Chart) construction work is executed through the Helm tool, and the built application deployment package is pushed to the Harbor warehouse.

[0066] In response to the completion of the execution of each of the above task instances, the workflow notifies K8s to release the volume resources (Volum) mounted by its load to clean up temporary files generated during the application construction process, release resources in time, and improve resource utilization.

[0067] It should be noted that the task instances in the above examples are only illustrative. In actual application scenarios, the specific implementation methods of the task instances will be flexibly adjusted according to different applications and deployment requirements, and this application does not limit this.

[0068] In some embodiments, an exception may occur during the execution of a task instance, resulting in execution failure. In response to the failure of the task instance, the file data generated during the execution of the failed task instance is deleted, and the failed task instance is recreated. In response to the cumulative number of execution failures of any task instance being greater than a failure number threshold, the application building workflow is terminated, and an exception log is generated based on the task execution information of the failed task instance.

[0069] Optionally, the failure number threshold may be a preset empirical value, such as a value of 2 for the failure number threshold.

[0070] Optionally, the failure number threshold can also be a flexibly calculated value. For example, each workflow template stores the cumulative number of successful constructions. If it is detected that the application construction workflow generated by the workflow template has been successfully executed, the cumulative number of successful constructions corresponding to the workflow template is increased by 1. For each task instance generated by the current workflow template, based on the importance level of each task instance and / or the cumulative number of successful constructions corresponding to the current workflow template, the failure number threshold of the task instance is calculated to determine whether the cumulative number of execution failures is greater than the failure number threshold after the task instance fails to execute. Among them, the greater the cumulative number of successful constructions corresponding to the current workflow template, and / or the higher the importance level of the task instance, the greater the calculated failure number threshold of the task instance. The importance level of the task instance can be determined based on the content of the steps executed by the task instance, and / or based on the number of dependent task instances corresponding to the task instance. The dependent task instance refers to a task instance that must wait for the task instance to be successfully executed before it can be started. The more dependent task instances there are, the higher the importance level of the task instance.

[0071] Furthermore, since the workflow template may be modified and updated, after setting the failure count threshold corresponding to each task instance according to the cumulative number of successful constructions stored in the workflow template, if it is detected that the workflow template has been modified and updated, the modified and updated template content is obtained, the task instances affected by the modified and updated template content are determined, and the degree of influence of the modified and updated template content on each associated affected task instance is determined (e.g., the higher the importance of the modified and updated template content and the more modified and updated template content, the higher the degree of influence on the corresponding associated affected task instances), so as to adjust the failure count threshold corresponding to each associated affected task instance according to the degree of influence.

[0072] If the cumulative number of execution failures of any task instance is greater than the failure number threshold, the application construction workflow is terminated and an exception log is generated based on the task execution information of the failed task instance.

[0073] The above method can flexibly set the failure count threshold of each generated task instance according to the application and / or modification and update of the workflow template, so as to limit the number of retries that can be made after the execution of each task instance fails. On the premise of improving the success rate of application construction, it avoids the waste of resources caused by defects in the workflow template itself.

[0074] Optionally, the execution status of each task instance, the exception log generated by the execution failure, etc. can also be visualized to facilitate the perception of the application construction progress and facilitate the location of the exception.

[0075] In some embodiments, workflow template modification parameters are obtained based on received template modification instructions, or workflow template modification parameters are obtained by analyzing an exception log generated by a failed execution of a task instance corresponding to the workflow template; the workflow template is modified using the workflow template modification parameters to obtain an updated workflow template; and an application construction workflow is generated based on the updated workflow template.

[0076] For example, a workflow template editing page is provided to application developers, in which relevant parameters of the workflow template can be edited. In response to a template modification instruction input by the application developer and received by the workflow template editing page, the workflow template is modified based on the workflow template modification parameters corresponding to the template modification instruction to obtain an updated workflow template.

[0077] For another example, you can also obtain the exception log generated by the failed execution of the task instance from the historical record of the application build, analyze the exception log (such as based on a pre-trained neural network with workflow exception analysis function), obtain the workflow template modification parameters, and modify the workflow template according to the workflow template modification parameters to obtain an updated workflow template.

[0078] By modifying the definition of the process in the workflow template in the container cloud, you can adjust the workflow construction steps at any time to improve the flexibility and maintainability of application construction.

[0079] In some implementations, the application deployment step includes: in response to an application deployment request of the target application, obtaining an application image and an application deployment package of the target application from a preset data warehouse, and sending the application image and the application deployment package of the target application to an application deployment end for deployment.

[0080] For example, the deployment request end requests to deploy the target application through a container cloud platform or a low-code platform, then accesses the preset data warehouse through the container cloud platform or the low-code platform to call the data download interface of the preset data warehouse to obtain the application image and application deployment package of the target application, and sends the application image and application deployment package of the target application to the application deployment end to realize the deployment of the target application.

[0081] See also Figure 5 , Figure 5 is a flowchart of a method for constructing a low-code application shown in another exemplary embodiment of the present application. The method for constructing a low-code application can be applied to Figure 1 The implementation environment shown is specifically implemented by the low-code platform in the implementation environment.

[0082] like Figure 5 As shown, the method for constructing a low-code application includes at least steps S510 to S520, which are described in detail as follows: Step S510: Edit the target application based on the received application editing instructions to generate application build data that the target application depends on. The application build data contains an image creation file and an application deployment template file. The image creation file contains instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies, and resource configuration of the target application.

[0083] Step S520: Based on the received application build instruction, an application build request corresponding to the target application is sent to the container cloud platform, so that the container cloud platform responds to the application build request, obtains the application build data that the target application depends on, uses the image creation file in the application build data to build the application image corresponding to the target application, and uses the application deployment template file in the application build data to package the resources and configurations required to deploy the target application to obtain the application deployment package corresponding to the target application, uses the application image and the application deployment package as the application build result of the target application, and sends them to the preset data warehouse for storage.

[0084] In some embodiments, after editing the target application based on the received application editing instructions and generating application build data that the target application depends on, the method also includes: performing data compression processing on the application build data to obtain an application build data compressed package; sending the application build data compressed package to a file server for storage, and obtaining a storage path of the application build data compressed package; based on the received application build instructions, sending an application build request corresponding to the target application to the container cloud platform, including: generating an application build request carrying the storage path of the application build data compressed package, and sending the application build request to the container cloud platform, so that the container cloud platform obtains the application build data compressed package from the file server based on the storage path, and decompressing the application build data compressed package to obtain the application build data.

[0085] For the execution methods of each step on the above low-code application platform side, please refer to the detailed description of each step on the container cloud platform side, which will not be repeated here.

[0086] The method for building a low-code application provided in the present application receives an application building request corresponding to a target application sent by a low-code platform through a container cloud platform; in response to the application building request, obtains application building data that the target application depends on; uses the image creation file in the application building data to build an application image corresponding to the target application; and uses the application deployment template file in the application building data to package the resources and configurations required for deploying the target application, and obtains an application deployment package corresponding to the target application; uses the application image and the application deployment package as the application building results of the target application, and sends them to a preset data warehouse for storage, so that the application building container, the low-code platform, and The application deployment containers are independent of each other, which ensures the independence between the application publishing business and the application building business. Compared with the low-code platform in the related technology, the export, import, and redeployment of applications are strongly bound and strongly coupled. In this application, the low-code application is decoupled from the low-code platform by building the application through the container cloud platform. Subsequently, by delivering the application image and application deployment package of the low-code application, lightweight cross-container cloud and cross-network application delivery and deployment can be achieved. If different container clouds can share the preset data warehouse, the low-code application can be deployed online directly through the preset data warehouse without having to worry about the existence of the low-code platform.

[0087] Figure 6 FIG. 1 is a block diagram of a container cloud platform application construction device shown in an exemplary embodiment of the present application. Figure 6 As shown, the exemplary container cloud platform application construction device 600 includes: a construction request receiving module 610, a data acquisition module 620, a file generation module 630 and a file storage module 640. Specifically: A build request receiving module 610 is used to receive an application build request corresponding to a target application sent by a low-code platform; wherein the low-code platform is used to edit the target application to generate application build data that the target application depends on, and the application build data contains an image creation file and an application deployment template file, the image creation file contains instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies, and resource configuration of the target application; The data acquisition module 620 is used to obtain application construction data that the target application depends on in response to the application construction request; The file generation module 630 is used to use the image creation file in the application construction data to build an application image corresponding to the target application; and use the application deployment template file in the application construction data to package the resources and configuration required for deploying the target application to obtain an application deployment package corresponding to the target application; The file storage module 640 is used to take the application image and the application deployment package as the application construction result of the target application and send them to a preset data warehouse for storage.

[0088] Figure 7 FIG. 1 is a block diagram of a low-code application construction device shown in an exemplary embodiment of the present application. Figure 7 As shown, the exemplary low-code platform application construction device 700 includes: an application editing module 710 and a construction instruction sending module 720. Specifically: The application editing module 710 is used to edit the target application based on the received application editing instruction, and generate application building data that the target application depends on, wherein the application building data includes an image creation file and an application deployment template file, wherein the image creation file includes instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies, and resource configuration of the target application; The build instruction sending module 720 is used to send an application build request corresponding to the target application to the container cloud platform based on the received application build instruction, so that the container cloud platform responds to the application build request, obtains the application build data that the target application depends on, uses the image creation file in the application build data to build the application image corresponding to the target application, and uses the application deployment template file in the application build data to package the resources and configurations required for deploying the target application to obtain the application deployment package corresponding to the target application, uses the application image and the application deployment package as the application build result of the target application, and sends them to the preset data warehouse for storage.

[0089] It should be noted that the low-code application construction device provided in the above embodiment and the low-code application construction method provided in the above embodiment belong to the same concept, and the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment and will not be repeated here. In actual applications, the low-code application construction device provided in the above embodiment can allocate the above functions to different functional modules as needed, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0090] See also Figure 8 , Figure 8 It is a structural diagram of an embodiment of an electronic device of the present application. The electronic device 800 includes a memory 801 and a processor 802, and the processor 802 is used to execute program instructions stored in the memory 801 to implement the steps in the embodiment of the construction method of any of the above-mentioned low-code applications. In a specific implementation scenario, the electronic device 800 may include but is not limited to: a microcomputer, a server, and in addition, the electronic device 800 may also include mobile devices such as laptops and tablets, which are not limited here.

[0091] Specifically, the processor 802 is used to control itself and the memory 801 to implement the steps in any of the above-mentioned low-code application construction method embodiments. The processor 802 may also be referred to as a central processing unit (CPU). The processor 802 may be an integrated circuit chip having the ability to process signals. The processor 802 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. In addition, the processor 802 may be implemented by an integrated circuit chip.

[0092] See also Fig. 9 , Fig. 9 1 is a schematic diagram of a computer-readable storage medium of the present application. The computer-readable storage medium 900 stores program instructions 910 that can be executed by a processor, and the program instructions 910 are used to implement the steps in any of the above-mentioned low-code application construction method embodiments.

[0093] In some embodiments, the functions or modules included in the device provided by the embodiments of the present disclosure can be used to execute the method described in the above method embodiments. The specific implementation can refer to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0094] The above description of various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced to each other, and for the sake of brevity, they will not be repeated herein.

[0095] In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0096] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of each implementation method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

Claims

1. A method for building a low-code application, characterized in that: Applied to a container cloud platform, the method includes: Receive an application building request corresponding to a target application sent by a low-code platform; wherein the low-code platform is used to edit the target application to generate application building data on which the target application depends, the application building data containing an image creation file and an application deployment template file, the image creation file containing instructions for building an application image, and the application deployment template file being used to describe the properties, dependencies and resource configuration of the target application; In response to the application construction request, obtaining application construction data on which the target application depends; Using the image creation file in the application building data to build the application image corresponding to the target application; and using the application deployment template file in the application building data to package the resources and configuration required for deploying the target application to obtain an application deployment package corresponding to the target application; The application image and the application deployment package are used as application building results of the target application and sent to a preset data warehouse for storage.

2. The method according to claim 1, characterized in that The container cloud platform is deployed with a cloud native workflow engine; after receiving an application building request corresponding to a target application sent by the low-code platform, the method further includes: Get predefined workflow templates; The cloud-native workflow engine generates an application construction workflow based on the workflow template, and the application construction workflow consists of multiple task instances; wherein, one task instance is used to obtain the application construction data that the target application depends on, one task instance is used to use the image creation file in the application construction data to build an application image corresponding to the target application, and one task instance is used to use the application deployment template file in the application construction data to package the resources and configurations required for deploying the target application to obtain an application deployment package corresponding to the target application.

3. The method according to claim 2, characterized in that The method further comprises: In response to the failure of the task instance to be executed, deleting the file data generated during the execution of the failed task instance, and recreating the failed task instance; In response to the cumulative number of execution failures of any task instance being greater than a failure number threshold, the application construction workflow is terminated, and an exception log is generated based on task execution information of the failed task instance.

4. The method according to claim 2, characterized in that: The method further comprises: Obtaining the workflow template modification parameters based on the received template modification instruction, or obtaining the workflow template modification parameters by analyzing an exception log generated by a failed execution of a task instance corresponding to the workflow template; Modifying the workflow template using the workflow template modification parameters to obtain an updated workflow template; An application construction workflow is generated based on the updated workflow template.

5. The method according to claim 1, characterized in that: The low-code platform sends the application construction data to a file server for storage, and the application construction request carries the storage path of the application construction data; The step of obtaining, in response to the application construction request, application construction data that the target application depends on, includes: Extracting a storage path of application construction data corresponding to the target application carried in the application construction request; The application construction data on which the target application depends is obtained from the file server based on the storage path.

6. The method according to claim 1, characterized in that The method further comprises: In response to the application deployment request of the target application, the application image and the application deployment package of the target application are obtained from the preset data warehouse, and the application image and the application deployment package of the target application are sent to the application deployment end for deployment.

7. A method for building a low-code application, characterized in that: Applied to a low-code platform, the method includes: Editing the target application based on the received application editing instruction, generating application building data on which the target application depends, wherein the application building data contains an image creation file and an application deployment template file, wherein the image creation file contains instructions for building an application image, and the application deployment template file is used to describe the properties, dependencies, and resource configuration of the target application; Based on the received application build instruction, an application build request corresponding to the target application is sent to the container cloud platform, so that the container cloud platform responds to the application build request, obtains the application build data that the target application depends on, uses the image creation file in the application build data to build the application image corresponding to the target application, and uses the application deployment template file in the application build data to package the resources and configuration required for deploying the target application to obtain the application deployment package corresponding to the target application, uses the application image and the application deployment package as the application build result of the target application, and sends them to a preset data warehouse for storage.

8. The method according to claim 7, characterized in that After editing the target application based on the received application editing instruction to generate the application building data that the target application depends on, the method further includes: Performing data compression processing on the application construction data to obtain an application construction data compression package; Sending the application construction data compressed package to a file server for storage, and obtaining a storage path of the application construction data compressed package; The sending, based on the received application building instruction, an application building request corresponding to the target application to the container cloud platform includes: Generate an application construction request that carries the storage path of the application construction data compression package, and send the application construction request to the container cloud platform, so that the container cloud platform obtains the application construction data compression package from the file server based on the storage path, and decompresses the application construction data compression package to obtain the application construction data.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the processor is configured to execute program instructions stored in the memory to implement the steps in the method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program instructions, and the program instructions can be executed by a processor to implement the steps in the method according to any one of claims 1 to 8.

Citation Information

Patent Citations

  • Platform tool chain integration and maintenance method, system, equipment and medium

    CN114610368A

  • Flow control method, configuration information sending method and device, and electronic equipment

    CN117640729A

  • Monitoring alarm method and device for warehousing system, warehousing system and electronic equipment

    CN117743991A

  • Application deployment method and device, equipment and medium

    CN117806662A

  • Mirror image construction method, electronic equipment and storage medium

    CN117931215A

Cited By

  • Low-code software development system

    CN119668576A

  • Cross-platform workflow development and calling system based on modular management

    CN119987781A

  • Container cloud deployment method, device and equipment based on DPC protocol

    CN120639772A

  • Kubernetes-based edge collaborative publishing method and device, and medium

    CN121309596A

  • Kubernetes-based edge collaboration publishing method, device and medium

    CN121309596B