Low-code development platform implementation method supporting single host to adapt to multiple operation environments

Abstract

The invention discloses a low-code development platform implementation method supporting a single host to adapt to multiple operation environments, and relates to the technical field of software development. The method comprises the steps that 1, according to a functional module of the low-code development platform, a service boundary is defined, a micro-service architecture is established, the functional module of the low-code development platform is divided into independent design-state micro-services and operation-state micro-services, and operation of the operation-state micro-services depends on data of the design-state micro-services; the method comprises the following steps: step 1, managing different deployment environments by using configuration files and environment variables through an operation center, step 2, deploying the environments, and step 4, deploying virtual isolation environments aiming at a starting virtual field scene, so that the same single host is distributed to different host sets and corresponds to a plurality of groups of virtual isolation environments. Therefore, the application programs of multiple versions can be started on a single host by using different virtual isolation environment configurations during deployment.

Description

Technical Field

[0001] The present invention discloses a method for realizing a low-code development platform that supports a single host to adapt to multiple operating environments, and relates to the technical field of software development. Background Art

[0002] With the development of low-code platforms, developers and non-developers can quickly create and iterate applications through visual development environments and pre-built components, which lowers the development threshold. Although low-code platforms provide the advantage of rapid development, in actual usage scenarios, customers often have independent deployment requirements and hope to deploy and use applications in different locations after the application is designed in the general control center. In terms of deployment, due to limited resources or the desire to make full use of the original machine resources, it is necessary to deploy low-code services on the physical host, and it is expected that multiple sets of low-code application services will be deployed on the same host. This scenario has a lot of actual needs in the current market, especially in government systems, but the design and deployment of such a low-code development system has not yet been realized. Summary of the invention

[0003] In view of the problems of the prior art, the present invention provides a method for implementing a low-code development platform that supports a single host to adapt to multiple operating environments. The specific solution proposed by the present invention is:

[0004] The present invention provides a method for implementing a low-code development platform that supports a single host adapting to multiple operating environments, including: step 1: defining service boundaries according to the functional modules of the low-code development platform, establishing a microservice architecture, and splitting the functional modules of the low-code development platform into independent design state microservices and running state microservices, wherein the operation of the running state microservices depends on the data of the design state microservices,

[0005] Step 2: Build an operation center for running microservices, and use the operation center to manage different deployment environments using configuration files and environment variables. For containerized scenarios, the configuration files are the Nacos YAML file and the value.yml file used for helm orchestration. For physical / virtual machine scenarios, the configuration files are the bootstrap.yml configuration files required for each module to start. The configuration files for the middleware include the ngnix.conf file of Nginx.

[0006] Step 3: Deployment environment: For containerized environment, use the application management package helm to start the service, publish the designed application image and save it, write the template file through helm chart, and pass in the name of the running service image to be deployed, and start the service through helminstall.

[0007] For virtual machine startup scenarios, use Ansible automated operation and maintenance to start independent applications for independent deployment.

[0008] Step 4: Deploy a virtual isolation environment for the virtual machine startup scenario: Configure the host group through the operation center, and configure a corresponding Nacos namespace for each host group to implement a virtual isolation environment. The same single host is assigned to different host groups, corresponding to multiple sets of virtual isolation environments, so that different virtual isolation environment configurations can be used on a single host to start multiple versions of applications during deployment.

[0009] Furthermore, when establishing a microservice architecture in step 1 of the implementation method of a low-code development platform that supports a single host adapting to multiple operating environments, the front end is built using the VUE3 language, the back end is built using the Spring framework service, the load balancer Nginx is used to distribute requests, and Nacos provides service configuration registration.

[0010] Furthermore, in step 2 of the implementation method of a low-code development platform that supports a single host adapting to multiple operating environments, an operation center is used to manage different deployment environments, wherein the deployment environment involves host management, data source management, Redis management, Minio management, and Nacos management. Each environment selects a specific host, data source, Redis configuration, and all other required static information according to actual needs, and persists the environment information after the selection is completed, and generates different configuration information according to the selected deployment scenario type, wherein the host information includes the host IP, Port, and ssh key; the data source information includes the data source Host address, port, user name, and password.

[0011] Furthermore, in step 3 of the method for implementing a low-code development platform that supports a single host adapting to multiple operating environments, independent applications are started for independent deployment using Ansible automated operation and maintenance, including: first configuring a basic Ansible environment and control node in the operation center; creating an Ansible Playbook file, and creating a virtual machine startup module to manage virtual machines; deploying application services for the low-code development platform, selecting middleware for the low-code development platform, including MariaDB, Minio, Nginx, and Nacos, configuring the Ansible Inventory file and running Playbooks, and the service can automatically start and deploy virtual machines.

[0012] The present invention also provides a low-code development platform implementation device that supports a single host to adapt to multiple operating environments, including an architecture management module, an operation center management module, a deployment module and an environment adaptation module.

[0013] The architecture management module defines service boundaries and establishes a microservice architecture based on the functional modules of the low-code development platform. It splits the functional modules of the low-code development platform into independent design-state microservices and running-state microservices. The operation of the running-state microservices depends on the data of the design-state microservices.

[0014] The operation center management module builds the operation center of the running microservices, and uses the operation center to manage different deployment environments using configuration files and environment variables. For containerized scenarios, the configuration files are the Nacos YAML files and the value.yml files used for helm orchestration. For physical machine / virtual machine scenarios, the configuration files are the bootstrap.yml configuration files required for each module to start. The configuration files for the middleware include the ngnix.conf file of Nginx.

[0015] Deployment module deployment environment: For containerized environments, the application management package helm is used to start the service. The designed application image is published and saved, the template file is written through helm chart, and the name of the running service image to be deployed is passed in. The service is named and started through helminstall.

[0016] For virtual machine startup scenarios, use Ansible automated operation and maintenance to start independent applications for independent deployment.

[0017] The environment adaptation module deploys a virtual isolation environment for the virtual machine startup scenario: the host group is configured through the operation center, and a corresponding Nacos namespace is configured for each host group to achieve a virtual isolation environment. The same single host is assigned to different host groups, corresponding to multiple sets of virtual isolation environments, so that different virtual isolation environment configurations can be used on a single host to start multiple versions of applications during deployment.

[0018] Furthermore, when the architecture management module of the device implementing the low-code development platform that supports a single host adapting to multiple operating environments establishes a microservice architecture, the front end is built using the VUE3 language, the back end is built using the Spring framework service, the load balancer Nginx is used to distribute requests, and Nacos provides service configuration registration.

[0019] Furthermore, the operation center management module of the device implementing a low-code development platform that supports a single host to adapt to multiple operating environments utilizes the operation center to manage different deployment environments, wherein the deployment environment involves host management, data source management, Redis management, Minio management, and Nacos management. Each environment selects a specific host, data source, Redis configuration, and all other required static information according to actual needs, and persists the environmental information after the selection is completed, and generates different configuration information according to the selected deployment scenario type, wherein the host information includes the host IP, Port, and ssh key; the data source information includes the data source Host address, port, user name, and password.

[0020] Furthermore, the deployment module of the low-code development platform implementation device that supports a single host to adapt to multiple operating environments uses Ansible automated operation and maintenance to start independent applications for independent deployment, including: first configuring the basic Ansible environment and control node in the operation center; creating an Ansible Playbook file, and creating a virtual machine startup module to manage virtual machines; deploying application services for the low-code development platform, selecting middleware for the low-code development platform, the middleware includes MariaDB, Minio, Nginx, Nacos, configuring the Ansible Inventory file and running Playbooks, and the service can automatically start the deployment of the virtual machine.

[0021] The benefits of the present invention are:

[0022] Through the method provided by the present invention, customers can support the low-code platform's function of supporting a single host to adapt to multiple operating environments, meet customers' needs for flexible and efficient customization, and improve development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 This is a schematic diagram of the microservice architecture of the low-code platform of the present invention.

[0024] Figure 2 This is a schematic diagram of the low-code platform front end.

[0025] Figure 3 It is a schematic diagram of a low-code platform application that supports multiple operating environments on a single host.

[0026] Figure 4 This is a schematic diagram of single host operation. DETAILED DESCRIPTION

[0027] The present invention is further described below in conjunction with the accompanying drawings and specific embodiments so that those skilled in the art can better understand the present invention and implement it, but the embodiments are not intended to limit the present invention.

[0028] Example 1

[0029] The present invention provides a method for implementing a low-code development platform that supports a single host adapting to multiple operating environments, including: Step 1: Based on the functional modules of the low-code development platform, define service boundaries, establish a microservice architecture, and split the functional modules of the low-code development platform into independent design-state microservices and running-state microservices, wherein the operation of the running-state microservices depends on the data of the design-state microservices.

[0030] The functional modules are divided into independent microservices such as user management, gateway service, form design, data storage, API management, process engine, etc. Each microservice has a single responsibility, which is easy to maintain and expand. Here we choose traditional programming languages ​​and frameworks, using VUE3 language for the front end and Spring framework service for the back end. The overall functional module architecture is shown below: Figure 1 As shown, the load balancer Nginx is used to distribute requests, and Nacos provides service configuration registration and discovery.

[0031] To support independent deployment functions, the design state and the running state are decoupled into independent microservices to ensure that the running state services can run independently. The design state has more comprehensive functions and can support all functions. The running state is deployed on demand. The services include basic running services, including database, user center, form management, and other functions can be subsets of these functions, or a combination of different functions, such as process engine and message service.

[0032] Step 2: Build an operation center for running microservices, and use the operation center to manage different deployment environments using configuration files and environment variables. For containerized scenarios, the configuration files are the Nacos YAML file and the value.yml file used for helm orchestration. For physical / virtual machine scenarios, the configuration files are the bootstrap.yml configuration files required to start each module. The configuration files for the middleware include the ngnix.conf file of Nginx.

[0033] The deployed environment involves host management, data source management, Redis management, Minio management, and Nacos management. Each environment selects a specific host, data source, Redis configuration, and all other required static information according to actual needs, and persists the environment information after the selection is completed, and generates different configuration information according to the selected deployment scenario type. The host information includes the host IP, Port, ssh key, etc.; the data source information includes the data source Host address, port, user name, password, etc.; Redis management and Minio management are similarly configured.

[0034] Step 3: Deployment environment: For containerized environment, use the application management package helm to start the service, where the designed application image is published and saved, the template file is written through helm chart, and the name of the running service image to be deployed is passed in, and the service is named and started through helminstall. Containerization: Package the application and dependencies into containers, such as Docker, to ensure consistency and portability in different environments. Orchestration tools: Use orchestration tools such as Kubernetes to manage the deployment, expansion and operation of containers to improve the reliability and scalability of the system.

[0035] For the scenario of starting virtual machines, use Ansible automated operation and maintenance to start independent applications for independent deployment. The method of using Ansible automated operation and maintenance to start independent applications for independent deployment includes: first configuring the basic Ansible environment and control nodes in the operation center; creating an Ansible Playbook file, and creating a virtual machine startup module to manage virtual machines; deploying application services for low-code development platforms, selecting middleware for low-code development platforms, including MariaDB, Minio, Nginx, and Nacos, configuring Ansible Inventory files and running Playbooks, and the service can automatically start and deploy virtual machines.

[0036] Step 4: Deploy a virtual isolation environment for the virtual machine startup scenario: Configure the host group through the operation center, and configure a corresponding Nacos namespace for each host group to implement a virtual isolation environment, so that the same single host is assigned to different host groups, corresponding to multiple sets of virtual isolation environments, so that when deployed, different virtual isolation environment configurations can be used on a single host to start multiple versions of applications. The operation center configures the host group. Each host group can contain multiple hosts. The host information includes the machine IP address and port. At the same time, the operation and maintenance personnel need to configure the available port range of the machine to support the low-code services that will be deployed and run on the machine. On the host, each running application uses its own independent database during operation, such as Figure 4 As shown, the security and isolation of data when the program is running is guaranteed.

[0037] Example 2

[0038] The present invention also provides a low-code development platform implementation device that supports a single host to adapt to multiple operating environments, including an architecture management module, an operation center management module, a deployment module and an environment adaptation module.

[0039] The architecture management module defines service boundaries and establishes a microservice architecture based on the functional modules of the low-code development platform. It splits the functional modules of the low-code development platform into independent design-state microservices and running-state microservices. The operation of the running-state microservices depends on the data of the design-state microservices.

[0040] The operation center management module builds the operation center of the running microservices, and uses the operation center to manage different deployment environments using configuration files and environment variables. For containerized scenarios, the configuration files are the Nacos YAML files and the value.yml files used for helm orchestration. For physical machine / virtual machine scenarios, the configuration files are the bootstrap.yml configuration files required for each module to start. The configuration files for the middleware include the ngnix.conf file of Nginx.

[0041] Deployment module deployment environment: For containerized environments, the application management package helm is used to start the service. The designed application image is published and saved, the template file is written through helm chart, and the name of the running service image to be deployed is passed in. The service is named and started through helminstall.

[0042] For virtual machine startup scenarios, use Ansible automated operation and maintenance to start independent applications for independent deployment.

[0043] The environment adaptation module deploys a virtual isolation environment for the virtual machine startup scenario: the host group is configured through the operation center, and a corresponding Nacos namespace is configured for each host group to achieve a virtual isolation environment. The same single host is assigned to different host groups, corresponding to multiple sets of virtual isolation environments, so that different virtual isolation environment configurations can be used on a single host to start multiple versions of applications during deployment.

[0044] As the information interaction, execution process and other contents between the modules in the above-mentioned device are based on the same concept as the embodiment of the method of the present invention, the specific contents can be found in the description of the embodiment of the method of the present invention and will not be repeated here.

[0045] Similarly, through the method provided by the present invention, the device of the present invention can enable customers to support the low-code platform's function of supporting a single host to adapt to multiple operating environments, meet customers' needs for flexible and efficient customization, and improve development efficiency.

[0046] It should be noted that not all steps and modules in the above-mentioned processes and device structures are necessary, and some steps or modules can be ignored according to actual needs. The execution order of each step is not fixed and can be adjusted as needed. The system structure described in the above-mentioned embodiments can be a physical structure or a logical structure, that is, some modules may be implemented by the same physical entity, or some modules may be implemented by multiple physical entities, or some components in multiple independent devices may be implemented together.

[0047] The above-described embodiments are only preferred embodiments for fully illustrating the present invention, and the protection scope of the present invention is not limited thereto. Equivalent substitutions or changes made by those skilled in the art based on the present invention are within the protection scope of the present invention. The protection scope of the present invention shall be subject to the claims.

Claims

1. A method for implementing a low-code development platform that supports a single host adapting to multiple operating environments, characterized by: include: Step 1: Define service boundaries and establish a microservice architecture based on the functional modules of the low-code development platform. Split the functional modules of the low-code development platform into independent design-state microservices and running-state microservices. The operation of the running-state microservices depends on the data of the design-state microservices. Step 2: Build an operation center for running microservices, and use the operation center to manage different deployment environments using configuration files and environment variables. For containerized scenarios, the configuration files are the Nacos YAML file and the value.yml file used for helm orchestration. For physical / virtual machine scenarios, the configuration files are the bootstrap.yml configuration files required for each module to start. The configuration files for the middleware include the ngnix.conf file of Nginx. Step 3: Deployment environment: For containerized environment, use the application management package helm to start the service, publish the designed application image and save it, write the template file through helm chart, and pass in the name of the running service image to be deployed, and start the service through helminstall. For virtual machine startup scenarios, use Ansible automated operation and maintenance to start independent applications for independent deployment. Step 4: Deploy a virtual isolation environment for the virtual machine startup scenario: Configure the host group through the operation center, and configure a corresponding Nacos namespace for each host group to implement a virtual isolation environment. The same single host is assigned to different host groups, corresponding to multiple sets of virtual isolation environments, so that different virtual isolation environment configurations can be used on a single host to start multiple versions of applications during deployment.

2. According to claim 1, a method for implementing a low-code development platform that supports a single host to adapt to multiple operating environments is characterized by: When establishing the microservice architecture in step 1, the front end is built using the VUE3 language, the back end is built using the Spring framework service, the load balancer Nginx is used to distribute requests, and Nacos provides service configuration registration.

3. According to claim 1, a method for implementing a low-code development platform that supports a single host to adapt to multiple operating environments is characterized by: In step 2, the operation center is used to manage different deployment environments, where the deployment environment involves host management, data source management, Redis management, Minio management, and Nacos management. Each environment selects a specific host, data source, Redis configuration, and all other required static information according to actual needs, and persists the environment information after the selection is completed. Different configuration information is generated according to the selected deployment scenario type, where the host information includes the host IP, Port, and sshkey; the data source information includes the data source Host address, port, user name, and password.

4. According to claim 1, a method for implementing a low-code development platform that supports a single host adapting to multiple operating environments is characterized by: In step 3, use Ansible automated operation and maintenance to start independent applications for independent deployment, including: first configure the basic Ansible environment and control node in the operation center; create an Ansible Playbook file, and create a virtual machine startup module to manage virtual machines; deploy application services for low-code development platforms, select middleware for low-code development platforms, including MariaDB, Minio, Nginx, Nacos, configure Ansible Inventory files and run Playbooks, and the service can automatically start and deploy virtual machines.

5. A low-code development platform implementation device that supports a single host to adapt to multiple operating environments, characterized by It includes architecture management module, operation center management module, deployment module and environment adaptation module. The architecture management module defines service boundaries and establishes a microservice architecture based on the functional modules of the low-code development platform. It splits the functional modules of the low-code development platform into independent design-state microservices and running-state microservices. The operation of the running-state microservices depends on the data of the design-state microservices. The operation center management module builds the operation center of the running microservices, and uses the operation center to manage different deployment environments using configuration files and environment variables. For containerized scenarios, the configuration files are the Nacos YAML files and the value.yml files used for helm orchestration. For physical machine / virtual machine scenarios, the configuration files are the bootstrap.yml configuration files required for each module to start. The configuration files for the middleware include the ngnix.conf file of Nginx. Deployment module deployment environment: For containerized environments, the application management package helm is used to start the service. The designed application image is published and saved, the template file is written through helm chart, and the name of the running service image to be deployed is passed in. The service is named and started through helminstall. For virtual machine startup scenarios, use Ansible automated operation and maintenance to start independent applications for independent deployment. The environment adaptation module deploys a virtual isolation environment for the virtual machine startup scenario: the host group is configured through the operation center, and a corresponding Nacos namespace is configured for each host group to achieve a virtual isolation environment. The same single host is assigned to different host groups, corresponding to multiple sets of virtual isolation environments, so that different virtual isolation environment configurations can be used on a single host to start multiple versions of applications during deployment.

6. According to claim 5, a low-code development platform implementation device that supports a single host to adapt to multiple operating environments is characterized by the architecture When the management module establishes a microservice architecture, the front end is built using the VUE3 language, the back end is built using the Spring framework service, the load balancer Nginx is used to distribute requests, and Nacos provides service configuration registration.

7. According to claim 5, a low-code development platform implementation device that supports a single host to adapt to multiple operating environments is characterized in that the operation center management module uses the operation center to manage different deployment environments, wherein the deployment environment involves host management, data source management, Redis management, Minio management, and Nacos management. Each environment selects a specific host, data source, Redis configuration, and all other required static information according to actual needs, and persists the environmental information after the selection is completed, and generates different configuration information according to the selected deployment scenario type, wherein the host information includes the host IP, Port, and ssh key; the data source information includes the data source Host address, port, user name, and password.

8. According to claim 5, a low-code development platform implementation device that supports a single host to adapt to multiple operating environments is characterized by: The deployment module uses Ansible automated operation and maintenance to start independent applications for independent deployment, including: first configuring the basic Ansible environment and control nodes in the operation center; creating an Ansible Playbook file, and creating a virtual machine startup module to manage virtual machines; deploying application services for low-code development platforms, selecting middleware for low-code development platforms, including MariaDB, Minio, Nginx, and Nacos, configuring Ansible Inventory files and running Playbooks, and the service can automatically start and deploy virtual machines.

Images