Application processing system, method and equipment based on low-code platform, storage medium and program product
By integrating a low-code platform with a container management system and leveraging containerization technology and fault tolerance mechanisms, the deployment difficulties caused by the differences between the development and runtime environments of the low-code platform are resolved, enabling efficient and stable deployment of applications.
Patent Information
- Application Number
- CN202411067942.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-05
- Publication Date
- 2024-11-22
AI Technical Summary
Existing low-code platforms have significant differences between their development and runtime environments, making it difficult to deploy applications directly and requiring cumbersome configuration and debugging work, resulting in low efficiency.
By integrating a low-code development platform with a container management system, applications can be developed and packaged on terminal devices, and the application deployment package can be provided to the target worker nodes in the container management system through the server. By leveraging the containerization technology and fault tolerance mechanism of the container management system, the application can be ensured to have a consistent running environment in different environments.
It simplifies the application development and deployment process, improves development efficiency, reduces tedious configuration and debugging work, and ensures application stability and flexible deployment.
Smart Images

Figure CN119002922A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of cloud computing technology, and in particular to an application processing system, method, device, storage medium and program product based on a low-code platform. Background Art
[0002] Low Code Development Platform (LCDP) is a development platform that can quickly generate applications with little or no code. Low Code Development Platform can visualize the application development process, and users can easily create applications on a graphical user interface.
[0003] The process of developing applications on a low-code development platform usually includes the following steps: selecting components, configuring component attribute information, binding data models to components, binding events to components, and generating metadata for the application. Metadata is descriptive information about application components, data, logic, and interface layout. When using the application, the metadata of the application is parsed by the parsing engine to obtain the program code of the application, and the program code is run to run the application.
[0004] At present, there are still large differences between the development environment and the operating environment of existing low-code platforms. Applications developed by application developers in the development environment are often difficult to deploy directly to the operating environment, and require tedious configuration and debugging work, resulting in cumbersome and inefficient processes from application development to deployment. Summary of the invention
[0005] Multiple aspects of the present application provide an application processing system, method, device, storage medium and program product based on a low-code platform, which is used to develop and package applications in a development environment developed by the low-code platform, and deploy them in containers provided by the working nodes of the container management system, ensuring that the application program has a consistent operating environment in different environments, thereby simplifying the application deployment process and improving deployment efficiency.
[0006] An embodiment of the present application provides an application processing system based on a low-code platform, including: a terminal device, a server, and at least one working node in a container management system; a development environment of the low-code platform is run on the terminal device, and a container is deployed on each working node, and the container provides an operating environment of the low-code platform for running applications developed based on the low-code platform; the terminal device is used to obtain metadata of the second application generated by the development environment of the low-code platform in response to a packaging operation for the second application; an application deployment package corresponding to the second application is generated based on the metadata, and uploaded to the server; and in response to a deployment operation for the second application, application deployment information for the second application is provided to the server; the server is used to determine a target working node from at least one working node according to the application deployment information, and provide the application deployment package of the second application to the target working node, and a first application is run in the container on the target working node; the target working node is used to replace the first application running in the container with the second application based on difference information between the application deployment package of the second application and the application deployment package of the first application.
[0007] An embodiment of the present application also provides an application processing method based on a low-code platform, which is applicable to a terminal device in an application processing system based on a low-code platform, and a development environment of the low-code platform is run on the terminal device, the method comprising: in response to a packaging operation for a second application, generating metadata of the second application based on the development environment of the low-code platform; based on the metadata of the second application, generating an application deployment package corresponding to the second application, and uploading it to a server in the application processing system; and in response to a deployment operation for the second application, providing application deployment information for the second application to the server, so that the server provides the application deployment package of the second application to a target working node in the container management system based on the application deployment information, so that the target working node replaces the first application running in its container with the second application based on the difference information between the application deployment package of the second application and the application deployment package of the first application.
[0008] An embodiment of the present application also provides an application processing method based on a low-code platform, which is applicable to a server in an application processing system based on a low-code platform, the method comprising: receiving application deployment information for a second application sent by a terminal device in the application processing system, the application deployment package of the second application is packaged and generated based on the metadata of the second application generated by the development environment of the low-code platform and uploaded to the server, and the application deployment information is sent by the terminal device in response to a deployment operation for the second application; according to the application deployment information, determining a target working node from at least one working node in the container management system, a first application running in a container on the target working node; sending the application deployment package of the second application to the target working node, so that the target working node replaces the first application running in the container with the second application based on the difference information between the application deployment package of the second application and the application deployment package of the first application.
[0009] An embodiment of the present application also provides an application processing method based on a low-code platform, which is applicable to a target working node in a container management system, and a container is deployed on the target working node. The container provides an operating environment of the low-code platform for running applications developed based on the low-code platform, and a first application is running in the operating environment; the method includes: receiving an application deployment package of a second application provided by a server in an application processing system to which the container management system belongs; the application deployment package of the second application is packaged and generated based on the metadata of the second application generated by the development environment of the low-code platform and uploaded to the server; the application deployment package of the second application is compared with the application deployment package of the first application to obtain difference information between the application deployment package of the second application and the application deployment package of the first application; based on the difference information, the first application running in the container is replaced with the second application.
[0010] An embodiment of the present application also provides an electronic device, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to implement each step in the application processing based on the low-code platform provided in the embodiment of the present application.
[0011] An embodiment of the present application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor implements each step of the application processing based on the low-code platform provided in the embodiment of the present application.
[0012] An embodiment of the present application also provides a computer program, including computer programs / instructions. When the computer programs / instructions are executed by a processor, the processor implements each step in the application processing based on the low-code platform provided in the embodiment of the present application.
[0013] In an embodiment of the present application, the low-code development platform and the container management system are integrated, the application is developed and packaged in the development environment of the low-code development platform running on the terminal device, multiple application deployment packages that have been developed are maintained on the server, and the terminal device initiates an application deployment operation to the server. The server provides the application deployment package to the target working node in the container management system, and provides the operating environment of the low-code development platform in the container of the target working node. Based on the difference information between the first application currently running in the operating environment and the second application corresponding to the application deployment package, the first application running in the container of the target working node is replaced with the second application. In the whole process, the process from application development to deployment is simplified, and development efficiency is improved. Application developers do not need to pay attention to tedious configuration and debugging work, and can focus on the development of applications.
[0014] Furthermore, the containerization technology of the container management system is fully utilized to realize flexible deployment and management of applications. Containers are deployed in the working nodes of the container management system, and the operating environment of the low-code platform is deployed in the container. Applications are run in the operating environment, and versions of applications are upgraded or rolled back. Through the management and fault-tolerant mechanism of the container management system itself, in the event of a failure in the container running the application, the application is deployed to other containers based on the application deployment package to ensure the stability of the application. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0016] Figure 1 A schematic diagram of the structure of an application processing system based on a low-code platform provided for an exemplary embodiment of the present application;
[0017] Figure 2a A schematic diagram of the structure of an application packaging page provided for an exemplary embodiment of the present application;
[0018] Figure 2b A schematic diagram of the structure of a historical version page provided for an exemplary embodiment of the present application;
[0019] Figure 2c A schematic diagram of the structure of a low-code platform at design time and runtime provided for an exemplary embodiment of the present application;
[0020] Figure 2d A schematic diagram of the contents contained in an application deployment package provided by an exemplary embodiment of the present application;
[0021] Figure 2eA schematic diagram of a deployment process of an application deployment package provided for an exemplary embodiment of the present application;
[0022] Figure 3 A flowchart of an application processing method based on a low-code platform provided for an exemplary embodiment of the present application;
[0023] Figure 4 A flowchart of another application processing method based on a low-code platform provided for an exemplary embodiment of the present application;
[0024] Figure 5 A flowchart of another application processing method based on a low-code platform provided for an exemplary embodiment of the present application;
[0025] Figure 6 A schematic structural diagram of an electronic device provided for an exemplary embodiment of the present application. DETAILED DESCRIPTION
[0026] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.
[0027] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0028] Existing low-code platforms still have a large gap between the development environment and the application environment. Applications completed by developers in the development environment are often difficult to deploy directly to the production environment, requiring tedious configuration and debugging.
[0029] In an embodiment of the present application, the low-code development platform and the container management system are integrated, the application is developed and packaged in the development environment of the low-code development platform running on the terminal device, multiple application deployment packages that have been developed are maintained on the server, and the terminal device initiates an application deployment operation to the server. The server provides the application deployment package to the target working node in the container management system, and provides the operating environment of the low-code development platform in the container of the target working node. Based on the difference information between the first application currently running in the operating environment and the second application corresponding to the application deployment package, the first application running in the container of the target working node is replaced with the second application. In the whole process, the process from application development to deployment is simplified, and development efficiency is improved. Application developers do not need to pay attention to tedious configuration and debugging work, and can focus on the development of applications.
[0030] Furthermore, the containerization technology of the container management system is fully utilized to realize flexible deployment and management of applications. Containers are deployed in the working nodes of the container management system, and the operating environment of the low-code platform is deployed in the container. Applications are run in the operating environment, and versions of applications are upgraded or rolled back. Through the management and fault-tolerant mechanism of the container management system itself, in the event of a failure in the container running the application, the application is deployed to other containers based on the application deployment package to ensure the stability of the application.
[0031] A solution provided by an embodiment of the present application is described in detail below in conjunction with the accompanying drawings.
[0032] Figure 1 The following is a schematic diagram of a structure of an application processing system based on a low-code platform provided by an exemplary embodiment of the present application. Figure 1 As shown, the system includes: a terminal device 101, a server 103 and a container management system 102. The container management system includes at least one working node 104, and a container is deployed on each working node.
[0033] In this embodiment, the low-code development platform is referred to as the low-code platform, and the low-code platform includes a development environment and a running environment. Among them, the development environment is the core of the low-code platform. The development environment provides a set of visual and drag-and-drop development tools, so that application developers can quickly build and configure applications through graphical interfaces and predefined modules. This environment usually includes component libraries, data model design tools, process orchestration tools, and interface designers, etc., which are convenient for application developers to perform logical design, interface design, and data processing operations of applications. At the same time, the development environment also provides code editing and debugging functions to meet the needs of application developers to write custom codes when necessary. Among them, the running environment is the environment in which the low-code platform deploys and runs applications. It is responsible for parsing, rendering, and executing the applications built by the application developer in the development environment, so that the applications can run normally on the working nodes. The running environment is usually related to specific hardware, operating system, or cloud service platform, ensuring that the application can maintain consistent running effects in different environments. At the same time, the running environment also provides security, stability, and performance guarantees for the application, ensuring that the application can provide services to users stably and efficiently.
[0034] In this embodiment, the container management system is a container orchestration system that supports automated deployment, large-scale scalability, and application container management. When deploying an application in a production environment, multiple containers are usually managed, and the containers need to interact with the underlying network, storage and other infrastructure. The container management system shields the interaction with the infrastructure so that users can manage these containers efficiently. At the same time, the container management system also provides a complete cluster management capability. The container management system includes a control node and a worker node, and the control node and the worker node work together and cooperate with each other. The worker node is a node that runs the container and is responsible for receiving instructions from the control node and creating, starting and managing the container. The worker node usually has sufficient computing and storage resources to support the operation of the application (such as the first application or the second application). The control node is responsible for managing the operation of multiple worker nodes contained in the entire container management system, and performing control tasks such as scheduling containers, managing worker nodes, and monitoring cluster status. In contrast, the worker node focuses on executing specific containerized applications.
[0035] Among them, the container is a lightweight virtualization technology that can package applications and their dependencies into a portable environment. This environment is isolated and independent of other containers in the working node. Containers have the advantages of portability, isolation, and lightness. Among them, portability means that containers can run in any environment that supports container technology without making a lot of modifications to the working nodes. Isolation means that containers provide process-level isolation to ensure the stability and security of applications. Lightweight means that containers share the kernel of the working node, occupy less resources, and start quickly.
[0036] In this embodiment, the terminal device corresponds to the application developer, and the application developer can develop an application based on the terminal device. The terminal device can be any terminal that can run the development environment of the low-code platform, and all terminal devices that can run the development environment of the low-code platform are applicable to the embodiments of this application. For example, the terminal device may include but is not limited to: laptops, desktop computers, and smart phones. The working node corresponds to the application user, and the container in the working node can provide the application user with an operating environment for the application. The working node can be any terminal device that can run a container, and the container can provide an operating environment for the low-code platform. For example, the working node can include but is not limited to: laptops, desktop computers, and smart phones. The terminal device and the working node can communicate through the server, and the server can maintain the application deployment packages of different applications developed by the low-code development platform. Further, the server can maintain different versions of application deployment packages for each application. The server may include but is not limited to: server devices such as conventional servers, cloud servers, or server arrays.
[0037] In this embodiment, the application developer and the application user are not limited. For example, in a private cloud scenario, the application developer may be application developer A, and the application user may also be application developer A, that is, application developer A develops the application by himself and uses the application by himself. The terminal device, container management system, and server all correspond to application developer A. For another example, the application developer may be application developer B, and the application user may also be multiple users C, that is, application developer B develops the application, and multiple users C use the application developed by application developer B. Among them, the terminal device and server correspond to application developer B, and the working node in the container management system corresponds to user C, that is, user C uses the working node to run the application.
[0038] In this embodiment, the terminal device is mainly used to develop applications on the low-code platform, package the applications, and deploy the applications to the working nodes. The server is mainly used to maintain the packaged applications, and when the terminal device initiates the deployment, it selects the working node where the application can be deployed from the working nodes in the container management system as the target working node. Among them, the control node can act as a communication bridge between the server and the working node. For example, the server provides the application deployment package to the control node, and the control node provides the application deployment package to the target working node.
[0039] It should be noted that the application involved in the embodiments of the present application can be an independent software installed on a terminal device such as a computer or a mobile phone, such as an application (APP), or it can be a lightweight application, such as a "mini program", which does not need to be downloaded and installed and can be run directly on other applications. The application user can open and use it by scanning a QR code or searching.
[0040] In this embodiment, the terminal device can develop at least one application. The following is an example of developing a second application on a terminal device. The terminal device generates metadata of the second application based on the development environment of the low-code platform in response to the application development requirements provided by the application developer. Among them, the low-code platform describes and builds the second application through metadata. Metadata is a descriptive data that can define the application structure, data model, business logic, user interface, integration information, permissions and security of the second application, as well as reporting and analysis. Among them, the application structure refers to the metadata defining the architecture and components of the second application, such as screen layout, form, view or menu. The data model refers to describing the structure and type of data, such as the attributes, data types, relationships and constraints of each data entity. Business logic refers to defining the business rules and processes of the second application, such as validation rules, workflows and decision logic. The user interface refers to describing the layout, controls, styles and interactive behaviors of the user interface. Integration information refers to defining how the second application integrates with external systems and services, including application program interfaces (APIs), service endpoints and data sources. Permissions and security refer to security-related metadata such as user roles, permissions, and access control rules. Reporting and analysis refers to defining the structure of the report, data sources, and presentation methods. Among them, by using metadata, the low-code platform can build complex applications without writing traditional code, allowing non-technical users to participate in the creation and modification process of the application. Non-technical users refer to people who cannot develop application code by writing logical code. The second application developed based on metadata is configurable. The data model, interface, business logic, etc. of the second application can be implemented through configuration, so it is very flexible. When business needs change, there is no need to find a software company to modify the program code of the second application, and there is no need to wait for a long time. Through configuration, for example, the mouse modifies the properties of the component, etc., the application will change with the change of configuration. Among them, there is a conversion relationship between metadata and source code. The parsing engine provided by the low-code development platform can parse metadata into an executable program.
[0041] Among them, the implementation method of developing the second application in the development environment of the low-code platform is not limited, and an example is provided below. For example, 1) Select and design components. The terminal device displays the application development page, which includes a component area and an editing area. The component area includes various components, such as text boxes, buttons, tables, pop-ups, and charts. The application developer can drag the components in the component area to the editing area. The terminal device responds to the drag operation and displays the dragged components in the editing area according to the end position of the drag operation. 2) Configure component properties. The application developer can also configure the attribute information of the component. For example, the attribute information of the component includes but is not limited to: position, size, color, shape, behavior, and data. The terminal device can respond to the configuration operation for any component and adjust the attribute information of any component in the editing area according to the configured attribute parameters. 3) Data binding. The development environment of the low-code platform supports the application developer to define the data model, and the terminal device can respond to the data binding operation to bind the attributes of the component to the defined data model. In this way, when the data in the data model changes, the data attributes of the component will also be updated accordingly, achieving the effect of dynamically displaying the component data. 4) Event binding. In addition to data binding, you can also bind events to components. For example, in response to the application developer's operation of binding an event to any component, the terminal device can establish a binding relationship between the component and the set time; accordingly, when the application user performs a user operation on any component on the target working node, the set event bound to the component can be triggered. For example, the set event can be a page jump, a form submission, etc.
[0042] In this embodiment, the application developer can initiate a packaging operation for the second application on the terminal device, and the terminal device generates an application deployment package corresponding to the second application based on the metadata of the second application in response to the packaging operation for the second application. The second application is packaged, and based on the packaged application deployment package, the second application can be transplanted to the operating environment provided by the low-code platform of the working node for operation, so that the second application has the transplantation capability.
[0043] The application deployment package of the second application may include files and configuration information required for application deployment to ensure that the second application can be correctly installed, configured and run in the running environment. The application deployment package may be a compressed package, for example, a compressed package with a suffix of ".zip" or ".tar".
[0044] In this embodiment, the server maintains multiple application deployment packages packaged by the application developer, and different application deployment packages correspond to different versions of the same application, or different applications. For example, application deployment package Q1 and application deployment package Q2 correspond to version 2.0 and version 2.5 of the same application. For another example, application deployment package Q3 is a social application, and application deployment package Q4 is a game application. The terminal device can upload the application deployment package of the second application to the server, which is saved and maintained by the server. When the terminal device needs to deploy the application deployment package of the second application, the application deployment package is sent to the corresponding working node. Among them, when the server maintains multiple versions of the application, the version management of the application can be realized, and the historical versions of the development can be managed, including the following advantages: 1) The historical records of the application can be clearly traced, including the content, time and responsible person of each change, which is very helpful for problem troubleshooting and compliance inspection. 2) When the current running version fails, for example, the container fails or the target working node fails, the application can be redeployed based on the historical version. 3) Through version management, the application developer can more easily compare the differences between different versions and quickly locate the problem. At the same time, version management tools usually provide some automated functions, such as code merging and conflict resolution, which can further improve development efficiency. 4) Version management can help identify and fix security vulnerabilities. When a security vulnerability in an application is discovered, the affected application version can be quickly located and repaired. In addition, version management can also record the repair process of security vulnerabilities and provide rich record information for subsequent application operations. Among them, the packaged deployment storage table maintained by the server can be as follows Table 1:
[0045] Field Name Field Chinese name type Is it empty? Is it a primary key? Remark Id Auto-increment primary key Bigint no yes Primary Key Org_id Organization ID Bigint no no index App_id Application ID Bigint no no Version Version Number Varchar(20) no no Package_by Packing operator Bigint yes no Package_time Packing time Datetime yes no index Remark Remark Varchar(255) yes no Diff Difference Information Text yes no Compare with previous version Package_cost Packing time Int yes no Unit: milliseconds
[0046] Among them, Bigint is a data type used to represent very large integers; Varchar(20) represents a string field that can store up to 20 characters. Varchar(255) represents a string field that can store up to 255 characters; Datetime is a data type in the database management system used to store date and time information. It usually includes parts such as year, month, day, hour, minute, second, and can provide precision to seconds. Text is a data type that stores large amounts of text data in the database management system. Int is an integer. Among them, primary key and index are important concepts in the database, used to optimize data storage and retrieval. The primary key is a field or combination of fields used to uniquely identify each record in the database table. The index is a separate, physical storage structure that sorts the values of one or more columns in the database table, similar to the catalog of a book, which can quickly find the required content according to the page number in the catalog. The primary key is mainly used to uniquely identify and associate data, while the index is mainly used to optimize data retrieval efficiency.
[0047] In this embodiment, the application developer can initiate a deployment operation for the second application, and the terminal device responds to the deployment operation for the second application and provides application deployment information for the second application to the server. The application deployment information is a descriptive information required to successfully deploy the application deployment package to the corresponding environment. Based on the application deployment information, it can be determined which application deployment package to deploy and on which working node to deploy the application deployment package.
[0048] In this embodiment, the server receives the application deployment information for the second application; based on the application deployment information, determines the target working node from at least one working node maintained by the container management system, and provides the application deployment package of the second application to the target working node.
[0049] The container on the target working node is deployed with the operating environment of the low-code platform, and the first application is running in the operating environment. The first application and the second application can be different versions of the same application, for example, the first application is version 2.0 of application D, and the second application is version 3.0 of application D.
[0050] In this embodiment, the target working node receives the application deployment package of the second application, compares the application deployment package with the application deployment package corresponding to the first application currently running on the target working node, and obtains the difference information between the second application and the first application; based on the difference information, the first application running in the container is replaced with the second application. For example, the metadata of the first application can be updated based on the difference information, and the method of updating the metadata of the first application can include but is not limited to: adding fields, modifying fields, and deleting fields. For another example, the current operating environment can be updated based on the difference information, for example, downloading a new database or framework in the container instance, and for another example, updating the version of the low-code platform in the container instance.
[0051] In an embodiment of the present application, the low-code development platform and the container management system are integrated, the application is developed and packaged in the development environment of the low-code development platform running on the terminal device, multiple application deployment packages that have been developed are maintained on the server, and the terminal device initiates an application deployment operation to the server. The server provides the application deployment package to the target working node in the container management system, and provides the operating environment of the low-code development platform in the container of the target working node. Based on the difference information between the first application currently running in the operating environment and the second application corresponding to the application deployment package, the first application running in the container of the target working node is replaced with the second application. In the whole process, the process from application development to deployment is simplified, and development efficiency is improved. Application developers do not need to pay attention to tedious configuration and debugging work, and can focus on the development of applications.
[0052] Furthermore, the containerization technology of the container management system is fully utilized to realize flexible deployment and management of applications. Containers are deployed in the working nodes of the container management system, and the operating environment of the low-code platform is deployed in the container. Applications are run in the operating environment, and versions of applications are upgraded or rolled back. Through the management and fault-tolerant mechanism of the container management system itself, in the event of a failure in the container running the application, the application is deployed to other containers based on the application deployment package to ensure the stability of the application.
[0053] In an optional embodiment, the terminal device generates an application deployment package corresponding to the second application based on the metadata of the second application in response to the packaging operation for the second application. For example, in response to the packaging operation for the second application, the original data of the second application is obtained according to the application identification information of the second application, and the original data includes at least metadata and environment dependency information; the original data is described in a structured grammatical format to obtain structured description information corresponding to the second application; based on the metadata, environment dependency information and structured description information, the application deployment package of the second application is generated, so as to realize one-click packaging of the application program under the low-code platform, which is simple and fast.
[0054] Among them, when developing the second application, the terminal device can pre-generate the application identification information of the second application, and establish a correspondence between the application identification information and the original data. In response to the packaging operation for the second application, the terminal device obtains the application identification information of the second application, and according to the application identification information of the second application, combined with the above correspondence, the original data of the second application can be obtained. Among them, metadata is usually stored in a file with an extension of ".json", and json (JavaScript Object Notation) is a lightweight data exchange format. Among them, in addition to metadata and environment dependency information, the original data can also include: basic information of the application developer. The basic information of the application developer may include but is not limited to: the name, role, organization, and authority of the developer. Among them, the environment dependency information includes at least: description information of the low-code platform on which the second application depends, framework description information, and database description information.
[0055] Among them, the structured syntax format refers to a standardized and systematic expression method. The structured syntax format helps to understand the meaning of the original data and the logical relationship between the data. The structured syntax format is used to describe the original data through certain rules to obtain the structured description information corresponding to the second application. For example, the structured syntax format can be the YAML syntax format. YAML is a human-readable data serialization format and a simple and easy-to-use data representation language. The YAML file uses the extension ".yaml" or ".yml" and uses a syntax format similar to indentation to represent the data structure. This syntax format does not depend on a specific programming language and can be parsed and generated by multiple programming languages. Among them, the YAML syntax format has the following characteristics: 1) distinguishing between uppercase and lowercase letters. 2) Using indentation to represent hierarchical relationships. 3) Supporting multiple data types, such as objects (a collection of key-value pairs), arrays (a set of values arranged in order), and scalars (single, indivisible values). YAML is widely used in configuration and management, especially in Kubernetes. For another example, the structured syntax format can also be extensible markup language (eXtensible Markup Language, XML), etc.
[0056] The application deployment package of the second application may be generated based on the metadata, the environment dependency information, and the structured description information. For example, the metadata, the environment dependency information, and the structured description information of the second application may be packaged into a compressed package to obtain the application deployment package of the second application. For another example, the original data and the structured description information of the second application may be packaged into a compressed package to obtain the application deployment package of the second application.
[0057] For example, in Figure 2d In the figure, the application deployment package of the second application includes: metadata, developer information, basic information, low-code platform operating environment information and structured description information. The application deployment package of the second application may include full data or differential data from the previous version. Metadata includes but is not limited to: model data, interface data, component description information DSL, menus, extension codes, and version numbers of the low-code platform. Developer information includes but is not limited to: basic information of the application developer, role information (such as leader, team leader or employee), organizational information (such as department), and permission information. Basic information includes but is not limited to: application version number, team or application basic information. Low-code platform operating environment information includes but is not limited to: routing interface information, kernel information, and extended function interface information.
[0058] The following is an example of structured description information, where the information after “ / / ” is just a comment for easy understanding.
[0059]
[0060]
[0061] Optionally, in response to the packaging operation for the second application, the implementation method of obtaining the original data of the second application according to the application identification information of the second application is not limited. For example, in response to the selection operation of the second application on the application packaging page, the application version information of the second application is generated, and the packaging control is displayed; in response to the trigger operation for the packaging control, the metadata and environment dependency information of the second application are obtained based on the application identification information of the second application; the metadata, environment dependency information and application version information are used as the original data of the second application.
[0062] For example, the version information of the second application can be named according to certain naming rules, for example, the version information is named by a combination of date and serial number, the date is the date when the second application is generated, and the serial number is incremented sequentially based on the historical version. For example, the historical versions of the application to which the second application belongs are 1.0, 1.5, and 2.0, the date when the second application is generated is 20240517, and the version number is incremented by 0.5 each time, then the application version information of the second application can be 20240517_2.5.
[0063] like Figure 2aAs shown, an application packaging page is provided, and the second application is implemented as a public test application. The application packaging page includes an application selection control, and in response to a trigger operation on the application selection control, at least one application is displayed, and the at least one application includes a second application. In response to a selection operation on the second application, application version information of the second application is generated and displayed. The application version information of the second application is: 20230216_175041. Further, Figure 2a The packaging time and the packager are also displayed. The packaging time is 2023-02-16, 17:50:41, which means February 16, 2023, 17:50:41, and the packager is E0. Furthermore, the application packaging page also includes: "Package" control and "Package and Deploy" control. Among them, clicking the "Package" control can initiate a packaging operation for the second application, and clicking the "Package and Deploy" control can first initiate a packaging operation for the second application, and then initiate a deployment operation for the second application.
[0064] Further optionally, the application packaging page also includes a "historical version" control; when generating a target application deployment package corresponding to the second application, in response to a trigger operation on the historical version control, at least one deployment control corresponding to at least one application version information is displayed, and the at least one application version information includes the target application version information of the application deployment package corresponding to the second application; in response to a trigger operation on the deployment control corresponding to the target application version information, based on the target application version information, target identification information of the target application deployment package is generated, and node deployment requirement information provided by the application developer is obtained; the target identification information and the node deployment requirement information are provided to the server as application deployment information of the second application.
[0065] The node deployment requirement information is a requirement information for the equipment required for the second application to run. For example, the node deployment requirement information may include but is not limited to: node type information, hardware requirement information, network requirement information, storage requirement information, and security requirement information, etc. The node type information includes test type and online type, etc.
[0066] like Figure 2a As shown, the application packaging page also includes a "historical version" control. Click the "historical version" control, and the terminal device responds to the click operation and displays the following Figure 2b The historical version page shown in the figure shows various application versions and their corresponding deployment controls. Figure 2bThe deployment controls include: "Deploy development environment" control and "Deploy formal environment" control as examples for illustration, but are not limited to this. In addition, "Deploy test environment" control may also be included. Different types of deployment controls may deploy application deployment packages to corresponding types of working nodes or containers to achieve isolation. For detailed description, please refer to the subsequent embodiments.
[0067] besides, Figure 2b Also included is a query control for querying application deployment packages based on keywords. Figure 2b The page shown provides: an edit box for entering the application name, an edit box for entering the packager ID, an edit box for entering the version number, and a display box corresponding to the notes information. Based on the above edit boxes, the application developer can enter keywords, and the terminal device responds to the input operation, obtains the keywords, determines the application deployment package that matches the keyword based on the keywords, and displays it. For example, Figure 2b The following table shows the basic information of two application deployment packages. orgId indicates the organization ID, which can be a department, company, or group, etc., and appId indicates the application ID. Notes refers to the notes for the application deployment package, and packaging time refers to the time required to respond to the packaging operation and obtain the application deployment package. The unit of packaging time is seconds (s). "Details" is the detailed information about the application deployment package, such as developer information, basic application information, metadata, and environment dependency information.
[0068] In this embodiment, the terminal device deploys the development environment of the low-code platform, and the target work node deploys the operating environment of the low-code platform as an example for explanation. Optionally, the terminal device can also deploy the operating environment of the low-code platform, and the target work node can also deploy the development environment of the low-code platform. That is, both the terminal device and the target work node can have the operating environment and development environment of the low-code development platform.
[0069] like Figure 2cAs shown, the test environment includes: design time and runtime, and the online environment also includes: design time and runtime. The design time corresponds to the development environment of the low-code platform, and the runtime corresponds to the operating environment of the low-code platform. Among them, whether in the test environment or the online environment, at design time, the development environment of the low-code platform includes: various components, extension code, basic information of the second application, developer information and metadata, among which, the extension code is a function provided by the low-code platform to provide custom code for application developers. Application developers can write specific service logic and functions according to their own needs. This extension capability makes the application developed by the low-code platform more flexible in function and can meet the more complex and personalized needs of application developers. Metadata includes: component description information and data model. The component description information can describe the relationship between components and components through a domain-specific language (Domain Specific Language, DSL). Among them, the data model refers to the data bound to the component, and the properties of the component can change with the change of the data. At runtime, the operating environment, service data and user permissions of the low-code platform on the target working node, the operating environment of the low-code platform provides an operating environment for the second application, including: application developers, routing interfaces, parsing engines, metadata, components and extension codes, etc. User permissions can be the access rights that application users have for applications. The design and runtime involved in the online environment and the test environment are the same or similar. Figure 2c Only the internal structure of the test environment is shown, and the internal structure of the online environment is not shown. After the second application has undergone various tests in the test environment and has perfected its functions, the application deployment package after the test environment has been perfected can be deployed to the online environment, and a new version of the application can be deployed in the online environment, and the application can be upgraded or rolled back.
[0070] In an optional embodiment, the server determines the target working node from at least one working node in the container management system based on the application deployment information for the second application, and sends the application deployment package of the second application to the target working node. For example, the server maintains the corresponding relationship between each application deployment package and its identification information, and can obtain the target application deployment package from at least one application deployment package maintained by the server based on the deployment package identification information; and select the target working node from at least one working node based on the node type information.
[0071] Optionally, at least one working node includes: a test type and an online type, wherein the test type working node is mainly used by the application developer to perform various tests on the second application, for example, to perform functional verification, performance testing, and security testing on the second application, so as to discover and repair potential problems and defects. The online type working node is the environment in which the second application ultimately provides services to users, also known as the production environment. In this environment, the second application needs to run stably and provide high-quality services to meet the needs of the application user. The online type working node usually has higher requirements for the performance, stability, and security of the second application. Among them, by distinguishing between online type working nodes and offline type working nodes through different working nodes, the test environment can be kept isolated from the online environment to a certain extent to avoid interference or damage to the online environment caused by the test activities. Based on this, according to the node type of at least one working node, at least one candidate working node matching the node type information in the application deployment information is selected; according to at least one of the operators, load rate, and network quality contained in the node deployment requirement information, a target working node that meets the set conditions is selected.
[0072] The node deployment requirement information includes at least one of an operator, a load rate, and a network quality, and set conditions for the operator, the load rate, and the network quality. The set condition refers to at least one of a set operator, a load rate of a working node being less than a set load rate, and a network quality of a working node being greater than or equal to a set network quality.
[0073] For example, candidate working node M1 corresponds to operator X1, candidate working node M2 corresponds to operator X2, candidate working node M3 corresponds to operator X3, and the setting condition includes setting the operator to operator X2, then candidate working node M1 can be used as the target working node.
[0074] For another example, the load rate of candidate working node M1 is 80%, the load rate of candidate working node M2 is 50%, and the load rate of candidate working node M3 is 70%. If the set load rate is 75%, then according to the set condition that the load rate of the working node is less than the set load rate, candidate working node M2 and candidate working node M3 can be used as target working nodes.
[0075] For another example, the network quality of candidate working node M1 is excellent, the network quality of candidate working node M2 is good, and the network quality of candidate working node M3 is poor. If the set network quality is good, then according to the set condition that the network quality of the working node is greater than or equal to the set load rate, candidate working node M1 and candidate working node M2 can be used as target working nodes.
[0076] For another example, the set condition is that the load rate of the set operator and the working node is less than the set load rate, and the network quality of the working node is greater than or equal to the set network quality. In combination with the above example, the candidate working node that meets the above conditions is M2, and the candidate working node M2 can be used as the target working node.
[0077] In an optional embodiment, the target work node can also output the difference information between the second application and the first application to prompt the application user and reduce the problems caused by environmental compatibility. For example, the difference information is displayed on the screen of the target work node, or the difference information is output by voice. Among them, the difference information between the application deployment package of the second application and the application deployment package corresponding to the first application includes: application version difference information, metadata difference information and environment dependency difference information. Furthermore, the difference information also includes the difference information of the application developer.
[0078] The implementation method of replacing the first application running in the container with the second application based on the difference information by the target working node is not limited. According to the application version difference information, it can be determined whether the first application running in the container and the second application to be deployed are the same application; if the first application and the second application are the same, there is no need to update the operating environment of the second application, the first application can be uninstalled, and the second application can be deployed in the container; if the first application and the second application are different applications, for example, the first application and the second application are different versions of the same application, or the first application and the second application belong to different applications, wherein the optimal operating environments that different applications rely on are not the same, for example, the database version that the first application relies on is 5.0, and the database version that the second application relies on is 5.2. If the second application uses the 5.0 version of the database, it may cause compatibility problems in the second application and affect the stability of the second application. Based on this, the operating environment can be updated for the second application in the container based on the environment dependency difference information; based on the metadata difference information, the metadata of the first application is updated to replace the first application running in the container with the second application. Replacement can be an upgrade, rollback, or deployment of a new application.
[0079] For example, the environment dependency difference information includes version difference information, database difference information, or framework difference information of the low-code platform. By comparing the structured description information, the version difference information, database difference information, or framework difference information of the above low-code platform can be determined. Among them, the version difference information is a kind of information indicating whether the version of the low-code platform that the second application depends on is newer or older than the version of the low-code platform that the first application depends on. Generally speaking, with the update of the version, the low-code platform may add new functions or improve existing functions, or with the update of the version, some functions or features may be adjusted or removed. For example, the version number of the low-code platform that the first application depends on is the first version number, and the version number of the low-code platform that the second application depends on is the second version number. In the case where the first version is earlier than the second version, the low-code platform is upgraded from the first version to the second version, and in the case where the first version is later than the second version, the low-code platform is rolled back from the first version to the second version. Similarly, the database difference information is a kind of information indicating the upgrade or rollback of the database version that the second application depends on, and the framework difference information is a kind of information indicating the upgrade or rollback of the framework version that the second application depends on.
[0080] The metadata difference information is a kind of difference information indicating the difference between the second application and the first application. If the metadata is implemented as a json file, the metadata difference information can be the difference information of each object in the json file, and the difference information can be determined from the field dimension of each object. The method of updating the metadata of the first application based on the metadata difference information may include but is not limited to: adding fields, deleting fields, and modifying fields. For example, the metadata difference information includes an index and detailed information. The index includes: 1) plug-in information: "0 new items, 1 deleted items, 0 modified items"; 2) menu information: "1 new items, 0 deleted items, 11 modified items"; 3) permission information: "17 new items, 0 deleted items, 0 modified items". The detailed information refers to how to operate the metadata specifically, for example, which fields are deleted, modified or added. Therefore, the updated metadata can be parsed to obtain the executable code of the second application, and the executable code can be run to replace the first application running in the container of the target working node with the second application.
[0081] In this embodiment, the application deployment package of the second application can be deployed in a new container of the target working node. The server can directly generate a container image file based on the basic image file according to the application deployment package of the second application, and provide the container image file to the target working node. The target working node starts the container creation module in the container image file, creates a container on the target working node, runs the low-code platform deployment module in the container image file, deploys the operating environment of the low-code platform in the container, runs the application deployment module in the container image file, parses the application deployment package, deploys the operating environment of the second application based on the application deployment package, installs the corresponding version of the database or framework, etc., or updates the operating environment of the low-code platform, and parses the metadata of the second application in the operating environment of the low-code platform to run the second application in the operating environment.
[0082] like Figure 2e As shown, a flowchart is provided for processing an application deployment package after a target working node receives the application deployment package. The target working node receives the application deployment package of the second application, parses the application deployment package, obtains a structured description file, and reads the target version information of the second application from the structured description file. The control node in the container management system instructs the application deployment package of the second application to be deployed in the target container of the target working node. If the application is not deployed in the target container, a new application, i.e., the second application, is deployed in the target application, and the metadata and developer information in the target application deployment package are obtained, and the metadata is run to run the second application. If the application version currently running in the target container is higher than the target version information, the currently running first application is upgraded, and the metadata of the second application and the metadata of the currently running first application are imported into a temporary library, and the difference information of the two metadata is compared; the difference information of the data models of the first application and the second application is compared; the metadata difference information and the data model difference information are output; the developer information is compared and updated; and the second application is started based on the metadata of the second application. If the application version currently running in the target container is lower than the target version information, the currently running first application will be rolled back. Similarly, the metadata difference information, data model difference information, and developer difference information between the first application and the second application can be obtained, and the second application can be started based on the metadata of the second application. When rolling back the version, the difference information of the application before and after the version rollback can also be output. Figure 2e The steps for displaying the difference information are not illustrated.
[0083] In this embodiment, the application processing system is divided into five modules, namely: data import and export module, metadata processing module, version management module, deployment management module and user and permission module. Among them, the data import and export module belongs to the module involved in the development environment corresponding to the low-code platform on the terminal device. The data import and export module is mainly responsible for exporting the metadata of the application developed by the low-code platform into a file and packaging the file. This module supports the import of different data sources, for example, data source formats supported by databases such as MySQL, MongoDB, and Elasticsearch (ES). Among them, MySQL is a relational database management system. MongoDB is a database based on distributed file storage. ES is a distributed search and analysis engine. Among them, the data import and export module also supports exporting data sources (such as metadata) into different file formats, which is compatible with different data sources. For example, text files, database executable scripts, csv format files, and json format files. Among them, the cvs format file is a comma separated values (Comma Separated Values) file, and cvs is a simple table data storage format.
[0084] Among them, the metadata processing module belongs to the module involved in the operating environment corresponding to the low-code platform on the target working node. This module can synchronize the metadata modified by the application developer to the application deployment environment, and can also compare the metadata in the application deployment package with the metadata difference of the currently running first application, and synchronize the metadata of the deployment environment. The synchronization method includes adding fields, modifying fields, and deleting fields. Furthermore, it is also possible to compare the differences between the environmental dependency information of the second application in the application deployment package and the current operating environment, and update the environmental information.
[0085] Among them, the version management module belongs to the module involved in the development environment corresponding to the low-code platform on the terminal device. Every time the second application is packaged, the application deployment package and its version number are automatically generated, and the packaged application deployment package is uploaded to the server (such as a file server). Subsequently, new versions can be deployed, upgraded versions can be upgraded, and old versions can be rolled back according to different versions.
[0086] Among them, the deployment management module belongs to the module involved in the operating environment corresponding to the low-code platform on the target working node. After each deployment of the application deployment package, the version, date, operator, version difference and other information of this deployment are recorded for subsequent query and troubleshooting.
[0087] The user and permission module can be a module corresponding to the development environment of the low-code platform on the terminal device, or a module corresponding to the operating environment of the low-code platform on the target work node. It is mainly used to package and store application developer information, organization information, and permission information, and restore it in the new operating environment when the second application is deployed. The organization refers to the department or company to which the application developer belongs, and the permission information can be the application developer's modification permission, development permission, etc. for the second application.
[0088] In addition to providing a system embodiment, the embodiment of the present application also provides an application processing method based on a low-code platform. The process of the application processing method based on a low-code platform provided by the embodiment of the present application is described below.
[0089] Figure 3 A flow chart of an application processing method based on a low-code platform provided for an exemplary embodiment of the present application, the method is applicable to a terminal device in an application processing system based on a low-code platform, and a development environment of the low-code platform is run on the terminal device; Figure 3 As shown, the method includes:
[0090] 301. In response to a packaging operation for a second application, obtain metadata of the second application generated by a development environment of a low-code platform;
[0091] 302. Generate an application deployment package corresponding to the second application based on the metadata of the second application, and upload it to a server in the application processing system;
[0092] 303. In response to the deployment operation for the second application, application deployment information for the second application is provided to the server, so that the server provides the application deployment package of the second application to the target working node in the container management system based on the application deployment information, so that the target working node replaces the first application running in its container with the second application based on the difference information between the application deployment package of the second application and the application deployment package of the first application.
[0093] In an optional embodiment, in response to a packaging operation for the second application, metadata of the second application generated by the development environment of the low-code platform is obtained, including: in response to the packaging operation for the second application, according to the application identification information of the second application, the original data of the second application is obtained, the original data including at least metadata and environment dependency information; the environment dependency information includes at least: description information, framework description information and database description information of the low-code platform on which the second application depends on to run; based on the metadata of the second application, an application deployment package corresponding to the second application is generated, including: using a structured grammatical format to describe the original data to obtain structured description information corresponding to the second application; based on the metadata, the environment dependency information and the structured description information, an application deployment package for the second application is generated.
[0094] Optionally, in response to a packaging operation for the second application, original data of the second application is obtained based on application identification information of the second application, including: in response to a selection operation on the second application on the application packaging page, application version information of the second application is generated, and a packaging control is displayed; in response to a trigger operation on the packaging control, metadata and environment dependency information of the second application are obtained based on the application identification information of the second application; and the metadata, environment dependency information and application version information are used as the original data of the second application.
[0095] Further optionally, the application packaging page also includes: a historical version control; when the application deployment package corresponding to the second application has been generated, in response to the deployment operation for the second application, the application deployment information for the application deployment package is provided to the server, including: in response to the trigger operation for the historical version control, displaying at least one deployment control corresponding to at least one application version information, the at least one application version information at least including the target application version information of the application deployment package corresponding to the second application; in response to the trigger operation for the deployment control corresponding to the target application version information, generating the target identification information of the application deployment package of the second application based on the target application version information, and obtaining the node deployment requirement information of the working node corresponding to the application deployment package; providing the target identification information and the node deployment requirement information as the application deployment information of the second application to the server.
[0096] Figure 4 A flowchart of another application processing method based on a low-code platform provided for an exemplary embodiment of the present application, the method is applicable to a server in an application processing system based on a low-code platform; Figure 4 The method shown includes:
[0097] 401. Receive application deployment information for a second application sent by a terminal device in an application processing system, where the application deployment package of the second application is packaged and generated based on metadata of the second application generated by a development environment of a low-code platform and uploaded to a server, and the application deployment information is sent by the terminal device in response to a deployment operation for the second application;
[0098] 402. Determine a target working node from at least one working node in the container management system according to the application deployment information, wherein a first application is running in a container on the target working node;
[0099] 403. Send the application deployment package of the second application to the target working node, so that the target working node replaces the first application running in the container with the second application based on the difference information between the application deployment package of the second application and the application deployment package of the first application.
[0100] In an optional embodiment, a target working node is determined from at least one working node in a container management system based on application deployment information, including: selecting a target working node from at least one working node based on node deployment requirement information in the application deployment information; the method also includes: obtaining an application deployment package of a second application from at least one application deployment package maintained by a server based on target identification information in the application deployment information.
[0101] Optionally, based on the node deployment requirement information in the application deployment information, a target working node is selected from at least one working node, including: based on the node type of at least one working node, at least one candidate working node that matches the node type information in the node deployment information is selected, the node type information includes a test type and an online type; based on at least one of the operator, load rate, and network quality contained in the node deployment requirement information, a target working node that meets the set conditions is selected from at least one candidate working node.
[0102] Figure 5 A flow chart of another application processing method based on a low-code platform provided for an exemplary embodiment of the present application, the method is applicable to a target working node in a container management system, a container is deployed on the target working node, the container provides an operating environment of a low-code platform for running an application developed based on the low-code platform, and a first application is running in the operating environment; Figure 5 As shown, the method includes:
[0103] 501. Receive an application deployment package of a second application provided by a server in an application processing system to which the container management system belongs; the application deployment package of the second application is packaged and generated based on metadata of the second application generated by a development environment of a low-code platform and uploaded to the server;
[0104] 502. Compare the application deployment package of the second application with the application deployment package of the first application to obtain difference information between the application deployment package of the second application and the application deployment package of the first application;
[0105] 503. Based on the difference information, replace the first application running in the container with the second application.
[0106] Optionally, based on the difference information, replacing the first application running in the container with the second application includes: if it is determined that the first application running in the container is different from the second application based on the application version difference information contained in the difference information, updating the operating environment for the second application in the container based on the environment dependency difference information contained in the difference information; and updating the metadata of the first application based on the metadata difference information contained in the difference information to replace the first application running in the container with the second application.
[0107] Regarding the embodiments of the present application Figures 3 to 5 The detailed implementation and beneficial effects of each step in the method have been described in detail in the aforementioned embodiments and will not be elaborated here.
[0108] It should be noted that the execution subject of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 301 to 303 can be device A; for another example, the execution subject of steps 301 and 302 can be device A, and the execution subject of step 303 can be device B; and so on.
[0109] In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or executed in parallel, and the sequence numbers of the operations, such as 301, 302, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., do not represent the order of precedence, and do not limit the "first" and "second" to be different types.
[0110] An exemplary embodiment of the present application provides an application processing device based on a low-code platform, the device corresponds to a terminal device in an application processing system based on a low-code platform, and a development environment of the low-code platform runs on the terminal device; the device includes: an acquisition module, a generation module, an upload module, and a provision module;
[0111] An acquisition module, configured to acquire metadata of the second application generated by the development environment of the low-code platform in response to a packaging operation for the second application;
[0112] A generation module, which generates an application deployment package corresponding to the second application based on the metadata of the second application;
[0113] An upload module, used to upload the application deployment package of the second application to a server in the application processing system;
[0114] A module is provided for providing application deployment information for the second application to a server in response to a deployment operation for the second application, so that the server can provide an application deployment package of the second application to a target working node in the container management system based on the application deployment information, so that the target working node replaces the first application running in its container with the second application based on difference information between the application deployment package of the second application and the application deployment package of the first application.
[0115] Optionally, the acquisition module is specifically used to: in response to a packaging operation for the second application, obtain the original data of the second application according to the application identification information of the second application, the original data including at least metadata and environment dependency information; the environment dependency information includes at least: description information of the low-code platform on which the second application depends, framework description information and database description information; the generation module is specifically used to: use a structured grammatical format to describe the original data to obtain structured description information corresponding to the second application; based on the metadata, environment dependency information and structured description information, generate an application deployment package for the second application.
[0116] Further optionally, the generation module is specifically used to: in response to a selection operation on the second application on the application packaging page, generate application version information of the second application and display a packaging control; in response to a trigger operation on the packaging control, based on the application identification information of the second application, obtain metadata and environment dependency information of the second application; and use the metadata, environment dependency information and application version information as original data of the second application.
[0117] Optionally, the application packaging page also includes: a historical version control; when the application deployment package corresponding to the second application has been generated, a module is provided specifically for: in response to a trigger operation on the historical version control, displaying at least one deployment control corresponding to at least one application version information, the at least one application version information at least including target application version information of the application deployment package corresponding to the second application; in response to a trigger operation on the deployment control corresponding to the target application version information, generating target identification information of the application deployment package of the second application based on the target application version information, and obtaining node deployment requirement information of the working node corresponding to the application deployment package; providing the target identification information and the node deployment requirement information as application deployment information of the second application to the server.
[0118] An exemplary embodiment of the present application provides an application processing device based on a low-code platform, the device corresponding to a server in an application processing system based on a low-code platform, the device comprising: a first receiving module, a determining module and a sending module;
[0119] A first receiving module is used to receive application deployment information for a second application sent by a terminal device in an application processing system, where the application deployment package of the second application is packaged and generated based on the metadata of the second application generated by a development environment of a low-code platform and uploaded to a server, and the application deployment information is sent by the terminal device in response to a deployment operation for the second application;
[0120] A determination module, configured to determine a target working node from at least one working node in the container management system according to the application deployment information, wherein a first application is running in a container on the target working node;
[0121] The sending module is used to send the application deployment package of the second application to the target working node, so that the target working node replaces the first application running in the container with the second application based on the difference information between the application deployment package of the second application and the application deployment package of the first application.
[0122] In an optional embodiment, the determination module is specifically used to: select a target working node from at least one working node based on the node deployment requirement information in the application deployment information; the device also includes: an acquisition module; the acquisition module is used to obtain the application deployment package of the second application from at least one application deployment package maintained by the server based on the target identification information in the application deployment information.
[0123] Optionally, the determination module is specifically used to: select at least one candidate working node that matches the node type information in the node deployment requirement information based on the node type of at least one working node, the node type information including a test type and an online type; select a target working node that meets the set conditions from at least one candidate working node based on at least one of the operator, load rate and network quality included in the node deployment requirement information.
[0124] An exemplary embodiment of the present application provides an application processing device based on a low-code platform, the device corresponds to a target working node in a container management system, a container is deployed on the target working node, the container provides an operating environment of the low-code platform for running an application developed based on the low-code platform, and a first application runs in the operating environment; the device includes: a second receiving module, a comparison module and a replacement module;
[0125] A second receiving module is used to receive an application deployment package of a second application provided by a server in an application processing system to which the container management system belongs; the application deployment package of the second application is packaged and generated based on the metadata of the second application generated by the development environment of the low-code platform and uploaded to the server;
[0126] A comparison module, used to compare the application deployment package of the second application with the application deployment package of the first application to obtain difference information between the application deployment package of the second application and the application deployment package of the first application;
[0127] The replacement module is used to replace the first application running in the container with the second application based on the difference information.
[0128] In an optional embodiment, the replacement module is specifically used to: if it is determined that the first application running in the container is different from the second application based on the application version difference information contained in the difference information, then based on the environment dependency difference information contained in the difference information, update the operating environment for the second application in the container; based on the metadata difference information contained in the difference information, update the metadata of the first application to replace the first application running in the container with the second application.
[0129] The detailed implementation methods and beneficial effects of each step in the above-mentioned device provided in the embodiment of the present application have been described in detail in the aforementioned embodiments and will not be elaborated here.
[0130] Figure 6 A schematic diagram of the structure of an electronic device provided for an exemplary embodiment of the present application, wherein the electronic device corresponds to a terminal device in an application processing system based on a low-code platform, and a development environment of the low-code platform is run on the terminal device; Figure 6 As shown, the device includes: a memory 64 and a processor 65.
[0131] The memory 64 is used to store computer programs and can be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method used to operate on the electronic device.
[0132] The processor 65 is coupled to the memory 64 and is used to execute the computer program in the memory 64, so as to: obtain the metadata of the second application generated by the development environment of the low-code platform in response to the packaging operation for the second application; generate an application deployment package corresponding to the second application based on the metadata of the second application, and upload it to the server in the application processing system; and provide application deployment information for the second application to the server in response to the deployment operation for the second application, so that the server can provide the application deployment package of the second application to the target working node in the container management system based on the application deployment information, so that the target working node replaces the first application running in its container with the second application based on the difference information between the application deployment package of the second application and the application deployment package of the first application.
[0133] In an optional embodiment, when the processor 65 obtains the metadata of the second application generated by the development environment of the low-code platform in response to a packaging operation for the second application, the processor 65 is specifically used to: in response to the packaging operation for the second application, obtain the original data of the second application according to the application identification information of the second application, the original data includes at least metadata and environment dependency information; the environment dependency information includes at least: description information of the low-code platform on which the second application depends on to run, framework description information and database description information; when the processor 65 generates an application deployment package corresponding to the second application based on the metadata of the second application, the processor 65 is specifically used to: describe the original data in a structured grammatical format to obtain structured description information corresponding to the second application; generate an application deployment package for the second application based on the metadata, the environment dependency information and the structured description information.
[0134] Optionally, when the processor 65 obtains the original data of the second application according to the application identification information of the second application in response to the packaging operation for the second application, it is specifically used to: generate application version information of the second application in response to the selection operation of the second application on the application packaging page, and display the packaging control; in response to the trigger operation for the packaging control, obtain metadata and environment dependency information of the second application based on the application identification information of the second application; and use the metadata, environment dependency information and application version information as the original data of the second application.
[0135] Further optionally, the application packaging page also includes: a historical version control; when the application deployment package corresponding to the second application has been generated, the processor 65, in response to the deployment operation for the second application, provides the application deployment information for the application deployment package to the server, specifically for: in response to the trigger operation for the historical version control, display at least one deployment control corresponding to at least one application version information, the at least one application version information at least including the target application version information of the application deployment package corresponding to the second application; in response to the trigger operation for the deployment control corresponding to the target application version information, generate the target identification information of the application deployment package of the second application based on the target application version information, and obtain the node deployment requirement information of the working node corresponding to the application deployment package; provide the target identification information and the node deployment requirement information as the application deployment information of the second application to the server. In response to a trigger operation on a historical version control, display a deployment control corresponding to at least one historical version, at least one historical version includes application version information corresponding to the second application; in response to a trigger operation on a deployment control corresponding to a target application version, generate target identification information of an application deployment package for the second application based on the target application version information, and obtain node type information provided by the application developer; provide the target identification information and node type information as application deployment information for the second application to the server. Figure 6 The detailed implementation and beneficial effects of each step in the illustrated device have been described in detail in the aforementioned embodiments and will not be elaborated on here.
[0136] Further, if Figure 6 As shown, the electronic device also includes: a communication component 66, a display 67, a power component 68, an audio component 69 and other components. Figure 6 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 6 In addition, Figure 6 The components in the dashed box are optional components, not mandatory components, and the specific components depend on the product form of the electronic device. The electronic device of this embodiment can be implemented as a terminal device such as a desktop computer, a laptop computer, a smart phone, or an IOT device, or a server device such as a conventional server, a cloud server, or a server array. If the electronic device of this embodiment is implemented as a terminal device such as a desktop computer, a laptop computer, a smart phone, etc., it can include Figure 6 If the electronic device of this embodiment is implemented as a server device such as a conventional server, a cloud server or a server array, it may not include Figure 6 Components within the dashed box.
[0137] The embodiment of the present application also provides an electronic device, which corresponds to a server in an application processing system based on a low-code platform; the implementation structure of the electronic device is similar to Figure 6 The implementation structure of the electronic device shown is the same or similar, and can refer to Figure 6 The electronic device provided in this embodiment is implemented as follows: Figure 6 The difference between the electronic devices in the illustrated embodiments mainly lies in: the functions implemented by the processor executing the computer program stored in the memory are different. For the electronic device provided in this embodiment, its processor executes the computer program stored in the memory, which can be used to: receive application deployment information for the second application sent by the terminal device in the application processing system, the application deployment package of the second application is packaged and generated based on the metadata of the second application generated by the development environment of the low-code platform and uploaded to the server, and the application deployment information is sent by the terminal device in response to the deployment operation for the second application; according to the application deployment information, determine the target working node from at least one working node in the container management system, and the first application is running in the container on the target working node; send the application deployment package of the second application to the target working node, so that the target working node can replace the first application running in the container with the second application based on the difference information between the application deployment package of the second application and the application deployment package of the first application.
[0138] In an optional embodiment, when the processor determines the target working node from at least one working node in the container management system based on the application deployment information, it is specifically used to: select the target working node from at least one working node based on the node deployment requirement information in the application deployment information; the processor is also used to: obtain the application deployment package of the second application from at least one application deployment package maintained by the server based on the target identification information in the application deployment information.
[0139] Optionally, when the processor selects a target working node from at least one working node based on the node deployment requirement information in the application deployment information, it is specifically used to: select at least one candidate working node that matches the node type information in the node deployment requirement information based on the node type of at least one working node, the node type information including a test type and an online type; select a target working node that meets the set conditions from at least one candidate working node based on at least one of the operator, load rate and network quality contained in the node deployment requirement information.
[0140] The embodiment of the present application also provides an electronic device, which corresponds to a target working node in a container management system, on which a container is deployed, and the container provides an operating environment of a low-code platform for running an application developed based on the low-code platform, and a first application is running in the operating environment; the implementation structure of the electronic device is similar to Figure 6The implementation structure of the electronic device shown is the same or similar, and can refer to Figure 6 The electronic device provided in this embodiment is implemented as follows: Figure 6 The difference between the electronic devices in the illustrated embodiments mainly lies in that the functions implemented by the processor executing the computer program stored in the memory are different. For the electronic device provided in this embodiment, its processor executes the computer program stored in the memory, which can be used to: receive the application deployment package of the second application provided by the server in the application processing system to which the container management system belongs; the application deployment package of the second application is packaged and generated based on the metadata of the second application generated by the development environment of the low-code platform and uploaded to the server; compare the application deployment package of the second application with the application deployment package of the first application to obtain the difference information between the application deployment package of the second application and the application deployment package of the first application; based on the difference information, replace the first application running in the container with the second application.
[0141] Optionally, when the processor replaces the first application running in the container with the second application based on the difference information, the processor is specifically used to: if it is determined that the first application running in the container is different from the second application based on the application version difference information included in the difference information, then based on the environment dependency difference information included in the difference information, update the operating environment for the second application in the container; based on the metadata difference information included in the difference information, update the metadata of the first application to replace the first application running in the container with the second application.
[0142] The detailed implementation and beneficial effects of the electronic device provided in the embodiments of the present application have been described in detail in the aforementioned embodiments and will not be elaborated here.
[0143] Accordingly, the present application also provides a computer-readable storage medium storing a computer program, which can achieve the above-mentioned Figures 3 to 5 The steps in the method embodiment shown may be executed by an electronic device.
[0144] Accordingly, the embodiment of the present application further provides a computer program, including a computer program / instruction, which, when executed by a processor, causes the processor to implement the above Figures 3 to 5 The steps in the method embodiment shown may be executed by an electronic device.
[0145] The above-mentioned memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.
[0146] The above-mentioned communication component is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.
[0147] The above-mentioned display includes a screen, and the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
[0148] The power supply assembly provides power to various components of the device where the power supply assembly is located. The power supply assembly may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply assembly is located.
[0149] The above-mentioned audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (Microphone, MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in a memory or sent via a communication component. In some embodiments, the audio component also includes a speaker for outputting an audio signal.
[0150] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-readable storage media (including but not limited to disk storage, compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage, etc.) containing computer-usable program code.
[0151] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0152] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0153] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0154] In a typical configuration, a computing device includes one or more processors (Central Processing Unit, CPU), input / output interface, network interface and memory.
[0155] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
[0156] Computer readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. 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 random access 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 technology, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape 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 temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0157] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0158] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.
Claims
1. An application processing system based on a low-code platform, It is characterized in that include: A terminal device, a server, and at least one working node in a container management system; the development environment of the low-code platform is run on the terminal device, and a container is deployed on each working node, and the container provides an operating environment of the low-code platform for running applications developed based on the low-code platform; The terminal device is used to obtain metadata of the second application generated by the development environment of the low-code platform in response to a packaging operation for the second application; generating an application deployment package corresponding to the second application based on the metadata, and uploading the application deployment package to the server; as well as In response to the deployment operation for the second application, providing application deployment information for the second application to the server; The server is configured to determine a target working node from the at least one working node according to the application deployment information, and provide an application deployment package of the second application to the target working node, wherein the first application is running in a container on the target working node; The target working node is used to replace the first application running in the container with the second application based on difference information between the application deployment package of the second application and the application deployment package of the first application.
2. An application processing method based on a low-code platform, It is characterized in that Applicable to a terminal device in an application processing system based on a low-code platform, on which a development environment of the low-code platform is run, the method comprising: In response to the packaging operation for the second application, obtaining metadata of the second application generated by the development environment of the low-code platform; Based on the metadata of the second application, generate an application deployment package corresponding to the second application, and upload it to a server in the application processing system; and In response to a deployment operation for the second application, application deployment information for the second application is provided to the server, so that the server provides an application deployment package of the second application to a target working node in a container management system based on the application deployment information, so that the target working node replaces the first application running in its container with the second application based on difference information between the application deployment package of the second application and the application deployment package of the first application.
3. The method according to claim 2, It is characterized in that In response to the packaging operation for the second application, obtaining metadata of the second application generated by the development environment of the low-code platform includes: In response to the packaging operation for the second application, original data of the second application is obtained according to the application identification information of the second application, the original data at least including the metadata and environment dependency information; the environment dependency information at least includes: description information of the low-code platform on which the second application depends, framework description information, and database description information; Generating an application deployment package corresponding to the second application based on the metadata of the second application includes: Describing the original data in a structured grammatical format to obtain structured description information corresponding to the second application; An application deployment package of the second application is generated based on the metadata, the environment dependency information and the structured description information.
4. The method according to claim 3, It is characterized in that In response to the packaging operation for the second application, obtaining original data of the second application according to the application identification information of the second application includes: In response to a selection operation of the second application on the application packaging page, generating application version information of the second application and displaying a packaging control; In response to a trigger operation on the packaged control, based on the application identification information of the second application, obtaining metadata and environment dependency information of the second application; The metadata, environment dependency information and application version information are used as original data of the second application.
5. The method according to claim 4, It is characterized in that The application packaging page also includes: a historical version control; when an application deployment package corresponding to the second application has been generated, in response to a deployment operation for the second application, providing application deployment information for the application deployment package to the server, including: In response to a trigger operation on the historical version control, display at least one deployment control corresponding to at least one application version information, wherein the at least one application version information includes at least target application version information of an application deployment package corresponding to the second application; In response to a trigger operation on a deployment control corresponding to the target application version information, generating target identification information of an application deployment package of the second application based on the target application version information, and acquiring node deployment requirement information of a working node corresponding to the application deployment package; The target identification information and the node deployment requirement information are provided to the server as application deployment information of the second application.
6. An application processing method based on a low-code platform, It is characterized in that Applicable to a server in an application processing system based on the low-code platform, the method includes: Receive application deployment information for a second application sent by a terminal device in the application processing system, where an application deployment package for the second application is packaged and generated based on metadata of the second application generated by a development environment of a low-code platform and uploaded to the server, and the application deployment information is sent by the terminal device in response to a deployment operation for the second application; Determine, according to the application deployment information, a target working node from at least one working node in the container management system, wherein a first application is running in a container on the target working node; The application deployment package of the second application is sent to the target working node, so that the target working node replaces the first application running in the container with the second application based on difference information between the application deployment package of the second application and the application deployment package of the first application.
7. The method according to claim 6, It is characterized in that Determining a target working node from at least one working node in a container management system according to the application deployment information includes: According to the node deployment requirement information in the application deployment information, selecting a target working node from the at least one working node; the method further comprises: According to the target identification information in the application deployment information, an application deployment package of the second application corresponding to the target identification information is obtained from at least one application deployment package maintained by the server.
8. The method according to claim 7, It is characterized in that Selecting a target working node from the at least one working node according to the node deployment requirement information in the application deployment information includes: According to the node type of the at least one working node, selecting at least one candidate working node that matches the node type information in the node deployment requirement information, wherein the node type information includes a test type and an online type; According to at least one of the operator, load rate and network quality included in the node deployment requirement information, a target working node that meets the set conditions is selected from the at least one candidate working node.
9. An application processing method based on a low-code platform, It is characterized in that Applicable to a target working node in a container management system, a container is deployed on the target working node, the container provides an operating environment of a low-code platform for running an application developed based on the low-code platform, and a first application is running in the operating environment; the method includes: Receive an application deployment package of a second application provided by a server in an application processing system to which the container management system belongs; the application deployment package of the second application is packaged and generated based on metadata of the second application generated by a development environment of a low-code platform and uploaded to the server; Compare the application deployment package of the second application with the application deployment package of the first application to obtain difference information between the application deployment package of the second application and the application deployment package of the first application; Based on the difference information, the first application running in the container is replaced with the second application.
10. The method according to claim 9, It is characterized in that Replacing the first application running in the container with the second application based on the difference information includes: If it is determined that the first application running in the container is different from the second application according to the application version difference information included in the difference information, updating the running environment for the second application in the container based on the environment dependency difference information included in the difference information; Based on the metadata difference information included in the difference information, the metadata of the first application is updated to replace the first application running in the container with the second application.
11. An electronic device, It is characterized in that include: Memory and processor; The memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to implement the steps in the method of any one of claims 2-5, claims 6-8 and claims 9-10.
12. A computer-readable storage medium storing a computer program, It is characterized in that When the computer program is executed by a processor, the processor is caused to implement the steps in the method of any one of claims 2 to 5, claims 6 to 8, and claims 9 to 10.
13. A computer program comprising computer program / instructions, It is characterized in that When the computer program / instructions are executed by a processor, the processor is caused to implement the steps in the method of any one of claims 2-5, claims 6-8 and claims 9-10.
Citation Information
Patent Citations
Application deployment method and related device
CN115469884A
Container scheduling method, device and system
CN116225612A
Application deployment method and device and computer readable storage medium
CN117762427A
Code package deployment method and device, equipment, medium and product
CN117762769A
Storage processing method and related device
CN118051166A
Cited By
Application isolation operation method, electronic equipment and readable storage medium
CN119987940A
Application calling method and device, equipment, medium and product
CN120296723A
