Business system

Abstract

The invention discloses a business system, and the system comprises a first container which is used for providing a micro-service according to the current business processing capability of the first container; the container cluster management subsystem is used for detecting the current actual service operation condition of the first container in the process that the first container provides the micro-service, and when the service processing capacity required by the current actual service operation condition of the first container is not matched with the current service processing capacity of the first container, the first container provides the micro-service; and dynamically adjusting the business processing capability of the first container according to the current actual business operation condition of the first container, and redeploying the first container according to the adjusted business processing capability of the first container, so that the redeployed first container provides the micro-service according to the adjusted business processing capability. In this way, useless no-load overhead caused by increasing the number of instances can be avoided, and precious resources are fully utilized.

Description

Technical Field

[0001] The present application relates to the field of container technology, and in particular to a business system. Background Art

[0002] In real work, a business system consists of multiple microservices, which can be provided by multiple different types of containers. Different types of containers correspond to different processing capabilities. The same microservice may require one or more instances (that is, one or more containers of the same type are required to provide the same microservice) to complete. Especially when the business pressure is high, multiple microservice instances need to be popped up to increase processing capabilities. However, each container requires basic memory, CPU (Central Processing Unit) and other resource overheads. Therefore, in the case of no load, the operating system and the basic operating environment occupy at least memory, which will cause a certain waste of resources. Summary of the invention

[0003] Based on this, an embodiment of the present application provides a business system that can avoid useless idle overhead caused by increasing the number of instances and fully utilize valuable resources.

[0004] In a first aspect, the present application provides a business system, the business system comprising:

[0005] A first container is used to provide microservices according to the current business processing capability of the first container;

[0006] The container cluster management subsystem is used to detect the actual business operation status of the first container during the process of the first container providing the microservice. When the business processing capability required by the current actual business operation status of the first container does not match the current business processing capability of the first container, the business processing capability of the first container is dynamically adjusted according to the current actual business operation status of the first container. According to the adjusted business processing capability of the first container, the first container is redeployed so that the redeployed first container provides the microservice according to the adjusted business processing capability.

[0007] The embodiment of the present application provides a business system. During the process of the first container providing microservices according to its own current business processing capability, the container cluster management subsystem detects the actual business operation status of the first container. When the business processing capability required by the actual business operation status does not match the current business processing capability, the container cluster management subsystem dynamically adjusts the business processing capability of the first container and redeploys the first container. The redeployed first container provides microservices according to the adjusted business processing capability. In this way, the number of first containers does not need to be changed, and one first container can be maintained as much as possible, and only the business processing capability of the first container needs to be changed, that is, the number of microservice instances does not need to be changed, and one instance can be maintained as much as possible, and only the resource quota of the instance needs to be changed. This can avoid useless idle overhead caused by increasing the number of instances and make full use of valuable resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 It is a schematic diagram of an embodiment of the business system of the present application;

[0009] Figure 2 It is a schematic diagram of another embodiment of the business system of the present application;

[0010] Figure 3 It is a schematic diagram of the interaction between the container cluster management subsystem and the first container in an embodiment of the business system of the present application;

[0011] Figure 4 It is a comparative diagram of the business system of the embodiment of the present application and the traditional business system. DETAILED DESCRIPTION

[0012] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0013] The flowcharts shown in the accompanying drawings are only examples and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, combined or partially merged, so the actual execution order may change according to actual conditions.

[0014] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no special meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.

[0015] Before introducing the embodiments of the present application in detail, the technical contents related to the present application are first introduced.

[0016] Containers are a technology used to bundle applications with all their necessary files into a runtime environment. As a unit, containers can be easily moved and run on any operating system in any environment. Using containers, software can be isolated so that it can run independently in different operating systems, hardware, networks, storage systems, and security policies. This allows container-based applications to be seamlessly converted between development, test, and production environments. Since the operating system is not packaged into the container, each container only needs to use very few computing resources, not only takes up very little space, but is also easy to install. By using containers, users can avoid crashes caused by incompatible environments and can get consistent performance on different machines. Developers can focus on the application itself without having to distract themselves from debugging or rewriting it for different server environments. Since containers do not contain operating systems, developers can efficiently deploy containers in clusters, and each container can be responsible for retaining a single component of a complex application. By placing components in independent containers, developers can also update individual components without rewriting the entire application.

[0017] Applications in containers are isolated from the host and do not need to pay attention to the environment. The biggest difference between containers and virtual machines is that containers do not need to start the operating system cycle, so the start and stop of containers will be very fast; and containers can also use various resources of the host machine quite efficiently. Containers package all application languages ​​and frameworks into containers, allowing containers to be deployed in any environment.

[0018] A container cluster is a collection of cloud resources required for container operation. There are many management solutions for container clusters, and the current mainstream solutions include: Swarm, Kubenetes, Mesos, etc.

[0019] The following is an explanation of the technical problems existing in the related technologies. In real work, a business system consists of multiple microservices, and multiple microservices can be provided by multiple different types of containers. Different types of containers correspond to different processing capabilities. The same microservice may require one or more instances (that is, one or more containers of the same type are required to provide the same microservice) to complete. Especially when the business pressure is high, multiple microservice instances need to be popped up to increase processing power. However, each container requires basic memory, CPU (Central Processing Unit) and other resource overheads. Therefore, in the idle state, the operating system and the basic operating environment occupy at least memory, which will cause a certain amount of resource waste.

[0020] The embodiment of the present application provides a business system. During the process of the first container providing microservices according to its own current business processing capability, the container cluster management subsystem detects the actual business operation status of the first container. When the business processing capability required by the actual business operation status does not match the current business processing capability, the container cluster management subsystem dynamically adjusts the business processing capability of the first container and redeploys the first container. The redeployed first container provides microservices according to the adjusted business processing capability. In this way, the number of first containers does not need to be changed, and one first container can be maintained as much as possible, and only the business processing capability of the first container needs to be changed, that is, the number of microservice instances does not need to be changed, and one instance can be maintained as much as possible, and only the resource quota of the instance needs to be changed. This can avoid useless idle overhead caused by increasing the number of instances and make full use of valuable resources.

[0021] The embodiments of the present application are described in detail below.

[0022] See also Figure 1 , Figure 1 This is a schematic diagram of an embodiment of a business system of the present application, wherein the business system includes: a first container and a container cluster management subsystem. A business system is usually composed of multiple microservices, and multiple microservices can be provided by multiple different types of first containers. The first container is deployed by the container cluster management subsystem according to the preset requirements of the corresponding microservice, and after the deployment is completed, the first container can provide the corresponding microservice.

[0023] The first container is used to provide microservices according to the current business processing capability of the first container.

[0024] The container cluster management subsystem is used to detect the actual business operation status of the first container during the process of the first container providing the microservice. When the business processing capability required by the current actual business operation status of the first container does not match the current business processing capability of the first container, the business processing capability of the first container is dynamically adjusted according to the current actual business operation status of the first container. According to the adjusted business processing capability of the first container, the first container is redeployed so that the redeployed first container provides the microservice according to the adjusted business processing capability.

[0025] In the embodiment of the present application, the container cluster management subsystem is a management solution for the container cluster, including but not limited to: Swarm, Kubenetes, Mesos, etc. The first container may refer to a container that provides a certain microservice. A microservice is an application composed of many smaller, loosely coupled services, which coordinate and cooperate with each other to provide ultimate value to users; each service runs in its own independent process, and services communicate with each other using lightweight communication mechanisms; each service is built around a specific business and can be independently deployed to a production environment, a quasi-production environment, etc.

[0026] The first container requires basic memory, CPU and other resource overheads. The current business processing capability of the first container is the resources allocated to the first container by the container cluster management subsystem (including but not limited to hardware resources, software resources, etc.). The first container provides microservices based on the current business processing capability of the first container. The current actual business operation status of the first container may be the resource utilization status of the first container in the process of providing microservices, including but not limited to CPU utilization, memory occupancy, etc. The business processing capability required for the current actual business operation status of the first container may refer to the business processing capability when the resource utilization status of the first container matches its resources in the process of providing microservices.

[0027] During the process of the first container providing the microservice, the container cluster management subsystem detects the actual operation status of the current business of the first container. If the business processing capability required by the current actual operation status of the first container does not match the current business processing capability of the first container, there are generally two situations: the first situation is that the business processing capability required by the current actual operation status of the first container is greater than the current business processing capability of the first container; the second situation is that the business processing capability required by the current actual operation status of the first container is less than the current business processing capability of the first container.

[0028] For example, the actual operation status of the current business of the first container is: the CPU utilization is 60%, and / or the memory occupancy is 65%. When the CPU utilization is preset to be less than or equal to 85% and greater than or equal to 50%, and / or the memory occupancy is less than or equal to 85% and greater than or equal to 50%, it is considered that the resource utilization matches the resources. Obviously, the business processing capacity required by the actual operation status of the current business of the first container matches the current business processing capacity of the first container. If the CPU utilization is less than 50% or greater than 85%, and / or the memory occupancy is less than 50% or greater than 85%, it can be considered that the business processing capacity required by the current actual business operation of the first container is not matched with the current business processing capacity of the first container: if the CPU utilization is less than 50%, and / or the memory occupancy is less than 50%, it can be considered that the business processing capacity required by the current actual business operation of the first container is less than the current business processing capacity of the first container (nearly half of the resources are idle); if the CPU utilization is greater than 85%, and / or the memory occupancy is greater than 85%, it can be considered that the business processing capacity required by the current actual business operation of the first container is greater than the current business processing capacity of the first container (resources are almost fully occupied).

[0029] In some embodiments, the business processing capability includes hardware resources, and the hardware resources include at least a central processing unit CPU and memory.

[0030] In the related art, if the business processing capacity required by the actual operation of the current business of the container is greater than the current business processing capacity of the container, the container cluster management system usually adds microservice instances, that is, deploys new containers to achieve the purpose of increasing processing capacity. Since the actual operation of the current business of the container is dynamically changing, when the business processing capacity required by the actual operation of the current business of the container is less than the current business processing capacity of the container, or even when it is unloaded, the newly added container still occupies basic memory, CPU and other resource overheads, which will cause a certain waste of resources. If the business processing capacity required by the actual operation of the current business of the container is less than the current business processing capacity of the container, or even when it is unloaded, the container still occupies basic memory, CPU and other resource overheads, which will also cause a certain waste of resources, then the container is equivalent to being idle.

[0031] The container cluster management subsystem of the embodiment of the present application dynamically adjusts the business processing capability of the first container and redeploys the first container when the business processing capability required by the actual operation of the current business of the first container does not match the current business processing capability of the first container. The redeployed first container provides microservices according to the adjusted business processing capability. In this way, the number of first containers does not need to be changed, and one first container is maintained as much as possible, and only the business processing capability of the first container is changed, that is, the number of microservice instances does not need to be changed, and one instance is maintained as much as possible, and only the resource quota of the instance is changed. This can avoid useless idle overhead caused by increasing the number of instances and make full use of valuable resources.

[0032] In some embodiments, the container cluster management subsystem is also used to increase the business processing capacity of the first container when the business processing capacity required by the actual operation of the current business of the first container is greater than the current business processing capacity of the first container, and redeploy the first container according to the increased business processing capacity of the first container, so that the redeployed first container provides the microservice according to the increased business processing capacity.

[0033] In the embodiment of the present application, if the business processing capacity required by the actual operation of the current business of the first container is greater than the current business processing capacity of the first container, the business processing capacity of the first container is increased, and the first container is redeployed according to the increased business processing capacity, and the redeployed first container provides the microservice according to the increased business processing capacity. In this way, there is no need to increase the number of first containers, and one first container is kept as much as possible. Only the business processing capacity of the first container is increased, and the resource quota of the first container is increased, which can avoid the useless idle overhead caused by adding a new first container and make full use of precious resources.

[0034] In some embodiments, the container cluster management subsystem is further used to increase the business processing capacity of the first container when the business processing capacity required by the actual operation of the current business of the first container is greater than the current business processing capacity of the first container, and the current business processing capacity of the first container is less than the preset maximum business processing capacity of the first container.

[0035] In the embodiment of the present application, a preset maximum business processing capacity of the first container is preset. When the business processing capacity required by the actual operation of the current business of the first container is greater than the current business processing capacity of the first container, the business processing capacity of the first container can be increased only when the current business processing capacity of the first container is less than the preset maximum business processing capacity of the first container. In this way, other problems caused by excessive occupation of resources due to excessive increase in the business processing capacity of the first container can be avoided.

[0036] In some embodiments, the container cluster management subsystem is further used to reduce the business processing capacity of the first container when the business processing capacity required by the actual operation of the current business of the first container is less than the current business processing capacity of the first container, and redeploy the first container according to the reduced business processing capacity of the first container, so that the redeployed first container provides the microservice according to the reduced business processing capacity.

[0037] In the embodiment of the present application, if the business processing capacity required by the actual operation of the current business of the first container is less than the current business processing capacity of the first container, the business processing capacity of the first container is reduced, and the first container is redeployed according to the reduced business processing capacity, and the redeployed first container provides the microservice according to the reduced business processing capacity. In this way, there is no need to change the number of first containers, and one first container is kept as much as possible, but the business processing capacity of the first container is reduced, and the resource quota of the first container is reduced, which can avoid idle resources of the first container.

[0038] In some embodiments, the container cluster management subsystem is further used to reduce the business processing capacity of the first container when the business processing capacity required by the actual business operation of the first container is less than the current business processing capacity of the first container, and the current business processing capacity of the first container is greater than the preset minimum business processing capacity of the first container.

[0039] In the embodiment of the present application, a preset minimum business processing capacity of the first container is pre-set. When the business processing capacity required by the actual operation of the current business of the first container is less than the current business processing capacity of the first container, the business processing capacity of the first container can be reduced only when the current business processing capacity of the first container is greater than the preset minimum business processing capacity of the first container. In this way, other problems caused by excessive reduction of resources due to excessive reduction of the business processing capacity of the first container can be avoided.

[0040] In some embodiments, the container cluster management subsystem is further used to deploy the first container according to a preset initial business processing capability of the first container, so that the first container initially provides the microservice according to the preset initial business processing capability.

[0041] In an embodiment of the present application, a preset initial business processing capability of the first container is pre-set. Initially, the container cluster management subsystem deploys the first container according to the preset initial business processing capability of the first container. After deployment, the first container initially provides the microservice according to the preset initial business processing capability.

[0042] It should be noted that for the same microservice, only one template file (such as a blueprint) can be developed, and the preset maximum business processing capability, the preset minimum business processing capability, and the preset initial business processing capability of the first container providing the microservice are set in the template file. Compared with the related art in which multiple sets of template files (such as blueprints) of different specifications (i.e., different business processing capabilities) need to be developed due to the different business processing capabilities of the first container, the embodiments of the present application can reduce development, testing, and maintenance costs.

[0043] In some embodiments, the business processing capability is represented by a specification coefficient, and a larger specification coefficient indicates a stronger business processing capability.

[0044] For example: by adding a default specification factor DefaultSpecFactor (i.e., a preset initial business processing capability), a minimum specification factor MinSpecFactor (i.e., a preset minimum business processing capability) and a maximum specification factor MaxSpecFactor (i.e., a preset maximum business processing capability) in the blueprint, initially, the container cluster management subsystem uses the default specification factor DefaultSpecFactor as the dynamic specification factor SpecFactor to deploy the first container.

[0045] See also Figure 2 In some embodiments, the business system further includes: a second container.

[0046] The second container is used to replace the first container to provide the microservice during the process of redeploying the first container by the container cluster management subsystem.

[0047] Since the microservice may be temporarily unavailable during the process of redeploying the first container by the container cluster management subsystem, the business system of the embodiment of the present application may also include a second container. During the process of redeploying the first container by the container cluster management subsystem, the second container replaces the first container to provide the microservice, that is, a resident microservice instance may be retained, with a maximum of two instances (1+1) (the first container and the second container).

[0048] In some embodiments, the redeployed first container is further used to start a corresponding number of work threads according to the adjusted business processing capacity. In this way, high concurrency requirements can be met, making the business system scalable and extensible.

[0049] The business system of the embodiment of the present application is described in detail below.

[0050] The technical problem to be solved by the embodiments of the present application is to avoid the waste of idle resources caused by increasing the number of microservice instances to meet the increasing business pressure, while also avoiding the cost of developing and maintaining multiple sets of blueprints.

[0051] The solution of the embodiment of the present application is:

[0052] Step 1: Add the default specification factor DefaultSpecFactor (i.e., the preset initial business processing capability), the minimum specification factor MinSpecFactor (i.e., the preset minimum business processing capability), and the maximum specification factor MaxSpecFactor (i.e., the preset maximum business processing capability) to the blueprint.

[0053] Step 2: Initially, the container cluster management subsystem uses the default specification factor DefaultSpecFactor as the dynamic specification factor SpecFactor to deploy the first container.

[0054] Step 3: During operation, the container cluster management subsystem adjusts the dynamic specification coefficient SpecFactor of the first container according to the actual operation status of the current business of the first container, such as the average CPU utilization reaching 90% within 5 minutes, updates the dynamic specification coefficient SpecFactor of the first container (i.e., reallocates memory, CPU and other resources to the first container), and redeploys the first container.

[0055] Step 4: The application in the first container starts a corresponding number of worker threads according to the adjusted dynamic specification factor SpecFactor to meet high concurrency requirements.

[0056] The business system of the embodiment of the present application does not need to change the number of microservice instances, and tries to maintain one instance. The container cluster management subsystem adjusts the dynamic specification coefficient SpecFactor according to the actual operation of the current business of the first container, changes the resource quota of the instance (i.e., the first container), avoids the useless idle overhead caused by increasing the number of instances, and makes full use of valuable resources. At the same time, it is not necessary to develop multiple sets of blueprints of different specifications for the same microservice, reducing development, testing, and maintenance costs. The application in the first container starts the corresponding number of working threads according to the dynamic specification coefficient SpecFactor to meet high concurrency requirements, making the business system scalable and extensible, and maximizing the use of infrastructure resources such as memory and CPU.

[0057] See also Figure 3 , Figure 3 It is a schematic diagram of the interaction between the container cluster management subsystem and the first container in an embodiment of the business system of the present application.

[0058] Step S01: Add the default specification factor DefaultSpecFactor, the minimum specification factor MinSpecFactor and the maximum specification factor MaxSpecFactor to the blueprint.

[0059] Step S02: Initially, the container cluster management subsystem uses the default specification factor DefaultSpecFactor as the dynamic specification factor SpecFactor to deploy the first container.

[0060] Step S03: During operation, the container cluster management subsystem detects that the load of the first container is high (ie, the actual operation status of the current service of the first container). If the dynamic specification factor SpecFactor is less than MaxSpecFactor, the dynamic specification factor SpecFactor is increased and the first container is redeployed.

[0061] Step S04: the application in the first container starts a corresponding number of working threads according to the adjusted dynamic specification factor SpecFactor.

[0062] Step S05: During operation, the container cluster management subsystem detects that the load of the first container is low (ie, the actual operation status of the current service of the first container). If the dynamic specification factor SpecFactor is greater than MinSpecFactor, the dynamic specification factor SpecFactor is reduced and the first container is redeployed.

[0063] Step S06: The application in the first container starts a corresponding number of working threads according to the adjusted dynamic specification factor SpecFactor.

[0064] Figure 4 It is a comparative diagram of the business system of the embodiment of the present application and the traditional business system.

[0065] The memory of the microservice in the figure is 512M, the infrastructure such as the operating system and SDK (Software Development Kit) in the runtime container occupies 112M, and the actual available memory for the business is 400M.

[0066] If the business system adopts the traditional container scaling method (i.e. the traditional business system), and pops up 3 instances (i.e. deploys 3 containers), the available memory of each instance is 400M, and the infrastructure occupies 112M. In this way, the three instances are equivalent to a shared memory of 1536M, of which the business available memory is 1200M and the infrastructure shared memory is 336M.

[0067] If the business system adopts the system based on dynamic specification coefficient of the embodiment of the present application to realize variable container processing capacity, the container cluster management subsystem sets the specification coefficient to 3, with only 1 instance. When the total memory remains unchanged at 1536M, since only 1 copy of the infrastructure is required, the infrastructure only occupies 112M of memory. In this way, the business available memory is 1536-112=1424M. Compared with the traditional business system, the business available memory of the business system of the embodiment of the present application increases by 1424-1200=224M.

[0068] In order to make the purpose and technical effect of the embodiments of the present application clearer and more explicit, the following example uses the core network EMS (Element Management System) in the communications field to manage each microservice through the container cluster management subsystem, taking the performance data collection service pm-dt microservice as an example.

[0069] In order to meet the pressure of large containers, the existing EMS system (i.e., business system) separately creates blueprints for large containers and pops up three pm-dt instances to meet the pressure requirements. Since each pm-dt instance is idle, the operating system, SDK, and JVM (Java Virtual Machine) in the container occupy a certain amount of memory and CPU, especially memory. This will cause a certain amount of resource waste; at the same time, since the blueprints for large containers are customized separately, additional development, testing, and maintenance costs are also required.

[0070] According to the solution of the embodiment of the present application, the EMS system adds three parameters, namely, the default specification factor DefaultSpecFactor, the minimum specification factor MinSpecFactor, and the maximum specification factor MaxSpecFactor, to the blueprint for the pm-dt microservice at one time. For stress scenarios, the container cluster management subsystem initially uses the default specification factor DefaultSpecFactor as the dynamic specification factor SpecFactor to deploy the first container, and deploys the first container with a new specification factor by adjusting the dynamic specification factor SpecFactor during runtime. When the load of the first container increases, the dynamic specification factor is increased until the maximum specification factor MaxSpecFactor is reached, and when the load of the first container decreases, the dynamic specification factor is reduced until the minimum specification factor MinSpecFactor is reached.

[0071] The first container corresponding to the pm-dt microservice instance automatically adjusts the JVM parameters based on the new specification factor SpecFactor and starts the corresponding number of warehousing threads to achieve the purpose of improving processing capacity without increasing instances. In actual implementation, the business may be temporarily interrupted due to the instantaneous unavailability of microservices. This can be solved by fixing a pm-dt daemon microservice instance (i.e., the second container). The container cluster management subsystem dynamically adjusts the specification factor SpecFactor according to the load changes of the first container and redeploys the first container. Therefore, the EMS system is scalable and extensible, and avoids idle resource occupation caused by popping up multiple instances, making maximum use of infrastructure resources such as memory and CPU; at the same time, it is not necessary to develop multiple sets of blueprints to meet different specifications, reducing development, testing, and maintenance costs.

[0072] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0073] In hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0074] The preferred embodiments of the present application are described above with reference to the accompanying drawings, but the scope of the present application is not limited thereby. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present application shall be within the scope of the present application.

Claims

1. A business system, characterized in that: The business system includes: A first container is used to provide microservices according to the current business processing capability of the first container; The container cluster management subsystem is used to detect the actual business operation status of the first container during the process of the first container providing the microservice. When the business processing capability required by the current actual business operation status of the first container does not match the current business processing capability of the first container, the business processing capability of the first container is dynamically adjusted according to the current actual business operation status of the first container. According to the adjusted business processing capability of the first container, the first container is redeployed so that the redeployed first container provides the microservice according to the adjusted business processing capability.

2. The business system according to claim 1, characterized in that: The container cluster management subsystem is further used to increase the business processing capacity of the first container when the business processing capacity required by the actual operation of the current business of the first container is greater than the current business processing capacity of the first container, and redeploy the first container according to the increased business processing capacity of the first container, so that the redeployed first container provides the microservice according to the increased business processing capacity.

3. The business system according to claim 2, characterized in that: The container cluster management subsystem is further configured to increase the business processing capacity of the first container when the business processing capacity required by the actual operation of the current business of the first container is greater than the current business processing capacity of the first container and the current business processing capacity of the first container is less than the preset maximum business processing capacity of the first container.

4. The business system according to claim 1, characterized in that: The container cluster management subsystem is further used to reduce the business processing capacity of the first container when the business processing capacity required by the actual operation of the current business of the first container is less than the current business processing capacity of the first container, and redeploy the first container according to the reduced business processing capacity of the first container, so that the redeployed first container provides the microservice according to the reduced business processing capacity.

5. The business system according to claim 4, characterized in that: The container cluster management subsystem is further configured to reduce the service processing capacity of the first container when the service processing capacity required by the actual service operation of the first container is less than the current service processing capacity of the first container and the current service processing capacity of the first container is greater than the preset minimum service processing capacity of the first container.

6. The business system according to claim 1, characterized in that: The container cluster management subsystem is further used to deploy the first container according to the preset initial business processing capability of the first container, so that the first container initially provides the microservice according to the preset initial business processing capability.

7. The business system according to claim 1, characterized in that: The business processing capability is represented by a specification coefficient, and a larger specification coefficient indicates a stronger business processing capability.

8. The business system according to claim 1, characterized in that: The business system also includes: The second container is used to replace the first container to provide the microservice during the process of redeploying the first container by the container cluster management subsystem.

9. The business system according to claim 1, characterized in that: The business processing capability includes hardware resources, and the hardware resources at least include a central processing unit (CPU) and memory.

10. The business system according to claim 1, characterized in that: The redeployed first container is further used to start a corresponding number of working threads according to the adjusted business processing capacity.

Images