An application access method and device based on a low-code development platform

Abstract

The application relates to a low-code development platform-based application access method and device, and relates to the technical field of computers.The method comprises the following steps: in response to a user operation of selecting a target application to be published, deploying an application instance of the target application according to configuration information of the target application; wherein the application instance comprises N replica application instances, the N replica application instances are deployed with N intranet IP addresses, N is an integer greater than 0; after the application instance of the target application is deployed, registering an application address of the target application to a gateway and generating an application access correspondence table; wherein the application address comprises a shared gateway IP address and a link suffix of the target application; in response to a user operation of inputting the application address, determining a target replica application instance meeting a requirement from the N replica application instances according to the application access correspondence table, so that the reuse rate of IP is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an application access method and apparatus based on a low-code development platform. Background Technology

[0002] With the development of internet technology, front-end technology is constantly expanding. The emergence of various front-end frameworks has reduced the difficulty of front-end development. Developing an application (or webpage) mainly involves front-end developers creating interfaces between the front-end page and the back-end based on user needs, and then rendering these interfaces onto the front-end page. Webpages or applications can be developed using low-code development platforms. These platforms utilize built-in components, such as icons, buttons, and dialog boxes, to orchestrate front-end webpages and configure component API calls, reducing front-end workload and accelerating product development.

[0003] When developing applications, each application needs to be assigned an Internet Protocol (IP) for network interconnection to allow user access. Since IP resources are limited, as the number of applications increases, IP addresses are continuously consumed, leading to resource waste. Summary of the Invention

[0004] This application provides an application access method based on a low-code development platform to improve the reuse rate of IP addresses.

[0005] Firstly, a method for accessing applications based on a low-code development platform is provided, including:

[0006] In response to a user's action to select and publish a target application, an application instance of the target application is deployed according to the configuration information of the target application. The application instance includes N replica application instances, each deployed with N internal network IP addresses, where N is an integer greater than 0. After the application instance of the target application is deployed, the application address of the target application is registered with the gateway, and an application access mapping table is generated. The application address includes a shared gateway IP address and the link suffix of the target application. In response to a user's action to input the application address, a target replica application instance that meets the requirements is determined from the N replica application instances according to the application access mapping table. This target replica application instance is used to provide application services.

[0007] Optionally, the application access mapping table is used to record the mapping relationship between the application address of the target application and the N intranet IP addresses; the method further includes:

[0008] The validity of the application address is monitored according to a first set period; if the application address is detected to be invalid, a new application address of the target application is registered with the gateway, and the application address in the access application relationship table is updated to the new application address.

[0009] Optionally, the method further includes:

[0010] Monitor the running status of the N replica application instances according to the second set period to obtain the load pressure of the N replica application instances; calculate the average load pressure of the N replica application instances to obtain the load pressure of the application instance; update the application access correspondence table according to the load pressure of the N replica application instances and the load pressure of the application instance.

[0011] Optionally, the low-code development platform includes a list of replicas to be deleted, which is used to cache replica application instances that have not yet started their application services; updating the application access correspondence table based on the load pressure of the N replica application instances and the load pressure of the application instance includes:

[0012] If the load pressure of the application instance is greater than the upper limit of the first threshold, it is determined whether the list of replicas to be deleted is empty; if not, the first replica application instance in the list of replicas to be deleted is removed and the first replica application instance is updated in the application access correspondence table; if yes, and N is less than the upper limit of the second threshold, at least one replica application instance is added to the target application.

[0013] Optionally, updating the application access mapping table based on the load pressure of the N replica application instances and the load pressure of the application instance includes:

[0014] If the load pressure of the application instance is less than or equal to the lower limit of the first threshold, and N is greater than or equal to the lower limit of the second threshold, then the second replica application instance among the N replica application instances is removed from the application access correspondence table, and the second replica application instance is added to the list of replicas to be deleted. The second replica application instance is the replica application instance with the lowest load pressure.

[0015] Secondly, an application access device based on a low-code development platform is provided, including:

[0016] The deployment module is used to deploy an application instance of the target application according to the configuration information of the target application in response to a user operation that selects to publish the target application; wherein the application instance includes N replica application instances, and the N replica application instances are deployed with N internal network IP addresses, where N is an integer greater than 0; the registration module is used to register the application address of the target application with the gateway after the application instance of the target application is deployed, and generate an application access mapping table; wherein the application address includes a shared gateway IP address and the link suffix of the target application; the access module is used to determine a target replica application instance that meets the requirements from the N replica application instances according to the application access mapping table in response to a user operation that inputs the application address, and the target replica application instance is used to provide application services.

[0017] Optionally, the application access mapping table is used to record the mapping relationship between the application address of the target application and the N intranet IP addresses; the device further includes a monitoring module; the monitoring module is used to monitor the validity of the application address according to a first set period; if the application address is detected to be invalid, a new application address of the target application is registered with the gateway, and the application address in the application access mapping table is updated to the new application address.

[0018] Optionally, the access module is further configured to:

[0019] Monitor the running status of the N replica application instances according to the second set period to obtain the load pressure of the N replica application instances; calculate the average load pressure of the N replica application instances to obtain the load pressure of the application instance; update the application access correspondence table according to the load pressure of the N replica application instances and the load pressure of the application instance.

[0020] Optionally, the low-code development platform includes a list of replicas to be deleted, which is used to cache replica application instances that have not yet started application services;

[0021] The access module is specifically used for:

[0022] If the load pressure of the application instance is greater than the upper limit of the first threshold, it is determined whether the list of replicas to be deleted is empty; if not, the first replica application instance in the list of replicas to be deleted is removed and the first replica application instance is updated in the application access correspondence table; if yes, and N is less than the upper limit of the second threshold, at least one replica application instance is added to the target application.

[0023] Optionally, the access module is specifically used for:

[0024] If the load pressure of the application instance is less than or equal to the lower limit of the first threshold, and N is greater than or equal to the upper limit of the second threshold, then the second replica application instance among the N replica application instances is removed from the application access correspondence table, and the second replica application instance is added to the list of replicas to be deleted. The second replica application instance is the replica application instance with the lowest load pressure.

[0025] Thirdly, an electronic device is provided, comprising:

[0026] A memory for storing computer programs; a processor for executing the computer programs stored in the memory to implement the method steps described in any one of the first aspects.

[0027] Fourthly, a computer-readable storage medium is provided, wherein a computer program is stored therein, and when executed by a processor, the computer program implements the method steps described in any one of the first aspects.

[0028] In this embodiment, in response to a user's operation of selecting and publishing a target application on a low-code development platform, an application instance of the target application is deployed according to the configuration information of the target application. After the application instance of the target application is deployed, the application address of the target application is registered with the gateway, and an application access mapping table is generated. The application address includes a shared gateway IP address and the link suffix of the target application. Therefore, it can avoid different applications occupying a single gateway IP address, thus improving the IP reuse rate. Furthermore, in response to a user's operation of inputting the application address, a target replica application instance that meets the requirements is determined from N replica application instances according to the application access mapping table. This target replica application instance is used to provide application services. Therefore, the stability of the application service can be guaranteed, thereby improving the user experience.

[0029] For the various aspects of the second to fourth aspects mentioned above, and the technical effects that each aspect may achieve, please refer to the above description of the technical effects that can be achieved for the first aspect or the various possible solutions in the first aspect, which will not be repeated here. Attached Figure Description

[0030] Figure 1 This is a schematic diagram illustrating an application scenario applicable to an embodiment of this application;

[0031] Figure 2 A flowchart illustrating an application access method based on a low-code development platform, provided in this application embodiment;

[0032] Figure 3 A flowchart for monitoring the validity of an application address is provided in an embodiment of this application;

[0033] Figure 4 A logical diagram illustrating application access provided in an embodiment of this application;

[0034] Figure 5 A flowchart illustrating the expansion of a copy application instance is provided in this application embodiment;

[0035] Figure 6 A flowchart illustrating the reduction of a copy application instance is provided in an embodiment of this application;

[0036] Figure 7 A schematic diagram of the structure of an application access device based on a low-code platform provided in this application embodiment;

[0037] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The specific operational methods in the method embodiments can also be applied to the device embodiments or system embodiments. It should be noted that in the description of this application, "multiple" is understood as "at least two". "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. A connected to B can represent: A and B directly connected, and A and B connected through C. Furthermore, in the description of this application, terms such as "first" and "second" are used only for distinguishing the purpose of description and should not be construed as indicating or implying relative importance or order.

[0039] To better understand the embodiments of this application, the technical terms involved in the embodiments of this application will be explained below.

[0040] (1) Components: Built-in development components on low-code development platforms, such as front-end components like buttons, tables, and text.

[0041] (2) Application: Users select the required components on the low-code development platform, drag them onto the low-code editor page, configure the component properties and styles, and configure method calls to render the components, thereby generating the application.

[0042] (3) Container: The final deployment location of applications developed on a low-code development platform. A container is an executable environment that contains the tools required for the application to run.

[0043] (4) Gateway: The endpoint for application access. For example, applications developed on a low-code development platform can access related applications through the gateway.

[0044] (5) Internal IP: The IP address that users can access only after configuring a Virtual Private Network (VPN).

[0045] (6) External IP: The IP address that users can access directly without configuring a VPN.

[0046] (7) Kubernetes, abbreviated as K8s, is an abbreviation formed by replacing the eight characters "ubernete". It is an open source application used to manage containerized applications on multiple hosts in a cloud platform. The goal of Kubernetes is to make deploying containerized applications simple and powerful. Kubernetes provides a mechanism for application deployment, planning, updating and maintenance.

[0047] The following is a brief introduction to the application scenarios to which the technical solutions of the embodiments of this application are applicable. It should be noted that the application scenarios described below are only for illustrating the embodiments of this application and are not intended to limit the scope. In specific implementation, the technical solutions provided by the embodiments of this application can be flexibly applied according to actual needs.

[0048] Figure 1 This is a schematic diagram of an application scenario applicable to an embodiment of this application. As shown in the figure, the scenario mainly includes a terminal 10 and a server 11. The terminal 10 and the server 11 can interact with each other through a communication network, and the communication network can use wireless communication or wired communication.

[0049] Optionally, terminal 10 can access the network and communicate with server 11 via cellular mobile communication technology, which may include 5th Generation Mobile Networks (5G) technology.

[0050] Optionally, terminal 10 can access the network and communicate with server 11 via short-range wireless communication, which may include Wireless Fidelity (Wi-Fi) technology.

[0051] This application embodiment does not impose any limitation on the number of the above-mentioned devices, such as Figure 1 As shown, only terminal 10 and server 11 are described as examples. The following is a brief introduction to each of the above devices and their respective functions.

[0052] Terminal 10 is a device that can provide users with voice and / or data connectivity, such as mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), etc.

[0053] In addition, a client for developing applications can be installed on the terminal 10. This client can be software (such as an APP, browser, etc.), or a webpage, mini-program, etc.

[0054] In this embodiment, terminal 10 can interact with server 11 via the aforementioned client to exchange information related to application building. For example, terminal 10 can open a user interface for building an application via the aforementioned client, then drag the required components from the user interface into the editor workbench, configure the style, attributes, and data source of the components, and generate connectors to bind to the components, thereby developing an application (which can correspond to the target application below). After the developed application is sent to server 11 for deployment, the application can be put into use.

[0055] Server 11 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0056] Furthermore, in this embodiment of the application, the server 11 may be equipped with an application access device based on development (e.g., a low-code development platform) related to the client. This device can meet the deployment of various applications. After successful deployment, the application address of the application can be output to the terminal 10 so that the user can access the developed application through the application address and experience the application function.

[0057] To further illustrate the technical solutions provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of this application provide method operation steps as shown in the following embodiments or drawings, the method may include more or fewer operation steps based on conventional or non-inventive methods. In steps where there is no logically necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the device executes the method, it may be executed in the order shown in the embodiments or drawings, or in combination.

[0058] Figure 2This application provides a flowchart of an application access method based on a low-code development platform. This process can be executed by an application access device of the low-code development platform. This device can be implemented in software, hardware, or a combination of both. Figure 2 As shown, the process includes the following steps:

[0059] 201: In response to a user action that selects to publish the target application, deploy an application instance of the target application based on the target application's configuration information.

[0060] In this step, specifically, the user can do so on a terminal (e.g., Figure 1 On the user interface of terminal 10, the required components are dragged and dropped into the editor workbench for arrangement. After the target application is arranged, the user can click the icon of the target application on the user interface by touch screen or other means. After the low-code development platform (such as the application access device based on the low-code development platform mounted on server 11 in the figure) receives the target application, it can deploy the application instance of the target application according to the configuration information of the target application.

[0061] Optionally, the deployment method can be implemented by the low-code development platform calling Kubernetes. The deployed application instance can include N replica application instances, each of which is deployed with N internal network IP addresses, where N is an integer greater than 0 and can be flexibly adjusted according to actual needs. Each application instance is also deployed with an internal network IP address to facilitate the differentiation of different applications.

[0062] 202: After the application instance of the above target application is deployed, register the application address of the target application with the gateway and generate an application access correspondence table.

[0063] The application address includes a shared gateway IP address and the link suffix of the target application. The shared gateway IP address is used by all developed target applications. The link suffixes in the application addresses of different target applications are different. For example, the application address of target application 1 is gateway IP address + link suffix 1, and the application address of target application 2 is gateway IP address + link suffix 2. This avoids different target applications occupying a single gateway IP address, which would result in excessive consumption of IP resources.

[0064] Optionally, the application access mapping table is used to record the mapping relationship between the application address of the target application and the above N intranet IP addresses. It may further include the intranet IP address of the application instance, as shown in Table 1, which exemplarily illustrates the application access mapping table.

[0065] Table 1: Application Access Correspondence Table

[0066]

[0067] Optionally, the gateway IP address can be an external gateway IP address, which allows users to access the target application without needing to mount a VPN, thereby reducing network restrictions.

[0068] In some embodiments, since the registered application address may become invalid during gateway restart or failover, the application address of the target application can be monitored in real time to ensure the reliability of the application service. For example... Figure 3 As shown, an exemplary flowchart of a method for monitoring the validity of an application address is illustrated in an embodiment of this application. Specifically, it may include the following steps:

[0069] 301: Monitor the validity of the application address according to the first set period.

[0070] In this step, the validity of the application address can be monitored in real time every 10 seconds.

[0071] 302: Check if the application address is offline. If not, proceed to 303. If yes, end this process.

[0072] 303: Check if the above access application relationship table exists. If it does, proceed to 301; otherwise, proceed to 304.

[0073] In this step, if the access application relationship table related to the application address is not detected when the application address is not offline, it indicates that the gateway is restarting or failover. Otherwise, it indicates that the application address is valid, and the process will switch to 301 and continue monitoring according to the first set cycle.

[0074] 304: Register the new application address of the target application with the gateway and update the application address in the access application relationship table to the new application address.

[0075] In this step, after updating and obtaining the new access application relationship table, the process can proceed to step 301 to continue monitoring the validity of the new application address according to the first set cycle.

[0076] In other embodiments, when the deployment of the application instance of the target application is cancelled, the application address of the target application can also be removed from the gateway, thereby avoiding a large amount of junk data on the gateway, which would waste resources, affect gateway performance, and the availability of other application services.

[0077] 203: In response to a user's input of an application address, based on the application access mapping table mentioned above, a target replica application instance that meets the requirements is determined from N replica application instances. This target replica application instance is used to provide application services.

[0078] Once the target application's application address is successfully registered with the gateway, users can use that application address to fulfill their access requests, such as... Figure 4 As shown, an exemplary schematic diagram of an application access logic provided in an embodiment of this application is illustrated.

[0079] First, in response to the terminal (e.g.) Figure 1 The user operation of entering the application address in the browser of terminal 10) determines the internal network IP address 1 of the application instance corresponding to the application address according to the application access correspondence table on the gateway (as shown in Table 1). Then, it queries the four replica application instances that have a relationship and selects the replica application instance 2 (target replica application instance) that meets the requirements (e.g., the lowest load pressure) from these four replica application instances to provide application services.

[0080] In other embodiments, when the application address is put into use, the access volume may be too high at times and too low at other times during the actual access process. Therefore, in order to ensure the performance of each replica application instance, the load pressure of each replica application instance can be monitored in real time, which also facilitates the subsequent expansion or reduction of replica application instances based on this. Specifically, it can be: monitoring the running status of N replica application instances according to a second set period to obtain the load pressure of N replica application instances; calculating the average load pressure of N replica application instances to obtain the load pressure of the application instance; and updating the application access correspondence table according to the load pressure of N replica application instances and the load pressure of the application instance.

[0081] Based on the aforementioned load pressure monitoring, when access volume is too high, the replica application instances can be scaled up in a timely manner, and when access volume decreases, the replica application instances can be scaled down in a timely manner. This dynamic scaling of replica application instances ensures application service stability and improves user experience. Specifically, this can include the following scenarios:

[0082] Case 1: such as Figure 5 The illustration shows a schematic diagram of a process for expanding a copy application instance according to an embodiment of this application. It may include the following steps:

[0083] 501: Determine whether the load pressure of the above application instance is greater than the upper limit of the first threshold. If yes, proceed to 502. If no, end this process, indicating that there is no need to expand the replica application instance.

[0084] 502: Check if the list of copies to be deleted is empty. If not, proceed to 503; if yes, proceed to 504.

[0085] In this step, the list of replicas to be deleted is used to cache replica application instances that have not yet started the application service.

[0086] 503: Remove the first replica application instance from the list of replicas to be deleted and update the application access mapping table with the first replica application instance.

[0087] The first copy application instance is any one of the copies to be deleted in the list.

[0088] 504: Is the above N less than the upper limit of the second threshold? If yes, proceed to 505; otherwise, proceed to 506.

[0089] 505: Add at least one copy of the application instance to the target application.

[0090] This step may involve calling the Kubernetes interface to expand the container and build a new replica application instance, and updating the relevant information of the newly built replica application instance to the application access relationship table to provide application services, thereby ensuring the stability of application services and improving user experience.

[0091] 506: Rate limiting is applied to access to the aforementioned target applications.

[0092] In this step, when the number of accesses per second to the target application is too high, some users' access to the application will be randomly rejected, thereby preventing all resources in this access scenario from being occupied by the target application and affecting the application services of other applications.

[0093] Scenario 2: such as Figure 6 The diagram shown illustrates a process for reducing the number of duplicate application instances according to an embodiment of this application. It may include the following steps:

[0094] 601: Determine whether the load pressure of the application instance is less than or equal to the lower limit of the first threshold. If yes, proceed to 602; otherwise, end this process, indicating that there is no need to reduce the replica application instance.

[0095] 602: Determine whether the above N is greater than or equal to the lower limit of the second threshold. If yes, it indicates that the replica application instance can be reduced, and proceed to 603; otherwise, end this process.

[0096] 603: Remove the second replica application instance from the application access mapping table among N replica application instances, and add the second replica application instance to the list of replicas to be deleted.

[0097] Optionally, the second replica application instance is the replica application instance with the lowest load pressure.

[0098] In some embodiments, the above-mentioned list of replicas to be deleted can be periodically checked and cleaned up in real time. Specifically, if it is detected that the number of replica application instances requested to the list of replicas to be deleted is 0 and exceeds a certain period of time, the replica application instances in the list of replicas to be deleted can be deleted.

[0099] In other embodiments, the number of replicas of the application instance required in the future can be predicted based on historical data, which may include the load pressure of the application instance, the load pressure of the application instance, and the number of replicas of the application instance. For example, the ratio of the load pressure of the application instance to the number of replicas in the historical data, and the load pressure value of the target application in the next hour, can be used to calculate the number of replicas of the application instance in the next hour; if the number of replicas is greater than the number of replicas of the current application instance, then based on... Figure 5 The method shown expands the replica application instance. If the number of replicas is less than or equal to the number of replicas of the current application instance, no operation is performed. This allows for flexible dynamic expansion or reduction of the replica application instances providing application services, improving user experience.

[0100] In this embodiment, in response to a user operation selecting to publish a target application on a low-code development platform, an application instance of the target application is deployed according to the configuration information of the target application. After the application instance of the target application is deployed, the application address of the target application is registered with the gateway, and an application access mapping table is generated. The application address includes a shared gateway IP address and the link suffix of the target application. Therefore, it can avoid different applications occupying a single gateway IP address, thus improving the IP reuse rate. Furthermore, in response to a user operation inputting the application address, a target replica application instance that meets the requirements is determined from N replica application instances according to the application access mapping table. This target replica application instance is used to provide application services. Therefore, the stability of the application service can be guaranteed, thereby improving the user experience.

[0101] Based on the same technical concept, this application embodiment also provides an application access device based on a low-code development platform, which can implement the above-described application access method based on a low-code development platform.

[0102] Figure 7 An application access device based on a low-code development platform is provided in this application embodiment. The device includes: a deployment module 701, a registration module 702, and an access module 703, and may further include a monitoring module 704.

[0103] Deployment module 701 is used to respond to a user operation that selects to publish a target application and deploy an application instance of the target application according to the configuration information of the target application; wherein, the application instance includes N replica application instances, and the N replica application instances are deployed with N internal network IP addresses, where N is an integer greater than 0.

[0104] The registration module 702 is used to register the application address of the target application with the gateway and generate an application access correspondence table after the application instance of the target application is deployed; wherein, the application address includes a shared gateway IP address and the link suffix of the target application.

[0105] Access module 703 is used to respond to a user operation that inputs the application address, and determine a target replica application instance that meets the requirements from the N replica application instances according to the application access correspondence table. The target replica application instance is used to provide application services.

[0106] The monitoring module 704 is used to monitor the validity of the application address according to a first set period; if the application address is detected to be invalid, it registers a new application address of the target application with the gateway and updates the application address in the access application relationship table to the new application address.

[0107] Optionally, access module 703 is also used for:

[0108] Monitor the running status of the N replica application instances according to the second set period to obtain the load pressure of the N replica application instances; calculate the average load pressure of the N replica application instances to obtain the load pressure of the application instance; update the application access correspondence table according to the load pressure of the N replica application instances and the load pressure of the application instance.

[0109] Optionally, the low-code development platform includes a list of replicas to be deleted, which is used to cache replica application instances that have not yet started their application services; the access module 703 is specifically used for:

[0110] If the load pressure of the application instance is greater than the upper limit of the first threshold, it is determined whether the list of replicas to be deleted is empty; if not, the first replica application instance in the list of replicas to be deleted is removed and the first replica application instance is updated in the application access correspondence table; if yes, and N is less than the upper limit of the second threshold, at least one replica application instance is added to the target application.

[0111] Optionally, the access module 703 is specifically used for:

[0112] If the load pressure of the application instance is less than or equal to the lower limit of the first threshold, and N is greater than or equal to the upper limit of the second threshold, then the second replica application instance among the N replica application instances is removed from the application access correspondence table, and the second replica application instance is added to the list of replicas to be deleted. The second replica application instance is the replica application instance with the lowest load pressure.

[0113] It should be noted that the apparatus provided in this application embodiment can implement all the method steps of the application access method based on the low-code development platform and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0114] Based on the same technical concept, this application also provides an electronic device that can realize the functions of the aforementioned application access device based on a low-code development platform.

[0115] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0116] At least one processor 801 and a memory 802 connected to at least one processor 801. In this embodiment, the specific connection medium between the processor 801 and the memory 802 is not limited. Figure 8 The example shown is the connection between processor 801 and memory 802 via bus 800. Bus 800 is... Figure 8 The connections between other components are indicated by thick lines and are for illustrative purposes only, not as limiting information. The 800 bus can be divided into address bus, data bus, control bus, etc., for ease of representation. Figure 8 The term is represented by a single thick line, but this does not imply that there is only one bus or one type of bus. Alternatively, the processor 801 can also be called a controller; there is no restriction on the name.

[0117] In this embodiment, the memory 802 stores instructions executable by at least one processor 801. By executing the instructions stored in the memory 802, the at least one processor 801 can execute the application access method based on a low-code development platform discussed above. The processor 801 can implement... Figure 7 The functions of each module in the device shown.

[0118] The processor 801 is the control center of the device. It can connect to various parts of the control device through various interfaces and lines. By running or executing instructions stored in memory 802 and calling data stored in memory 802, the processor can perform various functions and process data, thereby monitoring the device as a whole.

[0119] In one possible design, processor 801 may include one or more processing units. Processor 801 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into processor 801. In some embodiments, processor 801 and memory 802 may be implemented on the same chip; in some embodiments, they may also be implemented on separate chips.

[0120] The processor 801 can be a general-purpose processor, such as a central processing unit (CPU), digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the application access method based on a low-code development platform disclosed in the embodiments of this application can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0121] Memory 802, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. Memory 802 may include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic storage, magnetic disk, optical disk, etc. Memory 802 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. In the embodiments of this application, memory 802 can also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0122] By designing and programming the processor 801, the code corresponding to the application access method based on a low-code development platform described in the foregoing embodiments can be embedded into the chip, thereby enabling the chip to execute the code during runtime. Figure 2 The illustrated embodiment presents an application access method based on a low-code development platform. How to design and program the processor 801 is a technique well-known to those skilled in the art and will not be described further here.

[0123] It should be noted that the electronic device provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0124] This application also provides a computer-readable storage medium storing computer-executable instructions for causing a computer to execute an application access method based on a low-code development platform as described in the above embodiments.

[0125] This application also provides a computer program product, which, when invoked by a computer, causes the computer to execute an application access method based on a low-code development platform as described in the above embodiments.

[0126] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0127] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0128] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0129] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

Claims

1. An application access method based on a low-code development platform, characterized in that, include: In response to a user's action to select a target application for deployment, an application instance of the target application is deployed according to the configuration information of the target application; wherein, the application instance includes N replica application instances, and the N replica application instances are deployed with N internal network IP addresses, where N is an integer greater than 0; Once the application instance of the target application is deployed, the application address of the target application is registered with the gateway, and an application access correspondence table is generated; wherein, the application address includes the shared gateway IP address and the link suffix of the target application; In response to a user operation that inputs the application address, a target replica application instance that meets the requirements is determined from the N replica application instances according to the application access correspondence table. The target replica application instance is used to provide application services.

2. The method as described in claim 1, characterized in that, The application access mapping table is used to record the mapping relationship between the application address of the target application and the N internal network IP addresses; the method further includes: The validity of the application address is monitored according to the first set period; If the application address is detected to be invalid, a new application address for the target application is registered with the gateway, and the application address in the application access correspondence table is updated to the new application address.

3. The method as described in claim 1, characterized in that, The method further includes: Monitor the running status of the N replica application instances according to the second set period to obtain the load pressure of the N replica application instances; Calculate the average load pressure of the N replica application instances to obtain the load pressure of the application instance; Update the application access mapping table based on the load pressure of the N replica application instances and the load pressure of the application instance.

4. The method as described in claim 3, characterized in that, The low-code development platform includes a list of replicas to be deleted, which is used to cache replica application instances that have not yet started application services. The step of updating the application access mapping table based on the load pressure of the N replica application instances and the load pressure of the application instances includes: If the load pressure of the application instance is greater than the upper limit of the first threshold, then it is determined whether the list of replicas to be deleted is empty; If not, remove the first replica application instance from the list of replicas to be deleted, and update the first replica application instance to the application access correspondence table; If so, and the N is less than the upper limit of the second threshold, then at least one copy application instance is added to the target application.

5. The method as described in claim 4, characterized in that, The step of updating the application access mapping table based on the load pressure of the N replica application instances and the load pressure of the application instances includes: If the load pressure of the application instance is less than or equal to the lower limit of the first threshold, and N is greater than or equal to the lower limit of the second threshold, then the second replica application instance among the N replica application instances is removed from the application access correspondence table, and the second replica application instance is added to the list of replicas to be deleted. The second replica application instance is the replica application instance with the lowest load pressure.

6. An application access device based on a low-code development platform, characterized in that, include: The deployment module is used to respond to a user operation that selects a target application for release, and deploy an application instance of the target application according to the configuration information of the target application; wherein, the application instance includes N replica application instances, and the N replica application instances are deployed with N internal network IP addresses, where N is an integer greater than 0; The registration module is used to register the application address of the target application with the gateway after the application instance of the target application is deployed, and to generate an application access correspondence table; wherein, the application address includes a shared gateway IP address and the link suffix of the target application; The access module is used to respond to a user operation that inputs the application address, and determine a target replica application instance that meets the requirements from the N replica application instances according to the application access correspondence table. The target replica application instance is used to provide application services.

7. The apparatus as claimed in claim 6, characterized in that, The application access mapping table is used to record the mapping relationship between the application address of the target application and the N intranet IP addresses; the device also includes a monitoring module; The monitoring module is used to monitor the validity of the application address according to a first set period. If the application address is detected to be invalid, a new application address for the target application is registered with the gateway, and the application address in the application access correspondence table is updated to the new application address.

8. The apparatus as claimed in claim 6, characterized in that, The access module is also used for: Monitor the running status of the N replica application instances according to the second set period to obtain the load pressure of the N replica application instances; Calculate the average load pressure of the N replica application instances to obtain the load pressure of the application instance; Update the application access mapping table based on the load pressure of the N replica application instances and the load pressure of the application instance.

9. The apparatus as claimed in claim 8, characterized in that, The low-code development platform includes a list of replicas to be deleted, which is used to cache replica application instances that have not yet started application services. The access module is specifically used for: If the load pressure of the application instance is greater than the upper limit of the first threshold, then it is determined whether the list of replicas to be deleted is empty; If not, remove the first replica application instance from the list of replicas to be deleted, and update the first replica application instance to the application access correspondence table; If so, and the N is less than the upper limit of the second threshold, then at least one copy application instance is added to the target application.

10. The apparatus as claimed in claim 9, characterized in that, The access module is specifically used for: If the load pressure of the application instance is less than or equal to the lower limit of the first threshold, and N is greater than or equal to the upper limit of the second threshold, then the second replica application instance among the N replica application instances is removed from the application access correspondence table, and the second replica application instance is added to the list of replicas to be deleted. The second replica application instance is the replica application instance with the lowest load pressure.

11. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, when executing a computer program stored in the memory, implements the method steps of any one of claims 1-5.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the method steps of any one of claims 1-5.

Images