Microapplication instance creation method and device, equipment, storage medium and program product

Abstract

The invention relates to the technical field of cloud computing, and provides a micro-application instance creation method, device and equipment, a storage medium and a program product, resource configuration can be directly carried out from the perspective of a service system without being carried out in a management object namespace of kubernets, and the method and the device can be well suitable for a two-layer management scene of the service system-micro-application. The method comprises the following steps: in response to an instance creation request of a micro-application in a service system, determining a resource quantity required to be used by an instance specified by an instance configuration file; obtaining a resource balance of the service system; and according to the relative size between the resource balance and the resource quantity, determining whether to create an instance of the micro-application.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of cloud computing, and in particular to a micro application instance creation method and device, computer equipment, a storage medium and a computer program product. BACKGROUND

[0002] In the technical field of cloud computing, kubernets (a kind of container scheduling engine cluster) can be used for users to create instances. When the user creates an instance, the resources used by the user's instance need to be limited; the original kubernets resource allocation is performed in the management object namespace of kubernets, which is difficult to apply in the two-layer management scenario of a business system-micro application. SUMMARY

[0003] Therefore, it is necessary to provide a micro application instance creation method and device, computer equipment, a storage medium and a computer program product to solve the above technical problems.

[0004] The present application provides a micro application instance creation method, which comprises:

[0005] In response to an instance creation request of a micro application in a business system, determining the amount of resources required by an instance specified by an instance configuration file;

[0006] Obtaining the resource balance of the business system;

[0007] According to the relative size between the resource balance and the resource amount, it is determined whether to create an instance of the micro application.

[0008] The present application provides a micro application instance creation device, which comprises:

[0009] An instance resource amount determination module is configured to determine the amount of resources required by an instance specified by an instance configuration file in response to an instance creation request of a micro application in a business system;

[0010] A resource balance acquisition module is configured to obtain the resource balance of the business system;

[0011] An instance creation processing module is configured to determine whether to create an instance of the micro application according to the relative size between the resource balance and the resource amount.

[0012] The present application provides a computer equipment comprising a memory and a processor, wherein the memory stores a computer program, and the processor executes the above method.

[0013] The present application provides a computer readable storage medium having a computer program stored thereon, wherein the computer program is executed by a processor to execute the above method.

[0014] This application provides a computer program product having a computer program stored thereon, the computer program being executed by a processor using the above-described method.

[0015] The aforementioned micro-application instance creation method, apparatus, computer device, storage medium, and computer program product, in response to a micro-application instance creation request in a business system, determine the amount of resources required by the instance specified in the instance configuration file; obtain the resource balance of the business system; and determine whether to create a micro-application instance based on the relative size between the resource balance and the resource quantity. The solution provided in this application allows for determining the resource balance of the business system from its perspective; in response to a micro-application instance creation request in the business system, it can determine the amount of resources required by the instance specified in the instance configuration file; and determine whether to create a micro-application instance based on the relative size between the resource balance and the resource quantity. Users can directly configure resources from the perspective of the business system without needing to do so within the Kubernetes management object namespace, making it well-suited for two-tier management scenarios such as business system-micro-application. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 A flowchart illustrating a method for creating an instance of a microapplication in one embodiment;

[0018] Figure 2 This is a schematic diagram of the resource request process in one embodiment;

[0019] Figure 3 This is a schematic diagram of the upgrade process in one embodiment;

[0020] Figure 4 A structural block diagram of an apparatus is created for an instance of a micro-application in one embodiment;

[0021] Figure 5 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0023] It should be noted that the terms "first", "second", etc. used in the present application can be used to describe various objects, but these objects are not limited by these terms. These terms are only used to distinguish the first object from the second object. The terms "include" and "have" and any variations thereof used in the present application are intended to cover non-exclusive inclusion. The term "a plurality of" used in the present application refers to two or more. The term "and / or" used in the present application refers to one of the options or any combination of multiple options.

[0024] The instance creation method of the micro application provided by the present application can be applied to the multi-live deployment platform, and the method can include Figure 1 The steps shown.

[0025] In step S101, in response to a micro application instance creation request in a business system, the resource amount required by the instance specified by the instance configuration file is determined.

[0026] The business system can be referred to as a product, and the business system can include several micro applications. The multi-live deployment platform can have a hierarchical relationship of business system-micro application-deployment record. The deployment record can be understood as an instance of the micro application. A user can issue an instance creation request for a micro application in a business system. After receiving the instance creation request, the multi-live deployment platform can determine the resource amount required by the instance specified by the instance configuration file. The resources can include but are not limited to CPU and memory, and the resource amount can be the required CPU quantity and memory quantity.

[0027] In step S102, the resource balance of the business system is obtained.

[0028] The multi-live deployment platform can obtain the current resource balance of the business system, such as the CPU quantity and the memory quantity.

[0029] In step S103, according to the relative size between the resource balance and the resource amount, it is determined whether to create an instance of the micro application.

[0030] The multi-live deployment platform can compare the relative size between the resource balance and the resource amount to determine whether the current resource balance of the business system supports instance creation. If it supports, the instance of the micro application can be created, and if it does not support, a corresponding prompt message can be issued.

[0031] In the scheme provided in the application, the resource balance of the business system can be determined from the perspective of the business system; in response to an instance creation request of a micro application in the business system, the resource amount required by an instance specified by an instance configuration file can be determined, and whether to create the instance of the micro application can be determined according to the relative size between the resource balance and the resource amount. The user can directly configure resources from the perspective of the business system without needing to perform the configuration in the management object namespace of kubernets, and the scheme can be well applied in a two-layer management scenario of a business system-micro application.

[0032] In one embodiment, whether to create the instance of the micro application is determined according to the relative size between the resource balance and the resource amount, including:

[0033] If the resource balance is greater than or equal to the resource amount, it is determined to create the instance of the micro application; if the resource balance is less than the resource amount, a prompt message of insufficient resources is sent.

[0034] The multi-active deployment platform can compare the relative size between the resource balance and the resource amount. If the resource balance is greater than or equal to the resource amount, it can be indicated that the current resource balance of the business system supports instance creation, and in this case, the instance of the micro application can be created; if the resource balance is less than the resource amount, it can be indicated that the current resource balance of the business system does not support instance creation, and in this case, a prompt message of insufficient resources can be sent.

[0035] In the embodiment, the instance of the micro application is created when the resource balance is greater than or equal to the resource amount, which can avoid system avalanche caused by excessive use of resources, and the prompt message of insufficient resources is sent when the resource balance is less than the resource amount, which can timely remind relevant personnel to handle.

[0036] In one embodiment, the resource balance of the business system is obtained, including:

[0037] The total amount of resources of the business system sent by the resource application platform is obtained; the created instances of each micro application under the business system are determined; and the resource balance of the business system is obtained according to the resource amount used by the created instances and the total amount of resources.

[0038] The resource application platform can be an entrance for resource application, and the resource application platform can be controlled by a process engine. The resource application process can include five stages of an application end-product manager end-paas product deployment end-paas product manager end-automatic expansion. As shown in the resource application process Figure 2 The resource application platform can record the approval process at each step, and information such as a resource use view can be provided in the approval at each step.

[0039] After a resource application is initiated for a business system and is audited through a resource application process, the resource application platform can obtain the total amount of resources of the business system. The resource application platform can send the total amount of resources of the business system to the multi-active deployment platform. The multi-active deployment platform can determine the created instances of each micro application under the business system, and thus can determine the amount of resources used by the created instances, such as 8 CPUs. If the total amount of resources of the business system is 10 CPUs, according to the total amount of resources and the amount of resources used by the created instances, the resource balance of the business system can be obtained as 2 CPUs.

[0040] In this embodiment, according to the created instances of each micro application under the business system and the total amount of resources, the more accurate resource balance of the business system can be obtained, and thus the subsequent instance creation judgment can be supported.

[0041] In one embodiment, after creating an instance of a micro application, the method provided by the present application further includes:

[0042] In response to an instance upgrade request, whether to upgrade the instance is determined according to whether the amount of resources required by the instance before upgrade is consistent with the amount of resources required after upgrade.

[0043] After creating an instance of a micro application, when a user upgrades the instance, the user can issue an instance upgrade request. The multi-active deployment platform can receive the instance upgrade request and determine whether the amount of resources required by the instance before upgrade is consistent with the amount of resources required after upgrade, so as to determine whether to upgrade the instance, and thus the intelligent upgrade decision, the accurate control of upgrade operation and the resource optimization can be realized.

[0044] In one embodiment, whether to upgrade the instance is determined according to whether the amount of resources required by the instance before upgrade is consistent with the amount of resources required after upgrade, including Figure 3 The steps shown are:

[0045] In step S301, if the amount of resources required by the instance before upgrade is consistent with the amount of resources required after upgrade, the instance is upgraded. In step S302, if the amount of resources required by the instance before upgrade is not consistent with the amount of resources required after upgrade, whether to upgrade the instance is determined according to whether the current resource balance of the business system supports the upgrade of the instance.

[0046] If the amount of resources required by the instance before upgrade is consistent with the amount of resources required after upgrade, it can be indicated that the amount of resources required by the instance before and after upgrade has not changed, and at this time the instance upgrade request can be released and the instance can be upgraded.

[0047] If the required resource amount of the instance before the upgrade is inconsistent with the required resource amount after the upgrade, it can be indicated that the required resource amount of the instance changes before and after the upgrade, and at this time, it can be further judged whether the current resource balance of the business system supports the upgrade of the instance, so as to determine whether to upgrade the instance, and a relatively intelligent upgrade decision can be realized.

[0048] In one embodiment, whether to upgrade the instance is determined according to whether the current resource balance of the business system supports the upgrade of the instance, including:

[0049] If the current resource balance of the business system supports the upgrade of the instance, the instance is upgraded; if the current resource balance of the business system does not support the upgrade of the instance, a prompt message of insufficient resources is sent.

[0050] Exemplarily, the current resource balance of a certain business system is 1 CPU; if the instance upgrade needs to add 1 CPU, it can be determined that the current resource balance of the business system supports the upgrade of the instance, and the instance can be upgraded; if the instance upgrade needs to add 2 CPUs, it can be determined that the current resource balance of the business system does not support the upgrade of the instance, and a prompt message of insufficient resources can be sent, so that relevant personnel can intervene in processing in time.

[0051] In order to better understand the above method, an application example of an instance creation method of a micro application of the present application is described in detail below. When deploying a container, the user needs to limit the resources used by the user's container, such as cpu and memory size. Container orchestration can be performed using kubernets, and kubernets has quota limits on the cpu and memory size of the namespace. Kubernets is a single cluster, and in the deployment mode of related technologies, in order to ensure that a single service can be highly available when a fault occurs, it is generally selected to be deployed in multiple isolated kubernets, at this time, the resource allocation of multiple clusters needs to be allocated one by one. In addition, due to the original rolling upgrade mechanism of kubernets, a new container needs to be started first, and then the old container is closed, which causes the need to allocate resources required for starting a new container when allocating resources; for example, the container upgrade needs to add 1 CPU, and during the upgrade, it needs to ensure that there are 2 CPUs to ensure that the new container is started normally, and then the old container is deleted, and after the upgrade process is completed, only 1 CPU resource is used. Moreover, the original kubernets resource allocation is performed in the management object namespace of kubernets, which does not conform to the two-layer management scenario of business system-micro application.

[0052] The application instance provides an application multi-cluster resource allocation scheme based on a serverless architecture, and relates to resource allocation, which can be combined with an application multi-live mode. By putting multiple kubernets into a resource pool, the resources of different isolated kubernets can be uniformly managed.

[0053] The resource allocation scheme related by the application instance can be independent of the original kubernets resource management scheme, and use a uniformly constructed resource application platform and a multi-live deployment platform (which can be referred to as an application multi-live platform) to apply for resources and schedule resources during application deployment.

[0054] The scheme provided by the application instance relates to a resource allocation method, which can be combined with an application multi-live deployment method, and can use a differential resource calculation method. If the resources do not change or the resources change by no more than the total quota allocated by the business system, the upgrade can be released.

[0055] The resource allocation of the application instance can be a system, that is, a certain business system has how many CPU and memory quotas. The calculation and control of the quotas can be completed on the resource application platform and the multi-live deployment platform, and can be regarded as a replacement for the original k8s (k8s is the abbreviation of kubernets) scheme.

[0056] The resource allocation scheme related by the application instance can use a three-layer design of business system-micro application-deployment record for users, and uniformly manage resources at the business system level.

[0057] The application instance relates to two platforms, one is a resource application platform, and the other is a multi-live deployment platform.

[0058] The resources of the application instance can include CPU and memory. The resources act on business systems, that is, a certain business system can use how much CPU and memory. These data can exist in the multi-live deployment platform.

[0059] The resource application platform can be an entrance for resource application. The resource application platform can be controlled by a process engine. The resource application process can include five stages of application end (that is, development / deployment)-product manager end-paas product deployment end-paas product manager end-automatic expansion. The resource application process is as shown in Figure 2 The resource application platform can record the approval process at each step, and can provide resource usage views and other information in the approval at each step.

[0060] The multi-active deployment platform can be used for the actual deployment action of the micro application. In the two-layer management scenario of the business system-micro application, the micro application belongs to a logical concept, and the micro applications in different environments can be configured differently. Therefore, the concept of business system-micro application-deployment record is introduced on the multi-active deployment platform. The deployment record can be understood as an instance of the micro application.

[0061] The resources applied for by the resource application platform can be set on the business system. When the multi-active deployment platform creates a deployment record (i.e., an instance), the configuration file of the deployment record needs to specify the cpu and memory required by the deployment record. The multi-active deployment platform can check whether the current resource balance of the business system can support the creation of the deployment record. If it can, the deployment record can be created. If it cannot, it can be prompted that the resources are insufficient.

[0062] When the deployment record (i.e., the instance) is upgraded, the multi-active deployment platform can detect whether the resource configuration requirements before and after the upgrade of the deployment record are consistent. If they are consistent, the upgrade action can be released. If they are not consistent, it can be calculated whether the current resource balance of the business system can support the creation of the deployment record. If it can, the deployment record can be created. If it cannot, it can be prompted that the resources are insufficient.

[0063] The deployment record can include a pair of workload templates and deployment strategies (which can be referred to as workload distribution strategies). The workload belongs to the concept of kubernets and is a management concept above a group of containers. The hierarchy can be understood as workload-pods-container, which is a 1:N:N relationship.

[0064] The Paas deployment end can be a device used by a deployment personnel of the paas team; the Paas product manager end can be a device used by a product manager of the paas team; and the product manager end can be a device used by a product manager corresponding to an application for expansion of the product.

[0065] In this embodiment, the deployment can be completed by a multi-active deployment platform. The multi-active deployment platform is associated with a resource pool and a one-time deployment. A resource pool includes kubernets of different isolation domains. Under a resource pool, a user only needs to pay attention to the resources applied and used by the corresponding business system, and does not need to log in to each kubernets to allocate resources in sequence. When the deployment record is upgraded, the multi-active deployment platform can detect whether the resource configuration requirements before and after the upgrade of the deployment record are consistent. If they are consistent, the upgrade action can be released. If they are inconsistent, it can be calculated whether the current resource balance of the business system can support the creation of the deployment record. If it can support, the deployment record can be created. If it cannot support, it can be prompted that the resources are insufficient. The calculation logic used in this embodiment can be independent of the scheduling rules of the original kubernets. For a user, the user only needs to pay attention to the business system-micro application-deployment record, and the user only needs to pay attention to whether the resources of the business system are sufficient in the use of resources, so as to meet the two-layer management scene of the business system-micro application and the user's cognitive logic, without introducing the concept of kubernets.

[0066] It should be understood that, although each step in the flowchart involved in each embodiment as described above is displayed in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other sequences. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence of these steps or stages is not necessarily sequential, but can be executed in rotation or alternation with at least part of other steps or steps or stages in other steps. It can be understood that the steps in different embodiments can be freely combined as needed, and various non-contradictory schemes formed by the combination all belong to the scope of protection of the present application.

[0067] Based on the same inventive concept, the embodiment of the present application also provides a micro application instance creation device for implementing the micro application instance creation method as described above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more micro application instance creation device embodiments provided below can refer to the limitations of the micro application instance creation method in the above text, which will not be described here.

[0068] In one embodiment, as shown in Figure 4 a micro application instance creation device is provided, comprising:

[0069] The example resource amount determining module 401 is configured to determine a resource amount required by an instance specified in an instance configuration file in response to an instance creation request of a micro application in a business system.

[0070] The resource balance obtaining module 402 is configured to obtain a resource balance of the business system.

[0071] The instance creation processing module 403 is configured to determine whether to create an instance of the micro application according to a relative size between the resource balance and the resource amount.

[0072] In one embodiment, the instance creation processing module 403 is configured to:

[0073] If the resource balance is greater than or equal to the resource amount, it is determined to create the instance of the micro application; if the resource balance is less than the resource amount, a prompt message of insufficient resources is sent.

[0074] In one embodiment, the resource balance obtaining module 402 is configured to:

[0075] obtain a total amount of resources of the business system sent by a resource application platform; determine created instances of each of the micro applications under the business system; and obtain the resource balance of the business system according to a resource amount used by the created instances and the total amount of resources.

[0076] In one embodiment, the apparatus further comprises an upgrade processing module configured to:

[0077] In response to an instance upgrade request, determine whether to upgrade the instance according to whether a resource amount required by the instance before upgrade is consistent with a resource amount required by the instance after upgrade.

[0078] In one embodiment, the upgrade processing module is configured to:

[0079] If the resource amount required by the instance before upgrade is consistent with the resource amount required by the instance after upgrade, the instance is upgraded; if the resource amount required by the instance before upgrade is not consistent with the resource amount required by the instance after upgrade, it is determined whether to upgrade the instance according to whether the current resource balance of the business system supports the upgrade of the instance.

[0080] In one embodiment, the upgrade processing module is configured to:

[0081] If the current resource balance of the business system supports the upgrade of the instance, the instance is upgraded; if the current resource balance of the business system does not support the upgrade of the instance, a prompt message of insufficient resources is sent.

[0082] The modules in the instance creation apparatus of the micro application can be implemented by software, hardware, or a combination thereof. The modules can be embedded in or independent of a processor in a computer device in hardware form, or stored in a memory in the computer device in software form, so that the processor can call and execute the operations corresponding to the modules.

[0083] In an example embodiment, a computer device is provided, which can be a server. The computer device can be applied to a multi-active deployment platform. An internal structure diagram of the computer device can be as shown in Figure 5 The computer device includes a processor, a memory, an input / output interface (I / O), and a communication interface. The processor, the memory, and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for running the operating system and the computer program in the non-volatile storage medium. The database of the computer device is configured to store data related to the above method. The input / output interface of the computer device is configured to exchange information between the processor and external devices. The communication interface of the computer device is configured to communicate with external terminals through a network connection. The computer program is executed by the processor to implement a micro application instance creation method.

[0084] Those skilled in the art can understand that Figure 5 The structure shown in the above

[0085] In an example embodiment, a computer device is provided, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0086] In an example embodiment, a computer readable storage medium is provided, which stores a computer program. The computer program is executed by a processor to implement the steps in the above method embodiments.

[0087] In an example embodiment, a computer program product is provided, which stores a computer program. The computer program is executed by a processor to implement the steps in the above method embodiments.

[0088] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations.

[0089] It can be understood by those skilled in the art that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments of each method. In the embodiments provided in the present application, any reference to memory, database or other medium can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0090] Any technical features in the above embodiments can be combined, and for the sake of brevity, not all possible combinations are described above, however, any combination of these technical features is deemed to be within the scope of the present application.

[0091] The above embodiments only express several implementation manners of the present application, and the description is relatively specific and detailed, but it should not be understood as a limitation on the patent scope of the present application. It should be pointed out that, for ordinary skilled persons in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A method for creating instances of a micro-application, characterized in that, The method includes: In response to the instance creation request of a micro-application in the business system, determine the amount of resources required by the instance as specified in the instance configuration file; Obtain the resource balance of the business system; Based on the relative size between the resource balance and the resource quantity, determine whether to create an instance of the micro-application.

2. The method according to claim 1, characterized in that, Determining whether to create an instance of the micro-application based on the relative size between the resource balance and the resource quantity includes: If the resource balance is greater than or equal to the resource quantity, then it is determined that an instance of the micro-application will be created; If the resource balance is less than the resource quantity, a resource shortage warning message will be issued.

3. The method according to claim 1, characterized in that, Obtaining the resource balance of the business system includes: Obtain the total amount of resources for the business system sent by the resource application platform; Identify the created instances of each of the micro-applications under the aforementioned business system; The resource balance of the business system is obtained based on the amount of resources used by the created instance and the total amount of resources.

4. The method according to any one of claims 1 to 3, characterized in that, After creating an instance of the micro-application, the method further includes: In response to an instance upgrade request, determine whether to upgrade the instance based on whether the amount of resources required by the instance before the upgrade is the same as the amount of resources required after the upgrade.

5. The method according to claim 4, characterized in that, Determining whether to upgrade the instance based on whether the resource requirements of the instance before and after the upgrade are the same includes: If the amount of resources required by the instance before the upgrade is the same as the amount of resources required after the upgrade, then the instance is upgraded. If the amount of resources required by the instance before the upgrade is inconsistent with the amount of resources required after the upgrade, then it is determined whether to upgrade the instance based on whether the current resource balance of the business system supports the upgrade of the instance.

6. The method according to claim 5, characterized in that, Based on whether the current resource balance of the business system supports the upgrade of the instance, determine whether to upgrade the instance, including: If the current resource balance of the business system supports the upgrade of the instance, then the instance shall be upgraded; If the current resource balance of the business system does not support the upgrade of the instance, a resource shortage warning message will be issued.

7. A micro-application instance creation device, characterized in that, The device includes: The instance resource quantity determination module is used to determine the amount of resources required by the instance specified in the instance configuration file in response to the instance creation request of the micro-application in the business system. The resource balance acquisition module is used to acquire the resource balance of the business system; The instance creation processing module is used to determine whether to create an instance of the micro-application based on the relative size between the resource balance and the resource quantity.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images