CN116886704A - Server management system, method, equipment and medium based on micro-service architecture - Google Patents

Abstract

The invention belongs to the technical field of microservice architecture and specifically provides a server management system, method, equipment and medium based on microservice architecture. The system includes a microservice module, the microservice module is connected to a service gateway cluster module, and the service gateway cluster module is connected to Load balancing module, the load balancing module is connected to the external request module; the service gateway cluster module and the microservice module are both connected to the server registration module, and the microserver is connected to the server fault tolerance module; the external request module receives high-concurrency and high-throughput access from the client request; the load balancing module automatically distributes the incoming traffic of the application according to the client's access request; the service gateway cluster module parses the access request, queries the service registry according to the parsing result, finds the target service, and calls it; when the service fails or is delayed, the server The fault tolerance module isolates and tolerates faults. Improve access fluency and reduce latency.

Description

Server management system, method, equipment and media based on microservice architecture

Technical field

The present invention relates to the technical field of microservice architecture, and specifically relates to a server management system, method, equipment and medium based on microservice architecture.

Background technique

Microservices is an architectural style for developing software systems. It is completely opposite to the traditional monolithic architecture (which combines all components together). The monolithic architecture only focuses on a single application. Microservices are small and independent. Microservice architecture It seems clear and logical, but in reality it is quite complicated. For microservice architecture, distribution is almost a must-have technology (such as distributed server). Due to the complexity of distribution itself, microservice architecture has also become more complicated.

The microservice architectural style is a way to develop a single application using a set of small services. Each service runs in its own process and uses lightweight mechanisms to communicate. These services are built based on business capabilities and can be independently deployed through automated deployment mechanisms. Deployment, these services are implemented using different programming languages, as well as different data storage technologies, and maintain a minimum of centralized management.

Regarding the current deployment of microservice architecture, due to the intricate dependencies between microservices, a request may rely on multiple backend services. In actual production use, these services may cause failures or delays. In a world with high traffic and high data In the transmission system, once a certain service is delayed, system resources may be exhausted in a short period of time, bringing down the entire system, causing system paralysis and downtime.

Contents of the invention

In view of the problem that once a delay occurs in a certain service, system resources may be exhausted in a short period of time and the entire system will be brought down, causing system paralysis and downtime, the present invention provides a server management system based on a microservice architecture. Methods, equipment and media.

In a first aspect, the technical solution of the present invention provides a server management system based on a microservice architecture, including a microservice module. The input end of the microservice module is connected to a service gateway cluster module, and the input end of the service gateway cluster module is connected to a load balancing module. , the input end of the load balancing module is connected to an external request module;

The output end of the service gateway cluster module and the input end of the microservice module are both connected to the server registration module, and the output end of the microserver is connected to the server fault tolerance module;

The external request module is used to receive high-concurrency and high-throughput access requests from clients;

The load balancing module is used to automatically distribute the incoming traffic of the application based on the client's access request;

The service gateway cluster module is used to parse access requests, query the service registry according to the parsing results, discover the target service, and call it;

When the target service provided by the microservice module fails or is delayed, the fault is isolated and tolerated through the server fault tolerance module.

As a further limitation of the technical solution of the present invention, the service gateway cluster module includes multiple groups of gateways. Clients access the microservice module by requesting the gateway; the gateway is used to collect data and access log information.

As a further limitation of the technical solution of the present invention, the service gateway cluster module also includes a dynamic routing module, a current limiting fault tolerance module, and an identity authentication and security control module;

Dynamic routing module, used to dynamically route access requests to the required service cluster;

The current limiting fault tolerance module is used to allocate capacity for each type of request. When the number of requests exceeds the threshold, external requests are thrown away to limit traffic;

The identity authentication and security control module is used to authenticate users for each external request and reject requests that fail authentication.

As a further limitation of the technical solution of the present invention, the load balancing module includes a load balancing control module and a security encryption module;

Load balancing control module for automatically distributing an application's incoming traffic across multiple gateways;

Security encryption module, used to ensure the security of client requests.

As a further limitation of the technical solution of the present invention, the system also includes a cluster server, in which all microservices are registered and health checks are regularly sent to the cluster server;

After receiving the last health check of the microservice, the cluster server waits for the first time threshold and clears the registration information of the microservice when the self-protection mode of the cluster server is turned off.

When the cluster server loses more than the set threshold number of services within the set time, it will enter the self-protection mode. In the self-protection mode, the cluster server will not receive the health check of the microservice after waiting for the first time threshold. It will be deleted.

As a further limitation of the technical solution of the present invention, the server fault-tolerant module is used to actively activate the fuse when the service is abnormal or the second set threshold number of service delays, or automatically activate the fuse mode, and after the service isolation set time period, The setting enters the semi-fuse state. If the call still fails, it returns to the fuse state. If the call is successful, the fuse mode is turned off.

As a further limitation of the technical solution of the present invention, the server fault-tolerant module is used to set different services to use different thread pools; when an exception occurs in the service call, the exception is directly discarded; it is enabled when the program runs out of time, the circuit breaker is started, or the thread pool is full. Rollback; also used to limit the concurrent access to the service, set the number of concurrencies per unit time, and reject requests that exceed the limit and rollback.

In the second aspect, the technical solution of the present invention provides a server management method based on microservice architecture, which is applied to the system described in the first aspect. The method includes the following steps:

Receive high-concurrency and high-throughput access requests from clients;

Automatically distribute the application's incoming traffic based on client access requests;

Parse the access request, query the service registry according to the parsing results, discover the target service, and call it;

When a target service fails or is delayed, the failed service is isolated and fault-tolerant.

As a further limitation of the technical solution of the present invention, the method also includes:

Register all microservices into the cluster server and generate a service registry;

Manage microservices by setting them to send health checks regularly.

As a further limitation of the technical solution of the present invention, the steps of managing the microservice by setting the microservice to regularly send health checks include:

Microservices regularly send health checks to cluster servers;

After receiving the last health check of the microservice, the cluster server waits for the first time threshold to receive the health check of the microservice;

Determine whether the cluster server has lost more than a set threshold number of services within a set time;

If so, the cluster server self-protection mode is turned on;

Clear the registration information of the microservice;

If not, the cluster server self-protection mode is turned off;

Do not clear the registration information of this microservice.

As a further limitation of the technical solution of the present invention, the steps of parsing the access request, querying the service registry according to the parsing result, discovering the target service and calling it include:

User authentication for each external request;

Determine whether the certification is passed;

If so, dynamically route the access request to the required service cluster;

Allocate capacity to each type of request, and when the number of requests exceeds the threshold, external requests are thrown away to limit traffic;

Query the service registry to find the target service and call it;

If not, reject the request without authentication.

As a further limitation of the technical solution of the present invention, when the target service fails or is delayed, the steps of isolating and fault-tolerating the failed service include:

When the target service is abnormal or the target service delay exceeds the first threshold, set the active circuit breaker to execute and return directly;

Or automatically start the circuit breaker mode, and after the service isolation set time period, the setting enters the semi circuit breaker state. If the call still fails, it returns to the circuit breaker state. If the call is successful, the circuit breaker mode is turned off;

As a further limitation of the technical solution of the present invention, when the target service fails or is delayed, the steps of isolating and fault-tolerating the failed service include:

When an exception occurs in the target service call, determine whether there is a program running abnormally, circuit breaker startup, or the thread pool is full;

If so, enable fallback;

If not, discard the exception directly or return to the previous step.

As a further limitation of the technical solution of the present invention, the method further includes: collecting access log information.

In a third aspect, the technical solution of the present invention also provides an electronic device. The electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; the memory stores information that can be executed by the at least one processor. Computer program instructions, the computer program instructions are executed by the at least one processor, so that the at least one processor can execute the server management method based on the microservice architecture as described in the first aspect.

In a fourth aspect, the technical solution of the present invention also provides a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores computer instructions. The computer instructions cause the computer to execute as described in the first aspect. A server management method based on microservice architecture.

It can be seen from the above technical solutions that the present invention has the following advantages: the present invention is based on a microservice architecture, and in high-load and high-concurrency scenarios, automatically distributes the incoming traffic of applications from data input to output, improving access fluency, and Reduce latency; when the target service fails or is delayed, its fault can be isolated and fault-tolerant, reducing the delay caused by a certain service during the use of the server, causing the entire system to run out of resources, thereby bringing down the entire system and improving the system Runtime stability and reliability.

In addition, the design principle of the invention is reliable, the structure is simple, and it has very broad application prospects.

It can be seen that compared with the prior art, the present invention has outstanding substantive features and significant progress, and the beneficial effects of its implementation are also obvious.

Description of the drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those of ordinary skill in the art, It is said that other drawings can also be obtained based on these drawings without exerting creative work.

Figure 1 is a schematic connection block diagram of a system provided by an embodiment of the present invention.

Figure 2 is a schematic connection diagram of the service gateway cluster module in the embodiment of the present invention.

Figure 3 is a schematic diagram of the server fault tolerance module mode in the embodiment of the present invention.

Figure 4 is a schematic flow chart of a method according to an embodiment of the present invention.

Figure 5 is a connection block diagram of electronic equipment in the embodiment of the present invention.

Detailed ways

Those of ordinary skill in the art can appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of both. In order to clearly illustrate the relationship between hardware and software Interchangeability, in the above description, the composition and steps of each example have been generally described according to functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered to be beyond the scope of the present invention.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and/or processor devices and/or microcontroller devices. entity.

In the embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. In addition, the coupling or direct coupling or communication connection between each other shown or discussed may be an indirect coupling or communication connection through some interfaces, devices or units, or may be electrical, mechanical or other forms of connection.

Furthermore, the described features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to provide a thorough understanding of embodiments of the invention. However, those skilled in the art will appreciate that the technical solutions of the present invention may be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other instances, well-known methods, apparatus, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the present invention. In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described The embodiments are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of the present invention.

Due to the complex dependencies between microservices, a request may rely on multiple backend services. In actual production, these services may malfunction or be delayed. Once a service is delayed, it may consume time in a short period of time. It exhausts system resources, brings down the entire system, reduces system reliability and stability, brings hidden dangers to the server's business processing capabilities, and causes losses to customers. In view of this, as shown in Figure 1, an embodiment of the present invention provides a server management system based on a microservice architecture, including a microservice module. The input end of the microservice module is connected to a service gateway cluster module. The input end of the service gateway cluster module A load balancing module is connected, and an external request module is connected to the input end of the load balancing module;

The output end of the service gateway cluster module and the input end of the microservice module are both connected to the server registration module, and the output end of the microserver is connected to the server fault tolerance module;

The external request module is used to receive high-concurrency and high-throughput access requests from clients;

The load balancing module is used to automatically distribute the incoming traffic of the application based on the client's access request;

The service gateway cluster module is used to parse access requests, query the service registry according to the parsing results, discover the target service, and call it;

When the target service provided by the microservice module fails or is delayed, the fault is isolated and tolerated through the server fault tolerance module.

The external request module receives high-concurrency and high-throughput access from the client, and the load balancing module automatically distributes the incoming traffic of the application, which can play a role of diversion and at the same time encrypt the service to ensure the security of client requests; service The gateway cluster module can discover the target service and call it by querying the service registry; the service access of the service gateway cluster module and microservice module is registered and discovered by the cluster server; a server fault tolerance module is connected to the output end of the microservice module , In high load and high concurrency scenarios, when the target service provided by the microservice module fails or is delayed, the server fault tolerance module can be used to isolate and tolerate the fault. In this way, the entire design is to unblock traffic and services from input to output, solve the current intricate dependencies between microservices, and reduce the consumption of the entire system due to delays in certain services during the use of the server. It will exhaust resources and bring down the entire system, which has the advantage of improving the stability of the system during operation.

In some embodiments, the service gateway cluster module includes multiple groups of gateways, and clients access the microservice module by requesting the gateways; the gateways are used to collect data and access log information.

When used, when the gateway service forwards an external request to call the front-end service, the target service can be found and called by querying the service registry. A request may involve mutual calls between multiple services.

As shown in Figure 2, the service gateway cluster module is composed of multiple groups of gateway modules (gateways in this application). The gateway module can be understood as a door between the external system and the internal system of the enterprise. All clients pass the request The gateway module accesses the microservice module.

It should be noted that the service gateway cluster module also includes a dynamic routing module, a current limiting fault tolerance module, and an identity authentication and security control module;

Dynamic routing module, used to dynamically route access requests to the required service cluster;

The current limiting fault tolerance module is used to allocate capacity for each type of request. When the number of requests exceeds the threshold, external requests are thrown away to limit traffic;

The identity authentication and security control module is used to authenticate users for each external request and reject requests that fail authentication.

Dynamic routing: Dynamically route requests to the required backend service cluster. Current limiting and fault tolerance: Allocate capacity for each type of request. When the number of requests exceeds the threshold, external requests are discarded and the traffic is limited. This can protect the background service from being overwhelmed by heavy traffic; Identity authentication and security control: It can User authentication is performed for each external request, and requests that fail to pass authentication are rejected; monitoring: that is, the gateway can collect meaningful data and statistics to provide data support for background service optimization; access log: the gateway can collect access log information and analyze the log content , further optimize the backend system.

In some embodiments, the load balancing module includes a load balancing control module and a security encryption module;

Load balancing control module for automatically distributing an application's incoming traffic across multiple gateways;

Security encryption module, used to ensure the security of client requests.

As the name suggests, the load balancing module is designed to cope with high-concurrency access scenarios. Since the gateway module is deployed in a cluster, it is necessary to achieve load balancing when accessing the gateway module. The load balancing module consists of a load balancing control module and a security encryption module. The load balancing control module automatically distributes the incoming traffic of the application among multiple gateway modules, while the security encryption module is used to ensure the security of client requests. sex. Load balancing uses the ELB module, and security encryption can use relatively reliable SSL encryption.

When used, in order to cope with high concurrent access, the service gateway is deployed in the form of a cluster. This means that load balancing is required. Virtual cloud servers can be used for load balancing. Since the virtual cloud server has the function of automatically configuring capacity, when user traffic reaches peak , the virtual cloud server can automatically add more capacity to maintain the performance of the virtual host, and due to load balancing, the incoming traffic of the application can be automatically distributed among multiple service gateways.

In some embodiments, the system also includes a cluster server. All microservices are registered in the cluster server and health checks are sent to the cluster server regularly;

After receiving the last health check of the microservice, the cluster server waits for the first time threshold and clears the registration information of the microservice when the self-protection mode of the cluster server is turned off.

When the cluster server loses more than the set threshold number of services within the set time, it will enter the self-protection mode. In the self-protection mode, the cluster server will not receive the health check of the microservice after waiting for the first time threshold. It will be deleted.

The front-end external request module is the client, such as a client terminal such as a PC or a mobile phone.

The server registration module mentioned above is specifically composed of a cluster server module. Since the microservice architecture is a mesh structure composed of a series of services with single responsibilities, the services communicate through lightweight mechanisms, which introduces service registration and discovery. The service provider must register and report the service address, and the service caller must be able to discover the target service. Therefore, the service access of the service gateway cluster module and microservice module is registered and discovered by the cluster server.

Specifically: all microservices register in the cluster server and send health checks regularly. The default configuration of the cluster server is to send a health check every 20 seconds (set 20 seconds here to consider increasing the check frequency), indicating that the service is still alive. Status, the time interval for sending health checks can be configured by the cluster server configuration parameters. After the cluster server receives the last health check of the service instance, it needs to wait 60 seconds (the default configuration is 60 seconds, which can also be modified through the configuration parameters). , it is determined that the service is dead (that is, no heartbeat is received for 3 consecutive times (20x3)). When the cluster server self-protection mode is turned off, the registration information of the service will be cleared.

The self-protection mode mentioned here means that when a network partition occurs and the cluster server loses too many services in a short period of time, it will enter the self-protection mode. That is, if a service does not send heartbeats for a long time, the cluster server will not delete it.

In some embodiments, the server fault tolerance module is used to actively activate the circuit breaker or automatically activate the circuit breaker mode when the service is abnormal or the service is delayed by a second set threshold number, and after the service isolation set time period, the setting enters half-time. In the fuse state, if the call still fails, it will return to the fuse state. If the call is successful, the fuse mode will be turned off.

The server fault tolerance module is used to set different services to use different thread pools; when an exception occurs in a service call, the exception is discarded directly; when the program runs out of time, the circuit breaker is started, or the thread pool is full, rollback is enabled; it is also used to configure the service Limit the number of concurrent visits and set the number of concurrencies per unit time. Requests that exceed the limit will be rejected and rolled back.

As shown in Figure 3, the server fault tolerance module includes circuit breaker mode, isolation mode, fallback mode and current limiting mode.

Let’s talk about each mode: Circuit breaker mode: When the service is abnormal or has a large delay, and the circuit breaker conditions are met, the service caller will actively initiate the circuit breaker, and the execution will return directly without continuing to call the service to further bring down the system, or use the automatic circuit breaker mode. If the threshold is exceeded, the fuse mode will be automatically activated, and after the service is isolated for a period of time, the fuse will enter the semi-fuse state, which allows a small number of requests to be tried. If the call still fails, it will return to the fuse state. If the call is successful, the fuse mode will be turned off. .

Isolation mode: Different services use different thread pools and are not affected by each other. When a service fails and exhausts its thread pool resources, the normal operation of other services is not affected, achieving the isolation effect;

Rollback: When an exception occurs in a service call, you can directly discard the exception or return to the previous step. When the following exceptions occur, rollback can be enabled: program running timeout, circuit breaker startup, and thread pool is full;

Current limiting: Current limiting can limit the number of concurrent accesses to the service and set the number of concurrencies per unit time. Requests that exceed the limit will be rejected and rolled back to prevent background services from being overwhelmed. The fault tolerance module mentioned here can be handled by Hystrix components, which is more convenient.

The microservice architecture adds load balancing, which is composed of a load balancing control module and a security encryption module. It automatically distributes the incoming traffic of the application, which can play a diversion role and reduce the concentration of high concurrent access traffic on one group or multiple groups of service gateways. situation, and at the same time encrypts the service to ensure the security of client requests. The service access of the service gateway cluster module and microservice module is registered and discovered by the cluster server, so that the target service can be discovered and called by querying the service registry.

The server fault tolerance module includes fusing, isolation, fallback and current limiting modes. When used, when the target service provided by the microservice module fails or is delayed, the fault tolerance module can be used to isolate and tolerate the fault, reducing the server's risk of a certain The service is delayed, resulting in exhaustion of system resources.

The external request module receives the access request sent by the client, and the load balancing module accesses the client's access request, and sends the access request to one or more gateways according to the predetermined policy to authenticate the user login account carried in the access request and determine whether Whether the above login account has access rights; if there is access rights, according to the request content carried in the access request, determine the target microservice corresponding to the request content from the service registration table; determine the address of the target microservice from the server registration module , and call the service interface of the microservice corresponding to the access request according to the access request, access the target microservice, and call the target microservice to respond to the access request. Specifically, the access request is to obtain data. When requesting, the target microservice accesses the cache and determines whether the data corresponding to the access request is cached in the cache; when the cache has corresponding data, the target microservice obtains the data from the cache; when there is no corresponding data in the cache, The target microservice searches for and obtains the corresponding data from the database, caches the obtained data, and sends the requested data corresponding to the client. The access log records each access request received, as well as information related to the identity authentication of each requesting user and the request result corresponding to the access request.

As shown in Figure 4, the embodiment of the present invention provides a server management method based on microservice architecture, which is applied to the system described in the above embodiment. The method includes the following steps:

Step 1: Receive high-concurrency and high-throughput access requests from clients;

Step 2: Automatically distribute the application’s incoming traffic based on the client’s access request;

Step 3: Parse the access request, query the service registry according to the parsing results, find the target service, and call it;

Step 4: When the target service fails or is delayed, isolate and tolerate the failed service.

It should be noted that this method also includes: registering all microservices into the cluster server and generating a service registry; and managing the microservices by setting the microservices to send health checks regularly.

It should be further explained that the steps for managing microservices by setting up microservices to regularly send health checks include: microservices regularly send health checks to the cluster server; after receiving the last health check of the microservice, the cluster server waits for the The health check of the microservice is not received for a time threshold; determine whether the cluster server has lost more than the set threshold number of services within the set time; if so, the cluster server self-protection mode is turned on; the registration information of the microservice is cleared; if not , the cluster server self-protection mode is turned off; the registration information of the microservice is not cleared.

That is to say, all microservices register with the cluster server and send health checks regularly. The default configuration of the cluster server is to send a health check every 20 seconds (setting 20 seconds here considers increasing the check frequency), indicating that the service is still alive. , the time interval for sending health checks can be configured by the cluster server configuration parameters. After the cluster server receives the last health check of the service instance, it needs to wait 60 seconds (the default configuration is 60 seconds, which can also be modified through the configuration parameters). Only after it is determined that the service is dead (that is, no heartbeats are received for three consecutive times (20x3)), the registration information of the service will be cleared when the self-protection mode of the cluster server is turned off. The self-protection mode mentioned here means that when a network partition occurs and the cluster server loses too many services in a short period of time, it will enter the self-protection mode. That is, if a service does not send heartbeats for a long time, the cluster server will not delete it.

In some embodiments, the steps of parsing the access request, querying the service registry according to the parsing results, discovering the target service and calling it include:

Step 31: Perform user authentication for each external request;

Step 32: Determine whether the authentication is passed;

If yes, go to step 33; if not, go to step 36;

Step 33: Dynamically route the access request to the required service cluster;

Step 34: Allocate capacity for each type of request, and when the number of requests exceeds the threshold, discard external requests to limit traffic;

Step 35: Query the service registry to find the target service and call it;

Step 36: Reject requests that fail authentication.

In some embodiments, when a target service fails or is delayed, the steps of isolating and fault-tolerating the failed service include:

When the target service is abnormal or the target service delay exceeds the first threshold, set the active circuit breaker to execute and return directly;

Or automatically start the circuit breaker mode, and after the service isolation set time period, the setting enters the semi circuit breaker state. If the call still fails, it returns to the circuit breaker state. If the call is successful, the circuit breaker mode is turned off;

When an exception occurs in the target service call, determine whether there is a program running abnormally, circuit breaker startup, or the thread pool is full;

If so, enable fallback;

If not, discard the exception directly or return to the previous step.

That is to say, the circuit breaker mode: when the service is abnormal or has a large delay and the circuit breaker conditions are met, the service caller will actively initiate circuit breaker and return directly without continuing to call the service to further bring down the system, or adopt the automatic circuit breaker mode. The threshold will automatically activate the circuit breaker mode, and after the service is isolated for a period of time, the circuit breaker will enter a semi-circuit state, which allows a small number of requests to be tried. If the call still fails, it will return to the circuit breaker state. If the call is successful, the circuit breaker will turn off the circuit breaker mode.

Isolation mode: Different services use different thread pools and are not affected by each other. When a service fails and exhausts its thread pool resources, the normal operation of other services is not affected, achieving the isolation effect;

Rollback: When an exception occurs in a service call, you can directly discard the exception or return to the previous step. When the following exceptions occur, rollback can be enabled: program running timeout, circuit breaker startup, and thread pool is full;

Current limiting: Current limiting can limit the number of concurrent accesses to the service and set the number of concurrencies per unit time. Requests that exceed the limit will be rejected and rolled back to prevent background services from being overwhelmed.

As shown in Figure 5, an embodiment of the present invention also provides an electronic device. The electronic device includes: a processor, a communication interface, a memory, and a communication bus. The processor, the communication interface, and the memory complete mutual communication through the communication bus. communication. A communication bus can be used to transmit information between electronic devices and sensors. The processor can call logical instructions in the memory to perform the following methods: Step 1: Receive high-concurrency, high-throughput access requests from the client; Step 2: Automatically distribute the incoming traffic of the application according to the client's access requests; Step 3: Parse the access request, query the service registry according to the parsing results, find the target service, and call it; Step 4: When the target service fails or is delayed, isolate and fault-tolerate the failed service.

In addition, the above-mentioned logical instructions in the memory can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present invention essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .

Embodiments of the present invention provide a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores computer instructions. The computer instructions cause the computer to execute the method provided by the above method embodiment, for example, including: Step 1: Receive high-concurrency, high-throughput access requests from clients; Step 2: Automatically allocate the incoming traffic of the application according to the client's access requests; Step 3: Parse the access requests, query the service registry according to the parsing results, discover the target service, and call it ; Step 4: When the target service fails or is delayed, isolate and tolerate the failed service.

As the server management system, method, device and medium based on the microservice architecture of the present invention, they are the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein, and can be implemented by electronic hardware, computer software or a combination of both. Implementation, in order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered to be beyond the scope of the present invention.

Although the present invention has been described in detail with reference to the accompanying drawings in conjunction with preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the invention, those of ordinary skill in the art can make various equivalent modifications or substitutions to the embodiments of the invention, and these modifications or substitutions should be within the scope of the invention/any Those skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention, and they should all be covered by the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (10)

1. A server management system based on microservice architecture, characterized in that it includes a microservice module. The input end of the microservice module is connected to a service gateway cluster module. The input end of the service gateway cluster module is connected to a load balancing module. The load balancing module The input end of the module is connected to an external request module; The output end of the service gateway cluster module and the input end of the microservice module are both connected to the server registration module, and the output end of the microserver is connected to the server fault tolerance module; The external request module is used to receive high-concurrency and high-throughput access requests from clients; The load balancing module is used to automatically distribute the incoming traffic of the application based on the client's access request; The service gateway cluster module is used to parse access requests, query the service registry according to the parsing results, discover the target service, and call it; When the target service provided by the microservice module fails or is delayed, the fault is isolated and tolerated through the server fault tolerance module. 2. The server management system based on microservice architecture according to claim 1, characterized in that the service gateway cluster module includes multiple groups of gateways, and clients all access the microservice module by requesting the gateway; the gateway is also used to collect data and Access log information. 3. The server management system based on microservice architecture according to claim 2, characterized in that the service gateway cluster module also includes a dynamic routing module, a current limiting fault tolerance module and an identity authentication and security control module; Dynamic routing module, used to dynamically route access requests to the required service cluster; The current limiting fault tolerance module is used to allocate capacity for each type of request. When the number of requests exceeds the threshold, external requests are thrown away to limit traffic; The identity authentication and security control module is used to authenticate users for each external request and reject requests that fail authentication. 4. The server management system based on microservice architecture according to claim 3, characterized in that the load balancing module includes a load balancing control module and a security encryption module; Load balancing control module for automatically distributing an application's incoming traffic across multiple gateways; Security encryption module, used to ensure the security of client requests. 5. The server management system based on microservice architecture according to claim 4, characterized in that the system also includes a cluster server, all microservices are registered in the cluster server, and health checks are regularly sent to the cluster server; After receiving the last health check of the microservice, the cluster server waits for the first time threshold and clears the registration information of the microservice when the self-protection mode of the cluster server is turned off. 6. The server management system based on the microservice architecture according to claim 5, characterized in that the server fault tolerance module is used to actively start the circuit breaker when the service is abnormal or the service is delayed by a second set threshold number, or automatically After activating the circuit breaker mode and setting the service isolation period, the system enters the semi- circuit breaker state. If the call still fails, it returns to the circuit breaker state. If the call succeeds, the circuit breaker mode is turned off. 7. The server management system based on microservice architecture according to claim 6, characterized in that the server fault tolerance module is used to set different services to use different thread pools; when an exception occurs in the service call, the exception is directly discarded; when Enable rollback when the program runs out of time, circuit breaker is started, or the thread pool is full; it is also used to limit the number of concurrent accesses to the service, set the number of concurrencies per unit time, and reject requests that exceed the limit and roll back. 8. A server management method based on microservice architecture, characterized in that it is applied to the system according to any one of claims 1-7, and the method includes the following steps: Receive high-concurrency and high-throughput access requests from clients; Automatically distribute the application's incoming traffic based on client access requests; Parse the access request, query the service registry according to the parsing results, discover the target service, and call it; When a target service fails or is delayed, the failed service is isolated and fault-tolerant. 9. An electronic device, characterized in that the electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; the memory stores computer program instructions that can be executed by the at least one processor, The computer program instructions are executed by the at least one processor, so that the at least one processor can execute the server management method based on the microservice architecture according to any one of claims 1 to 7. 10. A non-transitory computer-readable storage medium, characterized in that the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions cause the computer to execute the method according to any one of claims 1 to 7. The server management method based on microservice architecture described above.