Microservice Management System

Abstract

A microservice management system, applicable to a container orchestration system, includes a container management module, a service management module, and a monitoring module. For each microservice, the service management module determines whether a performance metric of the microservice exceeds a load limit threshold and a preset number of times within a predetermined time period. When the service management module determines that the performance metric exceeds the load limit threshold within the predetermined time period, it dynamically adjusts the computing resources used by the microservice. For each microservice, the monitoring module determines whether another performance metric of the microservice exceeds another preset threshold and another preset number of times within another predetermined time period. When the monitoring module determines that the other performance metric exceeds the other preset threshold and the other preset number of times within the other predetermined time period, it issues an alarm message.

Claims

1. A microservice management system, suitable for use with a container orchestration system and multiple client electronic devices, comprising: a storage unit; and a processing unit electrically connected to the storage unit, and comprising a gateway control module, a container management module, a service management module, and a monitoring module, wherein the container management module is used to deploy one or more containers corresponding to one or more microservices to be executed on one or more nodes, the service management module is used to obtain a performance indicator corresponding to each of the microservices, and the monitoring module is used to obtain another performance indicator corresponding to each of the microservices; wherein, The gateway control module receives multiple service requests from client electronic devices, each service request corresponding to one of the microservices. For each service request, the gateway control module obtains a key value from a header field or a query parameter of the service request and verifies whether the key value corresponds to a pre-registered user unit. When the gateway control module verifies that the key value corresponds to the user unit, it analyzes a path, a hostname, or an HTTP method in the Uniform Resource Locator (URL) of the received service request and routes the service request accordingly to the microservice corresponding to the service request. The container set corresponding to the microservice is then responsible for processing the service request. For each microservice, the service management module determines whether the performance index of the microservice exceeds a load limit threshold a preset number of times within a predetermined time. If the determination result is yes, the module dynamically adjusts the computing resources used by the microservice. For each microservice, the monitoring module determines whether another performance metric of the microservice exceeds another preset threshold or another preset number of times within another predetermined time period, and issues an alarm message if the determination result is yes.

2. The microservice management system as described in request item 1, wherein, The service management module dynamically adjusts the computing resources used by the microservice, including: when the service management module determines that the performance index exceeds the load limit threshold for a predetermined number of consecutive times within a predetermined time, it executes a scaling procedure to dynamically increase the number of container sets of the microservice, and the number of container sets is not greater than a maximum number of replicas.

3. The microservice management system as described in request item 1, wherein, The service management module determines whether the performance metric is less than a load threshold. When the performance metric is determined to be less than the load threshold, a scaling-down procedure is executed to dynamically reduce the number of containers for the microservice. The number of containers is not less than a minimum number of replicas.

4. The microservice management system as described in claim 1 further includes an application-layer log management module, which is used to collect and analyze one or more application-layer logs output by the microservice(s); wherein, For each microservice, the application layer log management module determines whether the application layer log corresponding to each microservice meets an alarm condition, and if the determination result is yes, issues another alarm message.

5. The microservice management system as described in request item 1, wherein, Both of these performance metrics include a CPU utilization or a memory utilization for all container sets related to the microservice.

6. The microservice management system as described in claim 1, wherein, The monitoring module obtains the maximum memory capacity of a node and the used memory capacity of a node for the node(e). It then divides the used memory capacity of the node by the maximum memory capacity of the node to obtain the memory utilization rate of the node as another performance indicator.

7. The microservice management system as described in request item 1, wherein, The gate control module determines whether the number of service requests received within a predetermined time unit exceeds a preset upper limit. When the gate control module determines that the number of service requests within the predetermined time unit exceeds the preset upper limit, it refuses to receive subsequent service requests received within that time unit.

Images