Management method and system during running of online telescopic distributed application

Abstract

The invention relates to a management method during running of an online telescopic distributed application. The management method comprises the following steps: a control center monitors the transaction volume and the resource utilization condition during running of the application in real time; according to the change of the transaction volume, the control center issues an instruction to the base to dynamically adjust the number of the plug-in instances; the application establishes lease long connection with the runtime instance through an SDK (Software Development Kit), and the lease time is dynamically calculated by the control center according to the transaction volume and the resource utilization condition; the runtime instance provides a performance acquisition interface, the base periodically collects performance data of the runtime instance and reports the performance data to the control center, and the control center optimizes resource allocation according to the performance data, so that the maximum utilization efficiency of resources is realized, the running cost is reduced, and the elasticity and expandability of the system are enhanced.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a management method and system for online scalable distributed application runtime. Background Art

[0002] The distributed application runtime is a technical framework that supports the development, deployment, and operation of distributed applications. It aims to simplify the complexity of distributed systems and provides core functions required by distributed systems such as service discovery, load balancing, state management, and event-driven.

[0003] Currently, distributed application runtime technology is still in its developmental stages, with no unified standards or mature solutions yet. Representative existing technologies include the following:

[0004] Microsoft's Dapr (Distributed Application Runtime) is an open-source distributed application runtime that provides building blocks to simplify distributed application development. It coexists with applications through the sidecar model and provides features such as service invocation, state management, and messaging.

[0005] Ant Group's Layotto is an open-source distributed application runtime developed by Ant Group, focusing on service mesh and microservices architecture. It provides service governance, configuration management, traffic control, and multi-language and multi-protocol support. The Dapr and Layotto runtimes consume system resources upon startup and continue to do so even when the system is idle. This static resource allocation method results in low resource utilization and is unable to adapt to dynamic changes in business load. Existing technologies lack the ability to dynamically adjust runtime instances, unable to automatically scale up or down instances based on transaction volume and resource utilization. This can lead to insufficient resources during peak periods and wasted resources during off-peak periods. Furthermore, most plugin management is static, with plugin instances loaded at startup and unable to dynamically adjust based on business needs. This limits the system's flexibility and scalability. Furthermore, regarding lease settings, existing technologies lack a dynamic management mechanism for connection resources. Persistent connections can lead to resource waste, while short connections can compromise transaction integrity. Summary of the Invention

[0006] To address the shortcomings of the existing technology, the present invention dynamically adjusts the runtime instance and lease connection time according to the transaction volume and resource utilization through the control center, thereby solving the defects of the existing technology in resource occupation, elastic scaling, plug-in management and connection resource management, and realizing efficient utilization and elastic scaling of system resources.

[0007] In a first aspect, the present invention provides a method for managing online scalable distributed applications at runtime, characterized by comprising:

[0008] The control center monitors the transaction volume and resource utilization of the application in real time; based on changes in transaction volume, the control center issues instructions to the base to dynamically adjust the number of plug-in instances;

[0009] The application establishes a long connection with a lease with the runtime instance through the SDK. The length of the lease is dynamically calculated by the control center based on transaction volume and resource utilization;

[0010] The runtime instance provides a performance collection interface, and the base regularly collects performance data of the runtime instance and reports it to the control center, which then optimizes resource allocation based on the performance data.

[0011] Exemplarily, the control center issues instructions to the base to dynamically adjust the number of plug-in instances, including: when the transaction volume is lower than a preset threshold, the control center issues a stop instruction to the base, and the base notifies the runtime instance to complete the requests within the current lease and then unload the excess plug-in instances to release resources; when the transaction volume is higher than the preset threshold, the control center issues a start instruction to the base, and the base issues an instruction to the runtime instance to load a new plug-in instance to handle the increase request.

[0012] Exemplarily, the control center issues an instruction to the base to dynamically adjust the number of plug-in instances, further comprising:

[0013] When an application requests to call the first plug-in, the base first checks whether the first plug-in has been loaded locally; if not, the base applies to the control center for the endpoint information of the first plug-in; the control center returns the optimal endpoint information and lease information of the first plug-in based on the transaction volume; the base establishes a connection with the target runtime instance based on the returned endpoint information.

[0014] Exemplarily, the communication among the control center, the base, the runtime instance, and the SDK supports cross-POD access to the runtime instance.

[0015] Exemplarily, the lease duration of the leased long connection is dynamically calculated by the control center based on the following factors: current transaction volume, resource utilization of runtime instances, and the number and distribution of application requests;

[0016] The performance data includes at least one of the following: number of transactions per second, number of successful transactions per second, transaction latency per second, and CPU and memory usage of the runtime instance.

[0017] Exemplarily, optimizing resource allocation according to performance data by the control center includes:

[0018] When it is detected that the resource utilization of the runtime instance is lower than a preset threshold, the control center issues an instruction to recycle the redundant runtime instance;

[0019] When it is detected that the resource utilization of the runtime instance is higher than a preset threshold, the control center issues an instruction to start a new runtime instance to share the load.

[0020] In a second aspect, the present application further provides an online elastic distributed application runtime management system, characterized by including:

[0021] The control center is used to monitor the transaction volume and resource utilization of the application in real time during runtime, and dynamically adjust the number of runtime instances based on changes in transaction volume;

[0022] The base is used to dynamically adjust the number of runtime instances according to the control center's instructions and regularly collect performance data of runtime instances and report it to the control center;

[0023] Specifically, the base is the manager of the runtime instance, responsible for loading or unloading plug-in instances on demand, and regularly collecting performance data of the runtime instance and reporting it to the control center.

[0024] Runtime instance, used to process application requests and provide performance collection interface;

[0025] Specifically, the runtime instance is the core component for processing application requests. It is responsible for loading plug-in instances, processing business requests, and providing performance data through the performance collection interface.

[0026] SDK, used to interact with applications and establish a persistent connection with the runtime instance with a lease. The lease length is dynamically calculated by the control center.

[0027] Specifically, the SDK is a bridge between the application and the runtime instance. It is responsible for forwarding the application's business requests to the runtime instance and managing the leased long connection with the runtime instance.

[0028] The communication module is used to realize data transmission and command issuance between the control center, base, runtime instance and SDK.

[0029] Specifically, the communication module is responsible for transmitting data (such as performance data, plug-in endpoint information, lease information, etc.) between the control center, the base, the runtime instance, and the SDK. It is also responsible for sending instructions from the control center (such as starting / stopping the runtime instance, loading / unloading the plug-in instance, etc.) to the base and runtime instance. The specific flow of communication data can be divided into the following situations:

[0030] The control center generates instructions for starting / stopping runtime instances and sends them to the base via the communication module;

[0031] After receiving the instruction, the base sends the instruction of loading / unloading the plug-in instance to the runtime instance through the communication module;

[0032] During runtime, the instance reports performance data to the base via the communication module;

[0033] The base reports the collected performance data to the control center through the communication module;

[0034] The SDK forwards the application request to the runtime instance through the communication module;

[0035] The runtime instance returns the processing results to the SDK through the communication module.

[0036] The functions of each module of the above system are also applicable to an online elastic distributed application runtime management method of the present application.

[0037] Exemplarily, the communication module supports cross-POD access to the runtime instance.

[0038] In a third aspect, the present invention further provides a computer-readable storage medium, characterized in that a computer program is stored on the storage medium, and when the computer program is executed by a processor, it implements the method according to any one of claims 1 to 6.

[0039] The present invention also provides an electronic device, characterized in that it includes a processor and a memory;

[0040] The memory is used to store computer programs;

[0041] The processor is configured to execute the method according to any one of claims 1 to 6 by calling a stored computer program.

[0042] The present invention also relates to a computer program product, comprising a computer program and / or instructions, characterized in that the computer program and / or instructions implement the steps of the above method when executed by a processor.

[0043] The beneficial effects of the present invention are: the present application can automatically release the distributed runtime instance during idle trading hours and restore the distributed runtime instance during normal trading hours, thereby achieving maximum resource utilization efficiency, reducing operating costs, enhancing the elasticity and scalability of the system, improving the flexibility of plug-in management, optimizing the utilization efficiency of connection resources, and improving the high availability and fault tolerance of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 This is a flow chart of a runtime management method for online elastic distributed applications according to the present invention.

[0045] Figure 2 This is a structural diagram of an online elastic distributed application runtime management system of the present invention. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0047] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are used only to distinguish the description and should not be understood as indicating or implying relative importance.

[0048] First, as Figure 1 As shown, the present invention provides a method for managing online scalable distributed applications at runtime, which is characterized by comprising:

[0049] The control center monitors the transaction volume and resource utilization of the application in real time; based on changes in transaction volume, the control center issues instructions to the base to dynamically adjust the number of plug-in instances;

[0050] The application establishes a long connection with a lease with the runtime instance through the SDK. The length of the lease is dynamically calculated by the control center based on transaction volume and resource utilization;

[0051] The runtime instance provides a performance collection interface, and the base regularly collects performance data of the runtime instance and reports it to the control center, which then optimizes resource allocation based on the performance data.

[0052] Specifically, the control center selects the optimal plugin endpoint information based on current transaction volume and resource utilization and returns it to the pedestal. This optimal plugin endpoint information typically refers to a runtime instance with low resource utilization and load balancing. The plugin endpoint information returned by the control center can be a runtime instance on another pod. The pedestal establishes a connection to the target runtime instance based on the returned endpoint information, while also supporting cross-pod access.

[0053] When application requests increase, the control center issues a decision instruction, and the base needs to load the plug-in instance. The specific steps include:

[0054] The base first checks whether the required plug-in instance has been loaded locally; if it has, the base directly uses the local plug-in instance to process the request; if not, the base proceeds to the next step.

[0055] The base sends a request to the control center to apply for the endpoint information of the required plug-in; the control center selects the optimal plug-in endpoint information based on the current transaction volume and resource utilization.

[0056] The control center returns the optimal plug-in endpoint information (including IP address, port number, etc.) and lease information (lease duration).

[0057] Based on the returned plug-in endpoint information, the base establishes a leased persistent connection with the target runtime instance. Through this connection, the base forwards the application request to the target runtime instance. The target runtime instance loads and calls the corresponding plug-in instance to process the request. After processing is complete, the target runtime instance returns the result to the base, which then returns the result to the application.

[0058] The communication of this application can also adopt the standard protocol of TCP, which can ensure the reliability and efficiency of data transmission between components, while ensuring the dynamic adjustment capability of the overall system and ensuring the efficient utilization and elastic scalability of system resources.

[0059] Through the control center, this application realizes real-time monitoring, dynamic adjustment and optimal allocation of resources, ensuring the efficient, flexible and low-cost operation of the system.

[0060] Through the setting of the base, this application realizes runtime instance management, plug-in instance loading and unloading, performance data collection and reporting, and communication intermediary functions, ensuring the efficient, flexible and low-cost operation of the system

[0061] Through the SDK settings, this application realizes efficient communication and dynamic connection management between the application and the runtime instance, ensuring the efficient operation of the system and user experience.

[0062] Through runtime instances, this application implements real-time processing of application requests, plug-in instance management, and performance data collection, ensuring efficient operation and resource optimization of the system.

[0063] Second, as Figure 2 As shown, the present application provides an online elastic distributed application runtime management system, characterized by including:

[0064] The control center is used to monitor the transaction volume and resource utilization of the application in real time during runtime, and dynamically adjust the number of runtime instances based on changes in transaction volume;

[0065] The base is used to dynamically adjust the number of runtime instances according to the control center's instructions and regularly collect performance data of runtime instances and report it to the control center;

[0066] Runtime instance, used to process application requests and provide performance collection interface;

[0067] SDK, used to interact with applications and establish a persistent connection with the runtime instance with a lease. The lease length is dynamically calculated by the control center.

[0068] The communication module is used to realize data transmission and command issuance between the control center, base, runtime instance and SDK.

[0069] Exemplarily, the communication module supports cross-POD access to the runtime instance.

[0070] Specifically, the communication module can be used

[0071] For example, Figure 2 As shown, the control center includes:

[0072] Monitoring module, used to collect transaction volume and resource utilization in real time;

[0073] The decision module is used to dynamically calculate the number of runtime instances and the lease duration based on monitoring data;

[0074] The instruction issuing module is used to issue instructions to the base to start or stop the runtime instance.

[0075] Exemplarily, the base includes:

[0076] Plugin management module, used to load or unload plugin instances on demand;

[0077] Performance collection module, used to regularly collect performance data of runtime instances and report it to the control center;

[0078] The communication agent module is used to communicate with the control center and runtime instances.

[0079] Exemplarily, the runtime instance includes:

[0080] Request processing module, used to process application requests;

[0081] Performance collection interface, used to provide performance data;

[0082] The resource release module is used to complete the requests within the current lease and release resources after receiving the stop instruction.

[0083] Exemplarily, the SDK includes:

[0084] The connection management module is used to establish a leased persistent connection with the runtime instance;

[0085] The lease renewal module is used to dynamically adjust the lease duration according to the instructions of the control center;

[0086] The request forwarding module is used to forward application requests to the target runtime instance.

[0087] The specific application embodiment includes the following implementation steps:

[0088] Step 1: After the control center starts, it initializes information for each module, including the monitoring module, decision-making module, and command issuance module. The control center establishes communication with all pedestals and obtains initial runtime and plug-in instance information. After the pedestals start, they load the initial runtime and plug-in instances. The pedestals register with the control center and begin regularly reporting runtime instance performance data. Specific performance data includes at least the number of transactions per second, the number of successful transactions per second, CPU utilization, and transaction latency per second.

[0089] Step 2: During a low trading period, the control center monitors extremely low transaction volume (e.g., fewer than 10 transactions per second) and low runtime instance resource utilization (e.g., CPU utilization less than 20%). Based on this monitoring data, the control center's decision module determines whether some runtime instances can be reclaimed to free up resources. The decision module selects some runtime instances (e.g., instance A and instance B) as targets for reclaiming.

[0090] The control center, through the command delivery module, issues a stop command to the base, requesting the selected runtime instance to stop. Upon receiving the command, the base notifies the selected runtime instance to complete requests within the current lease. After completing the requests, the runtime instance releases resources and stops running. The control center confirms the selected runtime instance has stopped and updates the resource allocation status. System resources are released, and the system enters a low-power state.

[0091] Step 3: The transaction volume increases. The control center monitors that the current transaction volume begins to increase (for example, the number of transactions per second reaches 50), and the resource utilization of the remaining runtime instances gradually increases (for example, the CPU usage reaches 50%).

[0092] Decision to launch a new instance: Based on monitoring data, the control center's decision module determines the need to launch a new runtime instance to share the load. The decision module selects a pedestal (for example, pedestal X) as the target for launch. The control center, through the command delivery module, issues a launch command to pedestal X, requesting the launch of the new runtime instance.

[0093] After receiving the instruction, base X starts a new runtime instance (such as instance C) and loads the required plug-in instance.

[0094] Base X registers the new runtime instance with the control center and begins reporting its performance data. The new runtime instance begins processing business requests and sharing the system load.

[0095] The control center monitors that system resource utilization is approaching equilibrium (e.g., CPU utilization has dropped to 40%). The control center monitors that current transaction volume has reached a peak (e.g., the number of transactions per second has reached 200), and the resource utilization of the runtime instance is high (e.g., CPU utilization has reached 80%).

[0096] Step 4: Dynamically adjust the lease. The control center monitors that certain runtime instances have a high number of connections (for example, the number of connections to instance C has reached the upper limit) and the lease is about to expire. The control center's decision module calculates the new lease duration (for example, from 5 minutes to 3 minutes) based on current transaction volume and resource utilization. The control center sends a lease renewal instruction to the relevant SDK through the instruction issuance module. After receiving the instruction, the SDK renews the connection lease with the runtime instance. At the end of the lease, the SDK actively releases the connection and reestablishes the connection according to the control center's instructions.

[0097] Step 5: Transaction volume decreases (resource recovery) The control center monitors that the current transaction volume begins to decrease (for example, the number of transactions per second drops to 100), and the resource utilization of some runtime instances is low (for example, the CPU usage is less than 30%).

[0098] Based on monitoring data, the control center's decision module calculates that some runtime instances can be reclaimed to free up resources. The decision module selects some runtime instances (such as instance D and instance E) as targets for reclaim. The control center, through its instruction delivery module, issues a stop command to pedestals Y and Z, requesting the termination of the selected runtime instances. Upon receiving the command, pedestals Y and Z notify the selected runtime instances to complete requests within the current lease. After completing the requests, the runtime instances release resources and cease operation. The control center confirms the termination of the selected runtime instances, updates the resource allocation status, and system resources are released, entering a medium-load state.

[0099] By using this system, the above-mentioned processing method can be executed and the corresponding technical effects can be achieved.

[0100] An embodiment of the present invention also provides a computer-readable storage medium capable of implementing all steps of the method in the above embodiment. The computer-readable storage medium stores a computer program that implements all steps of the method in the above embodiment when executed by a processor.

[0101] An embodiment of the present invention also provides an electronic device for executing the above-mentioned method. As an implementation device of the method, the electronic device has at least a processor and a memory, and in particular, the memory stores the data and related computer programs required for executing the method, and the processor calls the data and programs in the memory to execute all the steps of the implementation method and obtains the corresponding technical effect.

[0102] Preferably, the electronic device may include a bus architecture, which may include any number of interconnected buses and bridges, and the bus will include various circuits linked together by one or more processors and memories. The bus may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface between the bus and the receiver and transmitter. The receiver and transmitter can be the same component, namely a transceiver, which provides a unit for communicating with various other systems over a transmission medium. The processor is responsible for managing the bus and general processing, while the memory can be used to store data used by the processor when performing operations.

[0103] Additionally, the electronic device may further include components such as a communication module, an input unit, an audio processor, a display, and a power supply. The processor (or controller, operating control) employed may include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of the electronic device. The memory may be one or more of a cache, flash memory, a hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices, and may store the aforementioned data and information. It may also store programs for executing the relevant information, and the processor may execute the programs stored in the memory to implement information storage or processing. The input unit is used to provide input to the processor, and may, for example, be a keypad or touch input device. The power supply is used to provide power to the electronic device. The display is used to display objects such as images and text, and may, for example, be an LCD display. The communication module is a transmitter / receiver that sends and receives signals via an antenna. The communication module (transmitter / receiver) is coupled to the processor to provide input signals and receive output signals, similar to the case of a conventional mobile communication terminal. Based on different communication technologies, multiple communication modules can be provided in the same electronic device, such as a cellular network module, a Bluetooth module, and / or a wireless local area network module. The communication module (transmitter / receiver) is also coupled to a speaker and a microphone via an audio processor to provide audio output via the speaker and receive audio input from the microphone, thereby implementing common telecommunications functions. The audio processor may include any suitable buffer, decoder, amplifier, etc. In addition, the audio processor is also coupled to a central processing unit, enabling local recording via the microphone and playback of stored audio via the speaker.

[0104] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0105] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce 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 flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A system that specifies the functions of a box or boxes.

[0106] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction system that is implemented in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0107] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The present invention is described in detail below. ...

[0108] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention are intended to be covered by the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for managing online scalable distributed applications at runtime, characterized in that: include: The control center monitors the transaction volume and resource utilization of the application in real time; based on changes in transaction volume, the control center issues instructions to the base to dynamically adjust the number of plug-in instances; The application establishes a long connection with a lease with the runtime instance through the SDK. The length of the lease is dynamically calculated by the control center based on transaction volume and resource utilization; The runtime instance provides a performance collection interface, and the base regularly collects performance data of the runtime instance and reports it to the control center, which then optimizes resource allocation based on the performance data.

2. The method according to claim 1, characterized in that The control center issues instructions to the base to dynamically adjust the number of plug-in instances, including: when the transaction volume is lower than a preset threshold, the control center issues a stop instruction to the base, and the base notifies the runtime instance to complete the requests within the current lease and then unload the excess plug-in instances to release resources; when the transaction volume is higher than the preset threshold, the control center issues a start instruction to the base, and the base issues an instruction to the runtime instance to load a new plug-in instance to handle the increase request.

3. The method according to claim 2, characterized in that The control center issues instructions to the base to dynamically adjust the number of plug-in instances, further comprising: When an application requests to call the first plug-in, the base first checks whether the first plug-in has been loaded locally; if not, the base applies to the control center for the endpoint information of the first plug-in; the control center returns the optimal endpoint information and lease information of the first plug-in based on the transaction volume; the base establishes a connection with the target runtime instance based on the returned endpoint information.

4. The method according to claim 1, wherein The communication between the control center, the base, the runtime instance and the SDK supports cross-POD access to the runtime instance.

5. The method according to claim 1, characterized in that: The lease duration of the leased long connection is dynamically calculated by the control center based on the following factors: current transaction volume, resource utilization of runtime instances, number and distribution of application requests; The performance data includes at least one of the following: number of transactions per second, number of successful transactions per second, transaction latency per second, and CPU and memory usage of the runtime instance.

6. The method according to claim 1, characterized in that The control center optimizing resource allocation according to the performance data includes: When it is detected that the resource utilization of the runtime instance is lower than a preset threshold, the control center issues an instruction to recycle the redundant runtime instance; When it is detected that the resource utilization of the runtime instance is higher than a preset threshold, the control center issues an instruction to start a new runtime instance to share the load.

7. An online elastic distributed application runtime management system, characterized in that: include: The control center is used to monitor the transaction volume and resource utilization of the application in real time during runtime, and dynamically adjust the number of runtime instances based on changes in transaction volume; The base is used to dynamically adjust the number of runtime instances according to the control center's instructions and regularly collect performance data of runtime instances and report it to the control center; Runtime instance, used to process application requests and provide performance collection interface; SDK, used to interact with applications and establish a persistent connection with the runtime instance with a lease. The lease length is dynamically calculated by the control center. The communication module is used to realize data transmission and command issuance between the control center, base, runtime instance and SDK.

8. The system according to claim 7, characterized in that The communication module supports cross-POD access to the runtime instance.

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

10. An electronic device, characterized in that: including processor and memory; The memory is used to store computer programs; The processor is configured to execute the method according to any one of claims 1 to 6 by calling a stored computer program.

11. A computer program product comprising a computer program and / or instructions, characterized in that When the computer program and / or instructions are executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images