WO2020063206A1

WO2020063206A1 - Flexible scaling method for microservice instances, device, and storage medium

Info

Publication number: WO2020063206A1
Application number: PCT/CN2019/101856
Authority: WO
Inventors: 王洪玲
Original assignee: 南京中兴软件有限责任公司
Priority date: 2018-09-28
Filing date: 2019-08-21
Publication date: 2020-04-02
Also published as: CN110971623A; CN110971623B

Abstract

Disclosed in the embodiments of the present application are a flexible scaling method for microservice instances, a device, and a computer-readable storage medium, the method comprising: acquiring an idle-resource state in total resources, the number of microservice instances required by each service in a plurality of services, the number of microservice instances allocated to each service, and the maximum number of microservice instances able to be allocated to each service; calculating the number of microservice instances needing to be added to or removed from each service; and on the basis of the number of the number of microservice instances needing to be added to or removed from each service, adjusting the number of microservice instances of each service.

Description

Microservice instance elastic scaling method, device and storage medium

cross reference

The present invention claims the priority of a Chinese patent application filed on September 28, 2018 with the Chinese Patent Office, with the application number 201811136091.6, and the invention name is "Microservice instance elastic scaling method, device and storage medium", the entire content of the application Incorporated by reference in the present invention.

Technical field

Embodiments of the present application relate to the field of communications technologies, and in particular, to a method and apparatus for elastically scaling a microservice instance, and a computer-readable storage medium.

Background technique

According to business needs and policies, the network management system can automatically calculate its flexible resource management services, seamlessly add microservice instances when business demand peaks increase, and automatically reduce microservice instances to reduce costs when business demand decreases, that is, The need for systems to be able to scale microservice instances elastically has become a common requirement for current big data applications.

In traditional open source frameworks or systems, the elastic scaling of resources is based on the remaining resources (CPU and memory) or how much the load exceeds the preset number and the amount to be reduced. This elastic scaling method cannot gradually meet the detailed requirements for the shrinking strategy in multi-service interconnected applications, which are mainly reflected in:

First, in the case of multiple services, each service is required to maintain the prescribed processing capacity. Second, in the case of multiple services, if certain services are temporarily unavailable, the services that have been opened can use the system's free resources to serve them as much as possible; Furthermore, when there is a business burst, the preset number of shrinking instances is not enough to support the current business, resulting in a bottleneck. Finally, in the case of multiple services, if the previously unopened service is opened once, the newly opened service needs to be able to obtain its regulations. The resources needed to serve it.

Summary of the Invention

In view of this, the purpose of the embodiments of the present application is to provide a microservice instance elastic scaling method, device, and computer-readable storage medium to solve the problem that the existing elastic scaling methods cannot meet the requirements of multi-service interconnected applications.

The technical solutions adopted by the embodiments of the present application to solve the above technical problems are as follows:

According to an aspect of the embodiments of the present application, there is provided a microservice instance elastic scaling method, the method includes:

Obtaining the status of idle resources in the total resources, the number of microservice instances required by each service in multiple services, the number of microservice instances allocated to each service, and the maximum number of microservice instances that can be allocated to each service ; According to the idle resource status in the total resources, the number of micro service instances required by each service, the number of micro service instances allocated to each service, and the maximum micro service that can be allocated to each service The number of instances calculates the number of micro service instances that each business needs to increase or decrease; and adjusts the number of micro service instances of each business according to the number of micro service instances that each business needs to increase or decrease.

According to another aspect of the embodiments of the present application, a microservice instance elastic scaling device is provided, the device includes a memory, a processor, and a microservice instance elasticity stored in the memory and operable on the processor. A scaling program, where the microservice instance elastic scaling program is executed by the processor to implement the steps of the above microservice instance elastic scaling method.

According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores a microservice instance elastic scaling program, and the microservice instance elastic scaling program is executed by a processor. Steps for implementing the elastic service scaling method of the micro service instance described above.

According to another aspect of the embodiments of the present application, a computer program product is provided. The computer program product includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer is caused to execute the method described in each of the above aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

1 is a schematic flowchart of a microservice instance elastic scaling method according to a first embodiment of the present application;

2 is a schematic structural diagram of an elastic scaling component of a microservice instance according to an embodiment of the present application;

3 is a schematic diagram of an elastic scaling structure of a microservice instance according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a microservice example elastic scaling device according to a second embodiment of the present application.

The implementation, functional features and advantages of the purpose of this application will be further described with reference to the embodiments and the drawings.

detailed description

In order to make the technical problems, technical solutions, and beneficial effects to be more clearly understood in the present application, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

First embodiment

As shown in FIG. 1, a first embodiment of the present application provides a method for elastically scaling a microservice instance. The method includes:

Step S11: Obtaining the status of the idle resources in the total resources, the number of micro service instances required by each service in the multiple services, the number of micro service instances allocated to each service, and the maximum number of micro services that can be allocated to each service The number of service instances.

In an implementation manner, the state of obtaining idle resources in the total resources, the number of micro service instances required by each service in multiple services, the number of micro service instances allocated to each service, and the number of micro service instances that can be allocated to the services The maximum number of microservice instances per business, previously also included:

Obtaining the total resources, the number of tasks of each service, the time required for a single task, the shrinking model formula of the number of tasks of each service, and the resource quota ratio of each service; according to the tasks of each service Number, the time required for the single task, and the shrinking model formula for the number of tasks for each service to calculate the number of microservice instances required for each service; based on the total resources and the resource quota for each service Ratio, calculating the maximum number of microservice instances that can be allocated to each business.

In this implementation manner, the number of tasks of each service should be less than the maximum number of tasks allowed to be processed by the service; otherwise, the user should appropriately prompt or reject the new task when receiving a new task.

The single task time consuming is the actual time consuming task processing of each business. The initial experience value can be obtained through testing and experience, and the operation period can be dynamically adjusted according to the actual task execution status of each business.

The shrinking model formulas for different tasks are different for different businesses, and the formulas can be determined based on different business characteristics.

The resource quota ratio of each service is a weight ratio of each service to resource usage determined by comprehensively considering service characteristics (for example, periodic length (hour / day), random on-demand, business importance, etc.). The default value of the quota ratio can be determined by experience and test data. During operation, adaptive adjustments are made according to business characteristics to achieve efficient use of resources.

As an example, suppose that the total resources are represented by MAX; the number of tasks for each service is represented by TaskNum (En), where En represents the business En and n is a positive integer; Vone_task represents the single task time consuming; FUNC_INS (En) represents each service The number of tasks shrinks the model formula; FUNC_RES (En) indicates the resource quota ratio of each service; ToAlloc_InstanceNum (En) indicates the number of microservice instances required by each service; MAX_InstanceNum (En) indicates that it can be allocated to the service Maximum number of microservice instances per business.

Then the number of micro service instances ToAlloc_InstanceNum (En) required for each business is calculated by the following formula:

ToAlloc_InstanceNum (En) = V_NumOfTotalTask / (V_X / Vone_task).

The maximum number of microservice instances that can be allocated to each business is calculated by the following formula:

MAX_InstanceNum (En) = MAX * FUNC_RES (En).

In an implementation manner, the obtaining total resources, the number of tasks per service, the time required for a single task, the shrinking model formula of the number of tasks per service, and the resource quota ratio of each service , Before also including:

Recording the number of tasks and time information of each business; obtaining a new single task time according to the recorded number of tasks and time information of each business; in the new single task time and the single task time When the change rate of time exceeds a preset value, adjusting the time consumption of the single task.

In this implementation manner, the obtaining a new single task is time-consuming based on the recorded task number and time information of each service, and then further includes:

In a case where the time consumption of the new single task decreases compared with the default time consumption of the single task continuously over a preset time, the resource quota ratio of each service is adjusted.

As an example, when the number of service microservice instances needs to be adjusted, the timing detection function can be turned on; the number of tasks of each service and the current time are recorded; the number of tasks of each service and the current time are recorded in the next monitoring cycle; and then according to Record the number of tasks and time information of each business to obtain a new single task time; if the change (up) of the new single task time from the current single task time exceeds 20% but is less than the maximum permitted time, adjust the current If the change (up) of the new single task time from the current single task time exceeds 20% and is greater than the maximum permitted time, then adjust the current single task time to the maximum permitted time; if Compared with the default single task time consumption, the new single task time consumption has dropped for more than half a year, so adjust the resource quota ratio of each service.

In an implementation manner, the micro service instance required by each service is calculated according to the number of tasks of each service, the time consumption of the single task, and the shrinking model formula of the number of tasks of each service. Number, followed by:

Calculate the total number of micro service instances required by all services; and if the total number of micro service instances required by all services is less than the total resources, allocate the calculated number of micro service instances required by each service to each service for use; When the total number of micro service instances required by all services is greater than the total resources, the number of micro service instances is allocated to each service according to the service priority and its resource preemption rules.

In this implementation manner, the allocation of the number of microservice instances for each service according to the service priority and its resource preemption rules includes, but is not limited to, the following situations:

When ensuring that the low-priority task itself retains the lowest number of microservice instances, ensure that high-priority services can enjoy more microservice instances, that is, the maximum number of microservice instances that preferentially guarantee high-priority services; The number of microservice instances cannot guarantee that the total time consumption meets the business requirements. The priority is to ensure the lowest number of microservice instances for the low-priority business in the direction of low priority, and then recursively ensure that the number of microservice instances for the low-priority business is equal to or higher. The minimum number of microservice instances; if all services have been allocated according to the minimum number of microservice instances, the total time consumption of each business still does not meet the business requirements, it is prompted that an appropriate number of microservice instances cannot be given.

In this embodiment, the allocating the number of microservice instances to each service according to the service priority and its resource preemption rules further includes:

Determining the service priority and its resource preemption rule.

As an example, the resource preemption rule may be: whether high-priority services occupy all or part of the resources of low-priority services during a business storm, and whether low-priority services should retain the minimum number of microservice instances.

Step S12: according to the idle resource status in the total resources, the number of microservice instances required by each service, the number of microservice instances allocated to each service, and the maximum number of microservice instances that can be allocated to each service The number of micro service instances is to calculate the number of micro service instances that each business needs to increase or decrease.

In this embodiment, the number of micro service instances required for each service, the number of micro service instances allocated to each service, and the number of micro service instances allocated to each service according to the status of idle resources in the total resources, The maximum number of micro service instances for each business, and calculating the number of micro service instances that each business needs to increase or decrease, including:

The number of micro service instances required in each service is greater than the number of micro service instances allocated to each service, and the number of micro service instances allocated to each service is equal to the maximum number of micro services that can be allocated to each service In the case of the number of service instances and total resources and free resources, the number of microservice instances required for each service is the number of microservice instances required for each service and the microservices allocated to each service The difference in the number of instances.

As an example, it is assumed that ToAlloc_InstanceNum (En) represents the number of micro service instances required by each service; Current_InstanceNum (En) represents the number of micro service instances allocated to each service; MAX_InstanceNum (En) represents that it can be allocated to the services Maximum number of microservice instances per business.

When ToAlloc_InstanceNum (En)> Current_InstanceNum (En), Current_InstanceNum (En) = MAX_InstanceNum (En), and the total resources still have free resources, the number of microservice instances required for each service is: (ToAlloc_InstanceNum (En)- Current_InstanceNum (En)).

The number of micro service instances required in each service is greater than the number of micro service instances allocated to each service, and the number of micro service instances allocated to each service is equal to the maximum number of micro services that can be allocated to each service In the case where the number of service instances and total resources have no idle resources, the number of micro service instances that each business needs to increase or decrease is zero; in this case, the number of micro service instances for each business remains as allocatable The maximum number of micro service instances for each service is guaranteed at this time.

In a case where the number of micro service instances required by each service is less than the number of micro service instances allocated to each service, the number of micro service instances required to be reduced by each service is the number of micro service instances allocated to each service The difference between the number of microservice instances and the number of microservice instances required for each business; in this case, there is no need to pop up a new microservice instance; instead, the number of microservice instances that complete the task needs to be reduced.

As an example, it is assumed that ToAlloc_InstanceNum (En) represents the number of microservice instances required by each service; Current_InstanceNum (En) represents the number of microservice instances allocated to each service. When ToAlloc_InstanceNum (En) <Current_InstanceNum (En), you need to reduce the number of microservice instances that complete the task to ToAlloc_InstanceNum (En).

The number of micro service instances required for each service is greater than the number of micro service instances allocated to each service, and the number of micro service instances required for each service is less than or equal to the maximum number of micro services that can be allocated to each service In the case of the number of service instances, and the total resources have no free resources, the number of micro service instances required for each service is the number of micro service instances allocated to another service and the maximum micro service that can be allocated to the other service The difference in the number of instances.

As an example, it is assumed that ToAlloc_InstanceNum (En) represents the number of micro service instances required by each service; Current_InstanceNum (En) represents the number of micro service instances allocated to each service; MAX_InstanceNum (En) represents that it can be allocated to the services The maximum number of microservice instances for each business; Current_InstanceNum (Em) represents the number of microservice instances allocated to another business; MAX_InstanceNum (Em) represents the difference between the maximum number of microservice instances that can be allocated to the other business.

When ToAlloc_InstanceNum (En) <= MAX_InstanceNum (En), ToAlloc_InstanceNum (En)> Current_InstanceNum (En), and the total resources have no idle resources, the number of microservice instances that need to be increased for each service is: Current_InstanceNum (Em) -MAX_InstanceNum (Em).

Step S13: Adjust the number of microservice instances of each service according to the number of microservice instances required to be increased or decreased for each service.

In an embodiment, the adjusting the number of micro service instances of each service according to the increase or reduction of the number of micro service instances required by each service further includes:

The number of micro service instances required to be added to each service is marked with the identifier of each service; or the number of micro service instances required to be reduced for each service is removed from the identifier of each service.

As an example, the number of micro service instances required for business En must be marked with En. The microservice instance marked with the En logo is then executed based on the task of obtaining only the business En, and once the microservice instance is assigned to other services (such as Em), the microservice instance needs to remove the En logo and be marked with the service Em Logo.

In order to better explain the microservice instance elastic scaling process, the following is described in conjunction with Figure 2, Figure 3, and application scenarios: (where Figure 2 is a schematic diagram of the microservice instance elastic scaling component structure, which includes model management, resource management, and business tasks Pool; Figure 3 is a schematic diagram of an elastic scaling structure of a microservice instance, where business tasks include interference tasks and degradation detection tasks).

A company China Telecom's alarm northbound interface adopts a traditional elastic scaling strategy, which only quantifies elastic scaling based on a preset resource occupation. It often lags behind business processing requests, resulting in the accumulation of business processing tasks and causing the system processing capacity to deteriorate when needed. Occupies redundant resources.

The design CPU usage exceeds 80% and increases by 5 instances. It does not distinguish between services. The long-term operation causes accumulation of degradation detection tasks. The continuous increase leads to failure in applying for resources. However, the intelligent interference resource usage rate is below 80% for a long time. The released resources cannot be used immediately. For degradation detection.

Based on the problems of the traditional elastic scaling strategy, in one application scenario, the model management module sets two services: intelligent interference location (on demand), and degradation detection (cycle time).

Among them, the maximum resource that the service can allocate is MAX (En) = 100, and the resource quota ratio of the service is FUNC_RES (En) = 30: 70.

FUNC_INS (E1), the contraction model formula of the number of business tasks, for interference tasks:

100 tasks, each task has 3 seconds processing time, 25 instances are allocated, the actual 12 second processing time is less than 15 seconds; 100 tasks, each task is 2 seconds processing time, 17 instances are allocated, the actual 12 second processing time. That is, 100 instances of task assignment are required to be processed within 12 to 15 seconds. The actual time required for each task is obtained through monitoring data, and the cycle is adjusted on a daily basis. The formula is as follows:

ToAlloc_InstanceNum (En) = V_NumOfTotalTask / (V_12 / Vone_task).

The number of business tasks shrinks the model formula FUNC_INS (E2) for degradation detection tasks:

100 tasks, 2 seconds processing time per task, 20 instances allocated, actual 10 seconds processing time <12 seconds; 100 tasks, 1.5 seconds processing time per task, 15 instances allocated, actual 10.5 seconds processing time <12 second. That is, 100 instances of task assignment are required to be processed within 10 to 12 seconds. The actual time required for each task is obtained through monitoring data, and the cycle is adjusted on a daily basis. The formula is as follows:

ToAlloc_InstanceNum (En) = V_NumOfTotalTask / (V_10 / Vone_task).

The resource management module adjusts the number of service microservice instances according to the setting information. The adjusted information is shown in the following table:

It can be seen from the table that in the first to third monitoring cycles, when the total number of required instances is less than MAX (En), the actual number of instances allocated for each task is the same as the number of required instances. distribution. In the fourth monitoring cycle, the total number of required instances (38 + 80) is greater than MAX (En). Therefore, the priority is allocated according to the full allocation of the service's resource quota ratio. High-priority tasks can rob resources using low-priority tasks. (Example).

In another application scenario, the model management module sets two services: intelligent interference location (on demand), and degradation detection (cycle time). Among them, the maximum resource that the service can allocate is MAX (En) = 100, and the resource quota ratio of the service is FUNC_RES (En) = 40: 60.

The number of business tasks shrinks the model formula FUNC_INS (E1) for interference tasks: 100 tasks, 2.5 seconds processing time for each task, 20 instances are allocated, the actual processing time is 12.5 seconds; 100 tasks, 2 seconds processing time for each task , Allocate 16 instances, the actual 14 seconds processing time. That is, 100 instances of task assignment are required to be processed within 12 to 15 seconds. The actual time required for each task is obtained through monitoring data, and the cycle is adjusted on a daily basis. The formula is as follows:

ToAlloc_InstanceNum (En) = V_NumOfTotalTask / (V_12 / Vone_task).

The number of business tasks shrinks the model formula FUNC_INS (E2) for degradation detection tasks: 100 tasks, 2.5 seconds processing time per task, 25 instances allocated, actual 10 second processing time; 100 tasks, 2 seconds processing per task Time, 15 instances are allocated, and the actual processing time is 10.5 seconds. That is, 100 instances of task assignment are required to be processed within 10 to 12 seconds. The actual time required for each task is obtained through monitoring data, and the cycle is adjusted on a daily basis. The formula is as follows:

ToAlloc_InstanceNum (En) = V_NumOfTotalTask / (V_10 / Vone_task).

The method for elastically scaling microservice instances according to the embodiment of the present application, by dynamically adjusting the number of microservice instances of each service in multiple services, solves the problem that existing elastic scaling methods cannot meet the requirements of multi-service interconnected applications. ; In the case of ensuring that the processing capacity of the business is not affected by other businesses, ensure that the number of microservice instances of each business is under the best conditions; and improve resource utilization.

Second embodiment

As shown in FIG. 4, a second embodiment of the present application provides a microservice instance elastic scaling device. The device includes: a memory 21, a processor 22, and stored on the memory 21 and may be on the processor 22. The running microservice instance elastic scaling program, when the microservice instance elastic scaling program is executed by the processor 22, is used to implement the steps of the microservice instance elastic scaling method described below:

When the microservice instance elastic scaling program is executed by the processor 22, it is also used to implement the steps of the microservice instance elastic scaling method described below:

Determining the service priority and its resource preemption rule.

The number of micro service instances required in each service is greater than the number of micro service instances allocated to each service, and the number of micro service instances allocated to each service is equal to the maximum number of micro services that can be allocated to each service In the case of the number of service instances and total resources and free resources, the number of microservice instances required for each service is the number of microservice instances required for each service and the microservices allocated to each service The difference between the number of instances; the number of microservice instances required in each business is greater than the number of microservice instances allocated to each business, and the number of microservice instances allocated to each business is equal to the number of microservice instances that can be allocated to the In the case where the maximum number of microservice instances of each service and the total resources have no idle resources, the number of microservice instances required to be increased or decreased for each service is zero; the number of microservice instances required for each service is less than In the case of the number of micro service instances allocated to each service, the number of micro service instances to be reduced for each service is the number of micro service instances allocated to each service and the number of micro services instances allocated to each service. The difference between the number of required microservice instances; the number of microservice instances required in each business is greater than the number of microservice instances allocated to each business, and the number of microservice instances required in each business is less than or equal to In the case that the maximum number of micro service instances allocated to each service and the total resources have no free resources, the number of micro service instances required to be added for each service is the number of micro service instances allocated to another service and the number of allocable resources The difference between the maximum number of microservice instances for the other business.

The microservice instance elastic scaling device of the embodiment of the present application dynamically adjusts the number of microservice instances of each service in multiple services; and solves the problem that the existing elastic scaling method cannot meet the requirements of multi-service interconnected applications. ; In the case of ensuring that the processing capacity of the business is not affected by other businesses, ensure that the number of microservice instances of each business is under the best conditions; and improve resource utilization.

Third embodiment

A third embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a microservice instance elastic scaling program. The microservice instance elastic scaling program is used to implement a first service when executed by a processor. The steps of the microservice instance elastic scaling method described in the embodiment.

It should be noted that the computer-readable storage medium of this embodiment belongs to the same concept as the method of the first embodiment. The specific implementation process is described in detail in the method embodiment, and the technical features in the method embodiment are all in this embodiment. Correspondence applies, and is not repeated here.

The computer-readable storage medium of the embodiment of the present application dynamically adjusts the number of micro service instances of each service in multiple services; and solves the problem that the existing elastic scaling method cannot meet the requirements of multi-service interconnected applications; In the case that the processing capacity of the business is not affected by other businesses, the number of microservice instances of each business is under the optimal condition; the resource utilization rate is improved.

Fourth embodiment

The computer program product of the embodiment of the present application includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, The computer executes the method in any of the above method embodiments.

Those of ordinary skill in the art can understand that all or some of the steps, systems, and functional modules / units in the devices disclosed in the methods above can be implemented as software, firmware, hardware, and appropriate combinations thereof. In a hardware implementation, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical The components execute cooperatively. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit . Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile implemented in any method or technology used to store information such as computer-readable instructions, data structures, program modules or other data. Removable, removable and non-removable media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

The preferred embodiments of the present application have been described above with reference to the accompanying drawings, and thus do not limit the scope of rights of the present application. Any modification, equivalent replacement, and improvement made by those skilled in the art without departing from the scope and substance of this application shall fall within the scope of rights of this application.

Claims

A microservice instance elastic scaling method, the method includes:

Obtaining the status of idle resources in the total resources, the number of microservice instances required by each service in multiple services, the number of microservice instances allocated to each service, and the maximum number of microservice instances that can be allocated to each service ;

According to the idle resource status in the total resources, the number of micro service instances required by each service, the number of micro service instances allocated to each service, and the maximum micro service instance that can be allocated to each service Number, calculating the number of micro service instances that each business needs to increase or decrease;

Adjusting the number of micro service instances of each service according to the number of micro service instances required to be increased or decreased for each service.
The method according to claim 1, wherein said obtaining the free resource status in the total resources, the number of micro service instances required by each service in the plurality of services, the number of micro service instances allocated to each service, and the available The maximum number of micro service instances allocated to each service previously also includes:

Obtaining the total resources, the number of tasks of each service, the time required for a single task, the shrinking model formula of the number of tasks of each service, and the resource quota ratio of each service;

Calculating the number of microservice instances required by each service according to the number of tasks of each service, the time consumption of the single task, and the shrinking model formula of the number of tasks of each service;

Calculating the maximum number of microservice instances that can be allocated to each service according to the total resources and the resource quota ratio of each service.
The method according to claim 2, wherein the obtaining total resources, the number of tasks per business, the time required for a single task, the shrinking model formula of the number of tasks per business, and the each business The resource quota ratio, including:

Record the number of tasks and time information of each service;

Obtaining a new single task time consuming according to the recorded number of tasks and time information of each service;

When the rate of change between the new single task time and the single task time exceeds a preset value, adjust the single task time.
The method according to claim 3, wherein the obtaining a new single task is time-consuming based on the recorded number of tasks and time information of each service, and further comprising:

In a case where the time consumption of the new single task decreases compared with the default time consumption of the single task continuously over a preset time, the resource quota ratio of each service is adjusted.
The method according to claim 2, wherein the calculation of the needs of each service is based on a shrinking model formula of the number of tasks of each service, the time consumption of the single task, and the number of tasks of each service. Number of microservice instances, after which also includes:

Calculate the total number of microservice instances required for all business;

When the total number of micro service instances required by all services is less than the total resources, allocating the calculated number of micro service instances required by each service to each service for use;

When the total number of micro service instances required by all services is greater than the total resources, the number of micro service instances is allocated to each service according to the service priority and its resource preemption rules.
The method according to claim 5, wherein the distributing the number of microservice instances to each service according to the service priority and its resource preemption rules further comprises:

Determining the service priority and its resource preemption rule.
The method according to claim 1, wherein said according to a state of free resources in said total resources, the number of microservice instances required by said each service, the number of microservice instances allocated to said each service, and The maximum number of micro service instances that can be allocated to each service, and calculating the number of micro service instances that each service needs to increase or decrease includes:

The number of micro service instances required in each service is greater than the number of micro service instances allocated to each service, and the number of micro service instances allocated to each service is equal to the maximum number of micro services that can be allocated to each service In the case of the number of service instances and total resources and free resources, the number of microservice instances required for each service is the number of microservice instances required for each service and the microservices allocated to each service The difference in the number of instances;

The number of micro service instances required in each service is greater than the number of micro service instances allocated to each service, and the number of micro service instances allocated to each service is equal to the maximum number of micro services that can be allocated to each service In the case where the number of service instances and total resources have no idle resources, the number of micro service instances that each business needs to increase or decrease is zero;

In a case where the number of micro service instances required by each service is less than the number of micro service instances allocated to each service, the number of micro service instances required to be reduced by each service is the number of micro service instances allocated to each service A difference between the number of micro service instances and the number of micro service instances required by each service;

The number of micro service instances required for each service is greater than the number of micro service instances allocated to each service, and the number of micro service instances required for each service is less than or equal to the maximum number of micro services that can be allocated to each service In the case of the number of service instances, and the total resources have no free resources, the number of micro service instances required for each service is the number of micro service instances allocated to another service and the maximum micro service that can be allocated to the other service The difference in the number of instances.
The method according to claim 1, wherein the adjusting the number of microservice instances of each service according to the increase or decrease of the number of microservice instances required by each service further comprises:

The number of micro service instances required to be added to each service is marked with the identifier of each service; or the number of micro service instances required to be reduced for each service is removed from the identifier of each service.
A microservice instance elastic scaling device, wherein the device includes a memory, a processor, and a microservice instance elastic scaling program stored on the memory and operable on the processor, and the microservice instance elastically scales When the program is executed by the processor, the steps of the microservice instance elastic scaling method according to any one of claims 1 to 8 are implemented.
A computer-readable storage medium, wherein a microservice instance elastic scaling program is stored on the computer-readable storage medium, and the microservice instance elastic scaling program is implemented as claimed in claims 1 to 8 when executed by the processor. Steps of the microservice instance elastic scaling method according to any one.