Service management method and system and storage medium
By automatically isolating failed service instances by using monitoring components and service management middleware in the service management system, the high cost and misoperation problems caused by manual intervention are solved, and efficient service management and service continuity are achieved.
Patent Information
- Application Number
- CN202411029082.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2024-12-06
AI Technical Summary
The prior art requires manual intervention for isolation in the event of service instances and/or machine failures, resulting in high costs and possible misoperation problems.
By introducing monitoring components and service management middleware into the service management system, the status of the target service instance is monitored in real time and sent to the name service system, and the faulty service instance is automatically isolated to avoid manual intervention.
It realizes convenient service management, reduces costs, avoids misoperation, ensures that the failed service instance does not undertake user traffic, and is automatically opened after failure recovery, improving service continuity and response speed.
Smart Images

Figure CN119088635A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a service management method, system and storage medium. Background Art
[0002] Currently, when a service instance and / or machine (i.e., service deployment device) fails, manual intervention is usually required to isolate (i.e., shield) the failed service instance, which results in high costs and possible misoperation. Based on this, there is currently no good solution for how to conveniently manage services to isolate failed service instances while reducing costs and avoiding misoperation. Summary of the invention
[0003] In view of this, an embodiment of the present invention provides a service management method, system and storage medium to solve the problem that related technologies require manual judgment and isolation of faulty service instances, resulting in high labor costs and possible misoperation. In other words, an embodiment of the present invention can conveniently perform service management to effectively isolate faulty service instances while reducing costs and avoiding misoperation.
[0004] According to one aspect of an embodiment of the present invention, a service management method is provided, the method being applied to a service management system, the service management system comprising service management middleware, a name service system, and at least one target service deployment device, the target service deployment device comprising a monitoring component and a target service instance in at least one target service instance of a target service, the method comprising:
[0005] The monitoring component in each target service deployment device of the at least one target service deployment device monitors the target service instance on the corresponding target service deployment device respectively, obtains the instance state identifier of the target service instance on the corresponding target service deployment device, and sends the instance state identifier of the target service instance on the corresponding target service deployment device to the name service system;
[0006] After receiving the instance status identifiers of the target service instances, the name service system stores the instance status identifiers of the target service instances;
[0007] The service management middleware receives the instance status identifiers of the target service instances sent by the name service system, and based on the instance status identifiers of the target service instances, isolates the faulty service instances of the target service, and opens the non-faulty service instances of the target service to the outside to provide the target service. The non-faulty service instances of the target service include all target service instances among the at least one target service instance except the faulty service instance of the target service.
[0008] According to another aspect of an embodiment of the present invention, a service management system is provided, the service management system comprising service management middleware, a name service system and at least one target service deployment device, a target service deployment device comprising a monitoring component and a target service instance in at least one target service instance of a target service, the service management system comprising:
[0009] The monitoring component in each target service deployment device of the at least one target service deployment device is used to monitor the target service instance on the corresponding target service deployment device, obtain the instance state identifier of the target service instance on the corresponding target service deployment device, and send the instance state identifier of the target service instance on the corresponding target service deployment device to the name service system;
[0010] The name service system is used to store the instance status identifiers of each target service instance of the target service after receiving the instance status identifiers of each target service instance of the target service;
[0011] The service management middleware is used to receive the instance status identifiers of the target service instances sent by the name service system, and based on the instance status identifiers of the target service instances, isolate the faulty service instances of the target service, and open the non-faulty service instances of the target service to the outside to provide the target service. The non-faulty service instances of the target service include all target service instances among the at least one target service instance except the faulty service instance of the target service.
[0012] According to another aspect of an embodiment of the present invention, an electronic device is provided, comprising a processor and a memory for storing programs; wherein the electronic device is used to constitute a service management system, and the electronic device is used to enable the service management system to execute the above-mentioned method.
[0013] According to another aspect of an embodiment of the present invention, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable a computer to execute the above-mentioned method.
[0014] In the embodiment of the present invention, the monitoring components in each target service deployment device in at least one target service deployment device can respectively monitor the target service instance on the corresponding target service deployment device, obtain the instance status identifier of the target service instance on the corresponding target service deployment device, and send the instance status identifier of the target service instance on the corresponding target service deployment device to the name service system. After receiving the instance status identifier of each target service instance of the target service, the name service system can store the instance status identifier of each target service instance. The service management middleware can receive the instance status identifier of each target service instance sent by the name service system, and based on the instance status identifier of each target service instance, isolate the faulty service instance of the target service, and open the non-faulty service instance of the target service to the outside to provide the target service, and the non-faulty service instance of the target service includes all target service instances in at least one target service instance except the faulty service instance of the target service. It can be seen that the embodiment of the present invention can achieve the isolation of faulty service instances without manual intervention, so as to avoid developing the faulty service instances to the outside, so that the faulty service instances do not have to take over user traffic; that is to say, the embodiment of the present invention can conveniently perform service management through monitoring components and service management middleware, so as to effectively achieve the isolation of faulty service instances while reducing costs and avoiding misoperation. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Further details, features and advantages of the invention are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:
[0016] Figure 1 A schematic flow chart of a service management method according to an exemplary embodiment of the present invention is shown;
[0017] Figure 2 A schematic flow chart of another service management method according to an exemplary embodiment of the present invention is shown;
[0018] Figure 3 A schematic diagram showing a service access according to an exemplary embodiment of the present invention;
[0019] Figure 4 A schematic diagram of a service management system according to an exemplary embodiment of the present invention is shown;
[0020] Figure 5 A block diagram of an exemplary electronic device that can be used to implement an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0021] Embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not intended to limit the scope of protection of the present invention.
[0022] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.
[0023] The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc. mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0024] It should be noted that the modifications of "one" and "plurality" mentioned in the present invention are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0025] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only used for illustrative purposes, and are not used to limit the scope of these messages or information.
[0026] It should be noted that the embodiments of the present invention may involve a service management system, which may include but is not limited to: service management middleware, a name service system (also referred to as a BNS (i.e., Baidu naming service) service system) and at least one target service deployment device, wherein a target service deployment device includes a monitoring component and a target service instance in at least one target service instance of a target service; wherein the name service system provides a mapping of a service name (i.e., a service identifier, also referred to as a BNS name) to a service running instance (also referred to as a service instance), and an information list of a service instance under a corresponding service (also referred to as a service instance of a corresponding service) can be obtained according to a service identifier, including but not limited to information such as a host name (i.e., the device name of the service deployment device where the corresponding service instance is located), an IP (Internet Protocol, a protocol for interconnection between networks), and a port. When a service wants to access other services, it can find the IP of the corresponding service through the BNS name of the corresponding service. Optionally, the service management system may also include all service deployment devices in at least one service deployment device except for at least one target service deployment device, that is, the service management system may include at least one service deployment device, at least one service deployment device may include at least one target service deployment device, at least one service deployment device may be used to deploy service instances of each service in at least one service, and the target service may be any service in at least one service.
[0027] In an embodiment of the present invention, the name service system may include at least one electronic device, that is, the name service system may be composed of at least one electronic device; accordingly, the service management middleware and a service deployment device may both be an electronic device; in other words, the service management system may include at least one electronic device. Based on this, the service management method provided in an embodiment of the present invention may be applied to a service management system, that is, the execution subject of the service management method provided in an embodiment of the present invention may be one or more electronic devices, that is, the execution subject of the service management method provided in an embodiment of the present invention may be an electronic device constituting a service management system.
[0028] Optionally, the electronic device may be a terminal (i.e., a client) or a server. The terminals mentioned here may include, but are not limited to, smart phones, tablet computers, laptop computers, desktop computers, smart watches, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, and the like. The server mentioned here may be an independent physical server, or a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms, and the like.
[0029] Based on the above description, an embodiment of the present invention proposes a service management method, which can be applied to a service management system. The service management system may include service management middleware, a name service system, and at least one target service deployment device. A target service deployment device includes a monitoring component and a target service instance in at least one target service instance of a target service; Figure 1 As shown, the service management method may include the following steps S101-S103:
[0030] S101, the monitoring components in each target service deployment device of at least one target service deployment device respectively monitor the target service instance on the corresponding target service deployment device, obtain the instance status identifier of the target service instance on the corresponding target service deployment device, and send the instance status identifier of the target service instance on the corresponding target service deployment device to the name service system.
[0031] Optionally, when a target service has a newly added service instance, at least one target service deployment device may include a service deployment device where the newly added service instance of the target service is located, that is, the service deployment device where the newly added service instance of the target service is located may be used as a target service deployment device; correspondingly, when a target service has a deleted service instance, the service deployment device where the deleted service instance of the target service is located may be deleted from at least one target service deployment device, that is, the service deployment device where the deleted service instance of the target service is located may not be used as a target service deployment device. The target service may be any service in at least one service, and each service in at least one service may be a BNS service; optionally, a service may be a microservice, and a microservice may include one or more programs, which may be accessed by users inside or outside the company and provide users with one or more functions.
[0032] Among them, a monitoring component in a service deployment device can be used to monitor each service instance in the corresponding service deployment device, that is, a monitoring component in a service deployment device can be used to monitor the instance running status of each service instance in the corresponding service deployment device to obtain an instance status identifier of each service instance in the corresponding service deployment device. An instance status identifier can be used to indicate an instance running status (such as faulty or not faulty, etc.).
[0033] In an embodiment of the present invention, the monitoring component in any service deployment device can monitor each service instance on any service deployment device in real time, that is, the monitoring component in any service deployment device can realize real-time monitoring of each service instance on any service deployment device (that is, it can realize real-time monitoring of the instance running status of each service instance on any service deployment device), so as to obtain the instance status identifier of each service instance on any service deployment device in real time, so as to send the instance status identifier of each service instance on any service deployment device to the name service system in real time. In this case, for any target service deployment device in at least one target service deployment device, the monitoring component in any target service deployment device can monitor the target service instance on any target service deployment device in real time, so as to obtain the instance status identifier of the target service instance on any target service deployment device in real time; then correspondingly, the monitoring component in any target service deployment device can send the instance status identifier of the target service instance on any target service deployment device to the name service system in real time, so as to update the instance status identifier of the target service instance on any target service deployment device in the name service system in real time.
[0034] In other implementations, the monitoring component in any target service deployment device may also monitor the target service instance on any target service deployment device at a preset monitoring interval, thereby sending the instance status identifier of the target service instance on any target service deployment device at the current monitoring time to the name service system; optionally, the preset monitoring interval may be set based on experience or actual needs, which is not limited in the embodiments of the present invention. Alternatively, the monitoring component in any target service deployment device may monitor the target service instance on any target service deployment device when receiving a service instance monitoring instruction for the target service instance sent by the name service system, and so on; the present invention does not limit this.
[0035] Optionally, a monitoring component may include an agent (plug-in), so the monitoring component in any target service deployment device may send the instance status identifier of the target service instance on any target service deployment device to the name service system through the agent (i.e., the agent in the corresponding monitoring component). Optionally, the name service system may include a BNS management module (also represented as Server, i.e., a server) for each service in at least one service, and a BNS management module may include a service instance indication information set of the corresponding service; in this case, the monitoring component in any target service deployment device may send the instance status identifier of the target service instance on any target service deployment device to the BNS management module of the target service in the name service system through the agent, so that the BNS management module of the target service in the name service system can store the instance status identifier of the target service instance on any target service deployment device; in this case, the monitoring component in any target service deployment device may report the instance status identifier of the target service instance on any target service deployment device to the BNS management module of the target service through the agent.
[0036] Optionally, when the monitoring component in any target service deployment device sends the instance status identifier of the target service instance on any target service deployment device to the name service system, the monitoring component in any target service deployment device may also send the service instance identifier of the target service instance on any target service deployment device to the name service system, so that the name service system can determine the instance status identifier of the service instance indicated by any service instance identifier through the correspondence between the instance status identifier and the service instance identifier.
[0037] S102: After receiving the instance status identifier of each target service instance of the target service, the name service system stores the instance status identifier of each target service instance.
[0038] In an embodiment of the present invention, the name service system may include a service identifier (such as a service name) of each service in at least one service and a service instance indication information set of each service, etc., which is not limited in the embodiment of the present invention; a service instance indication information may include but is not limited to a service instance identifier, an instance status identifier, etc. of a service instance of a service, which is not limited in the embodiment of the present invention. Based on this, the name service system can determine the service instance indication information set of the service indicated by any service identifier to determine the instance status identifier of each service instance of the service indicated by any service identifier, thereby determining the instance running status of each service instance of any service. A service instance identifier is used to indicate a service instance, and an instance status identifier can be used to indicate an instance running status. Optionally, a service instance identifier may include at least one of the following: the device name and IP of the service deployment device where a service instance is located, the service identifier of the service to which the corresponding service instance belongs, and the instance name of the corresponding service instance, etc., which is not limited in the embodiment of the present invention. Optionally, an instance status identifier can be an instance fault identifier or an instance non-fault identifier. The instance fault identifier can be used to indicate a service instance fault (that is, it can be used to indicate that the corresponding service instance is a faulty service instance), and the instance non-fault identifier can be used to indicate that the service instance is not faulty (that is, it can be used to indicate that the corresponding service instance is a non-faulty service instance). Optionally, both the instance fault identifier and the instance non-fault identifier can be set according to experience or according to actual needs, and the embodiments of the present invention are not limited to this.
[0039] Optionally, when storing the instance status identifier of each target service instance, the instance status identifier of each target service instance may be recorded in the metadata of the target service. Optionally, when the name service system includes a BNS management module for each service in at least one service, the BNS management module of any service may record the instance status identifier of each service instance of any service in the metadata of any service after receiving the instance status identifier of each service instance of any service. In this case, the metadata of any service may be located in the BNS management module of any service.
[0040] S103, the service management middleware receives the instance status identifier of each target service instance sent by the name service system, and based on the instance status identifier of each target service instance, isolates the faulty service instance of the target service, and opens the non-faulty service instance of the target service to the outside to provide the target service. The non-faulty service instance of the target service includes all target service instances except the faulty service instance of the target service in at least one target service instance.
[0041] In the embodiment of the present invention, the service management middleware can be any middleware, such as RPC (Remote Procedure Call Protocol) middleware, etc., which is not limited by the embodiment of the present invention; wherein, the service management middleware can be linked with the operation of the name service system through the API (Application Programming Interface) logic of the built-in name service system. Based on this, the service management middleware can perceive the changes in the instance operation status of any service instance through the API interface of the name service system, that is, it can obtain the instance status identifier of each target service instance through the API interface of the name service system. Optionally, when receiving the instance status identifier of each target service instance, the service management middleware can also receive the service instance identifier of each target service instance.
[0042] Optionally, when the naming service system includes BNS management modules for each service, and a service instance indication information set of a service is stored in the metadata of the BNS management module of the corresponding service, the service management middleware can receive the instance status identifiers of each target service instance sent by the naming service system (such as receiving the instance status identifiers of each target service instance sent by the BNS management module of the target service in the naming service system) by monitoring the metadata changes of the BNS management module of the target service, thereby perceiving the changes in the instance running status of each target service instance.
[0043] In the embodiment of the present invention, the monitoring components in each target service deployment device in at least one target service deployment device can respectively monitor the target service instance on the corresponding target service deployment device, obtain the instance status identifier of the target service instance on the corresponding target service deployment device, and send the instance status identifier of the target service instance on the corresponding target service deployment device to the name service system. After receiving the instance status identifier of each target service instance of the target service, the name service system can store the instance status identifier of each target service instance. The service management middleware can receive the instance status identifier of each target service instance sent by the name service system, and based on the instance status identifier of each target service instance, isolate the faulty service instance of the target service, and open the non-faulty service instance of the target service to the outside to provide the target service, and the non-faulty service instance of the target service includes all target service instances in at least one target service instance except the faulty service instance of the target service. It can be seen that the embodiment of the present invention can achieve the isolation of faulty service instances without manual intervention, so as to avoid developing the faulty service instances to the outside, so that the faulty service instances do not have to take over user traffic; that is to say, the embodiment of the present invention can conveniently perform service management through monitoring components and service management middleware, so as to effectively achieve the isolation of faulty service instances while reducing costs and avoiding misoperation.
[0044] Based on the above description, the embodiment of the present invention further proposes a more specific service management method, which can be applied to a service management system. The service management system may include service management middleware, a name service system, and at least one target service deployment device. A target service deployment device includes a monitoring component and a target service instance in at least one target service instance of a target service; see Figure 2 , the service management method may include the following steps S201-S205:
[0045] S201, the monitoring components in each target service deployment device of at least one target service deployment device respectively monitor the target service instance on the corresponding target service deployment device, obtain the instance status identifier of the target service instance on the corresponding target service deployment device, and send the instance status identifier of the target service instance on the corresponding target service deployment device to the name service system.
[0046] Among them, the monitoring component in a service deployment device supports monitoring each service instance on the corresponding service deployment device. In an embodiment of the present invention, the at least one target service deployment device may include a service deployment device that includes a target service instance of the target service and is not faulty in at least one service deployment device; based on this, when all service deployment devices including the target service instance are not faulty, the at least one target service deployment device may include all service deployment devices in the at least one service deployment device that have the target service instance deployed.
[0047] Optionally, when any service deployment device is a non-faulty service deployment device, the monitoring component in any service deployment device may monitor each service instance on any service deployment device. Optionally, a monitoring component monitoring a service instance may refer to the corresponding monitoring component monitoring the software running state of the corresponding service instance (i.e., the instance running state may be the software running state of the corresponding service instance at this time); accordingly, if a software fault occurs in the service instance and it cannot run, the monitoring component may determine that the instance state identifier of the corresponding service instance is an instance fault identifier.
[0048] Optionally, for any target service deployment device in at least one target service deployment device, the monitoring component in any target service deployment device can monitor the target service instance on any target service deployment device according to each monitoring indicator in at least one monitoring indicator, and obtain the monitoring result of the target service instance on any target service deployment device under each monitoring indicator; that is, it can detect whether a service instance has a software failure according to at least one monitoring indicator. Further, the monitoring component in any target service deployment device can determine the instance state identifier of the target service instance on any target service deployment device based on the monitoring result of the target service instance on any target service deployment device under each monitoring indicator.
[0049] Optionally, at least one monitoring indicator may include a service process monitoring indicator and / or a service port monitoring indicator. Based on this, when determining the instance status identifier of the target service instance on any target service deployment device based on the monitoring results of the target service instance on any target service deployment device under each monitoring indicator, if the monitoring result of the target service instance on any target service deployment device under the service process monitoring indicator is a service process abnormality identifier, and / or the monitoring result of the target service instance on any target service deployment device under the service port monitoring indicator is a service port not normally occupied identifier, the monitoring component in any target service deployment device may use the instance fault identifier as the instance status identifier of the target service instance on any target service deployment device; if the monitoring result of the target service instance on any target service deployment device under each monitoring indicator does not include a service process abnormality identifier and a service port not normally occupied identifier, the instance non-fault identifier is used as the instance status identifier of the target service instance on any target service deployment device.
[0050] It should be understood that if at least one monitoring indicator includes a service process monitoring indicator, then when the monitoring result of the target service instance on any target service deployment device under the service process monitoring indicator is a normal service process indicator, the monitoring result of the target service instance on any target service deployment device under each monitoring indicator does not include an abnormal service process indicator and an abnormal service port occupancy indicator (at this time, the monitoring result of the target service instance on any target service deployment device under each monitoring indicator includes a normal service process indicator); if at least one monitoring indicator includes a service port monitoring indicator, then when the monitoring result of the target service instance on any target service deployment device under the service port monitoring indicator is a normal service port occupancy indicator, the monitoring result of the target service instance on any target service deployment device under each monitoring indicator does not include an abnormal service process indicator and an abnormal service port occupancy indicator. If at least one monitoring indicator includes a service process monitoring indicator and a service port monitoring indicator, then when the monitoring result of the target service instance on any target service deployment device under the service process monitoring indicator is a normal service process indicator, and the monitoring result of the target service instance on any target service deployment device under the service port monitoring indicator is a normal service port indicator, the monitoring result of the target service instance on any target service deployment device under each monitoring indicator does not include an abnormal service process indicator and an abnormal service port indicator (at this time, the monitoring result of the target service instance on any target service deployment device under each monitoring indicator includes a normal service process indicator and a normal service port indicator).
[0051] Among them, a service process normal flag of a service instance under a service process monitoring indicator can be used to indicate that the process of the corresponding service instance is normal, a service process abnormal flag of a service instance under a service process monitoring indicator can be used to indicate that the process of the corresponding service instance is abnormal, a service port normal occupation flag of a service instance under a service port monitoring indicator can be used to indicate that the port of the corresponding service instance is normally occupied by the corresponding service instance, and a service port abnormal occupation flag of a service instance under a service port monitoring indicator can be used to indicate that the port of the corresponding service instance is not normally occupied by the corresponding service instance. Optionally, the service process normal flag, the service process abnormal flag, the service port normal occupation flag, and the service port abnormal occupation flag can all be set according to experience or according to actual needs, and the embodiments of the present invention do not limit this.
[0052] S202: After receiving the instance status identifier of each target service instance of the target service, the name service system stores the instance status identifier of each target service instance.
[0053] S203, when the name service system detects a service deployment device to be detected, the name service system sends a detection instruction to the service deployment device to be detected to initiate detection of the service deployment device to be detected. The service deployment device to be detected is a service deployment device for which the name service system has not received corresponding monitoring information within a preset time period. The monitoring information of a service deployment device includes an instance status identifier of each service instance in at least one service instance on the corresponding service deployment device.
[0054] For any target service deployment device among the at least one target service deployment device, the monitoring information of any target service deployment device may include an instance state identifier of a target service instance on any target service deployment device.
[0055] Optionally, the preset duration can be set according to experience or according to actual needs, and the embodiment of the present invention does not limit this. Based on this, when the name service system does not receive monitoring information sent by the monitoring component in any service deployment device within the preset duration, any service deployment device can be used as a service deployment device to be detected.
[0056] Accordingly, when the name service system fails to receive monitoring information of any service deployment device for a period of time (ie, a preset time period), the name service system may initiate detection of any service deployment device.
[0057] S204, after the name service system fails to detect the service deployment device to be detected, the name service system marks the service deployment device to be detected as a failure state, and uses the instance failure identifier as the instance state identifier of each service instance on the service deployment device to be detected.
[0058] In the embodiment of the present invention, after the name service system sends a detection instruction to the service deployment device to be detected, if the name service system does not receive the detection response information returned by the service deployment device to be detected within the preset detection waiting time, the name service system can determine that the detection of the service deployment device to be detected has failed. Optionally, the preset detection waiting time and the detection response information can be set according to experience or according to actual needs, which is not limited in the embodiment of the present invention.
[0059] Based on this, the name service deployment system can mark the instance running status of all service instances on the service deployment device marked as a faulty state (i.e., the faulty service deployment device) as a faulty state, so that the instance state identifiers of all service instances on the service deployment device marked as a faulty state will change accordingly, that is, the instance running status of all service instances on the service deployment device marked as a faulty state will also change accordingly.
[0060] In summary, when a service deployment device exits due to a failure, the monitoring component in the corresponding service deployment device is also affected by the failure and cannot timely report the instance running status of the service instance on the corresponding service deployment device (that is, it cannot timely report the instance status identifier of the service instance on the corresponding service deployment device). At this time, the automatic detection of the name service system can be used to determine whether the service deployment device to be detected is faulty, so as to timely monitor the service instance failure on the faulty service deployment device.
[0061] S205, the service management middleware receives the instance status identifier of each target service instance sent by the name service system, and based on the instance status identifier of each target service instance, isolates the faulty service instance of the target service, and opens the non-faulty service instance of the target service to the outside to provide the target service. The non-faulty service instances of the target service include all target service instances except the faulty service instance of the target service in at least one target service instance.
[0062] Optionally, when isolating faulty service instances of the target service based on the instance status identifiers of each target service instance, for any target service instance of the target service, if the instance status identifier of any target service instance is an instance fault identifier, the service management middleware may treat any target service instance as a faulty service instance of the target service and isolate any target service instance to isolate the faulty service instance of the target service; if the instance status identifier of any target service instance is an instance non-fault identifier, any target service instance may be treated as a non-faulty service instance of the target service, and any target service instance will not be isolated, so as to trigger the execution of opening any target service instance to the outside.
[0063] In an embodiment of the present invention, the service management middleware may open the instance information (such as the service instance identifier, etc.) of the non-faulty service instance of the target service to the required service (such as the upstream service that accesses the target service) to ensure that the user traffic can access the non-faulty service instance of the target service. Figure 3 As shown, service 1, service 2 and service 3 can all be upstream services, service A can be a target service, and service A-1, service A-2 and service A-3 can all be target service instances of the target service. Optionally, the number of non-faulty service instances of the target service can be one or more, which is not limited in the embodiment of the present invention.
[0064] Optionally, the instance status identifier of any target service instance of the target service at the first monitoring time is an instance failure identifier, and the instance status identifier of any target service instance at the second monitoring time is an instance non-fault identifier; based on this, after receiving the instance status identifier of any target service instance at the first monitoring time, the service management middleware can treat any target service instance as a faulty service instance of the target service; after receiving the instance status identifier of any target service instance at the second monitoring time, the service management middleware can treat any target service instance as a non-faulty service instance of the target service. Based on this, the embodiment of the present invention can enable the service instance to normally accept user traffic in a timely manner after the faulty service instance is restored.
[0065] Correspondingly, the service management middleware can receive the newly added service instance identifier of the target service sent by the name service system, and the newly added service instance identifier can be used to indicate the newly added service instance of the target service; based on this, the service management middleware can use the newly added service instance of the target service as a non-faulty service instance of the target service based on the newly added service instance identifier, thereby realizing opening the newly added service instance of the target service to the outside to provide the target service, that is, the newly added service instance indicated by the newly added service instance identifier can be opened to the upstream service. Optionally, when the instance state identifier of any service instance identifier in the service management middleware is empty or any service instance identifier has a newly added identifier, it can be determined that any service instance identifier is a newly added service instance identifier, that is, it can be determined that the service instance indicated by any service instance identifier is a newly added service instance identifier; optionally, the newly added identifier can be set according to experience or according to actual needs, and the embodiment of the present invention does not limit this. Optionally, the name service system can respond to the service instance addition operation performed by the service management object (such as the management personnel) on the target service to determine the newly added service instance identifier of the target service, and then the name service system can send the newly added service instance identifier to the service management middleware.
[0066] From the above, it can be seen that no matter whether the service instance of the service is newly started or the faulty service instance is restored, the embodiment of the present invention can ensure that the service instance is determined to be in an open state, so that it can normally accept user traffic. Based on this, the embodiment of the present invention can achieve that in the service instance failure scenario, without manual intervention, the faulty service instance can be isolated and stopped to prevent user traffic from continuously accessing the faulty service instance; after the faulty service instance is restored, the restored service instance can be automatically opened to ensure that the service instance can be restored in time without manual intervention, etc.
[0067] In the embodiment of the present invention, the monitoring components in each target service deployment device in at least one target service deployment device can monitor the target service instance on the corresponding target service deployment device respectively, obtain the instance status identifier of the target service instance on the corresponding target service deployment device, and send the instance status identifier of the target service instance on the corresponding target service deployment device to the name service system. After receiving the instance status identifier of each target service instance of the target service, the name service system stores the instance status identifier of each target service instance. Among them, the monitoring component in a service deployment device supports monitoring each service instance on the corresponding service deployment device. Further, when the name service system detects the service deployment device to be detected, it can send a detection instruction to the service deployment device to be detected to initiate detection of the service deployment device to be detected. The service deployment device to be detected is a service deployment device for which the name service system has not received corresponding monitoring information within a preset time period. The monitoring information of a service deployment device includes the instance status identifier of each service instance in at least one service instance on the corresponding service deployment device; accordingly, after the name service system fails to detect the service deployment device to be detected, it marks the service deployment device to be detected as a fault state, and uses the instance fault identifier as the instance status identifier of each service instance on the service deployment device to be detected. Based on this, the service management middleware receives the instance status identifiers of each target service instance sent by the name service system, and based on the instance status identifiers of each target service instance, isolates the faulty service instances of the target service, and opens the non-faulty service instances of the target service to the outside to provide the target service. The non-faulty service instances of the target service include all target service instances except the faulty service instance of the target service in at least one target service instance. It can be seen that the embodiment of the present invention can call the name service system through the service management middleware to determine whether the service instance provides services to the outside (such as determining whether a target service instance provides target services to the outside) by judging the instance running status of the service instance (such as faulty or not); based on this, if a service instance of a service fails, the service management middleware can quickly determine the instance running status of the faulty service instance (which is a faulty state at this time) and isolate it, thereby preventing upstream services from accessing the faulty service instance; and, when the faulty service instance is restored, the service management middleware can also automatically determine and release the isolation, so that the released service instance can resume opening to the outside to provide services, that is, the restored service instance can re-accept the user's traffic; or, when a new service instance of the service is online, the service management middleware will automatically sense it and open the new service instance to the outside to provide services, that is, the new service instance can re-accept the user's traffic.Based on this, the embodiments of the present invention can automatically perform service management through the service management middleware without human intervention, which can effectively improve the response speed, improve the continuity of services, reduce labor costs, and provide better data consistency to avoid omissions, errors, etc. caused by manual operations.
[0068] Based on the description of the above-mentioned service management method, the embodiment of the present invention further proposes a service management system; Figure 4 As shown, the service management system may include at least one target service deployment device 401, a name service system 402, and a service management middleware 403. A target service deployment device 401 includes a monitoring component and a target service instance in at least one target service instance of the target service. The service management system may execute Figure 1 or Figure 2 The service management method shown, that is, the service management system can run the above units:
[0069] The monitoring component in each target service deployment device 401 of at least one target service deployment device 401 is used to monitor the target service instance on the corresponding target service deployment device, obtain the instance state identifier of the target service instance on the corresponding target service deployment device, and send the instance state identifier of the target service instance on the corresponding target service deployment device to the name service system;
[0070] The name service system 402 is used to store the instance status identifier of each target service instance of the target service after receiving the instance status identifier of each target service instance of the target service;
[0071] The service management middleware 403 is used to receive the instance status identifiers of the various target service instances sent by the name service system, and based on the instance status identifiers of the various target service instances, isolate the faulty service instances of the target service, and open the non-faulty service instances of the target service to the outside to provide the target service. The non-faulty service instances of the target service include all target service instances in the at least one target service instance except the faulty service instance of the target service.
[0072] In one implementation, the monitoring component in each target service deployment device 401 of the at least one target service deployment device 401 monitors the target service instance on the corresponding target service deployment device respectively, and obtains the instance state identifier of the target service instance on the corresponding target service deployment device, which can be specifically used to:
[0073] For any target service deployment device 402 in the at least one target service deployment device 401, the monitoring component in any target service deployment device 402 is used to monitor the target service instance on the any target service deployment device according to each monitoring indicator in at least one monitoring indicator, and obtain the monitoring result of the target service instance on the any target service deployment device under each monitoring indicator;
[0074] The monitoring component in any target service deployment device 401 is used to determine the instance state identifier of the target service instance on any target service deployment device based on the monitoring results of the target service instance on any target service deployment device under the various monitoring indicators.
[0075] In another embodiment, at least one monitoring indicator includes a service process monitoring indicator and / or a service port monitoring indicator. When the monitoring component in any target service deployment device 401 determines the instance state identifier of the target service instance on any target service deployment device based on the monitoring result of the target service instance on the any target service deployment device under the respective monitoring indicators, it can be specifically used to:
[0076] If the monitoring result of the target service instance on any target service deployment device under the service process monitoring indicator is a service process abnormality mark, and / or the monitoring result of the target service instance on any target service deployment device under the service port monitoring indicator is a service port not normally occupied mark, then the instance fault mark is used as the instance state mark of the target service instance on any target service deployment device;
[0077] If the monitoring results of the target service instance on any target service deployment device under the various monitoring indicators do not include the service process abnormality flag and the service port abnormal occupation flag, the instance non-fault flag is used as the instance status flag of the target service instance on any target service deployment device.
[0078] In another implementation manner, when isolating the faulty service instance of the target service based on the instance status identifier of each target service instance, the service management middleware 403 may be specifically used to:
[0079] For any target service instance of the target service, if the instance status identifier of any target service instance is an instance fault identifier, the any target service instance is regarded as a faulty service instance of the target service, and the any target service instance is isolated, so as to isolate the faulty service instance of the target service;
[0080] If the instance status identifier of any target service instance is an instance non-fault identifier, then any target service instance is treated as a non-faulty service instance of the target service and is not isolated to trigger the execution of opening any target service instance to the outside.
[0081] In another embodiment, a service deployment device supports deployment of a service instance of each service in at least one service, and a monitoring component in a service deployment device supports monitoring each service instance on the corresponding service deployment device;
[0082] The name service system 402 may also be used to send a detection instruction to the service deployment device to be detected when detecting the service deployment device to be detected, so as to initiate detection of the service deployment device to be detected, wherein the service deployment device to be detected is a service deployment device for which the name service system has not received corresponding monitoring information within a preset time period, and the monitoring information of a service deployment device includes an instance state identifier of each service instance in at least one service instance on the corresponding service deployment device;
[0083] The name service system 402 may also be configured to mark the service deployment device to be detected as a failure state after detection of the service deployment device to be detected fails, and use the instance failure identifier as the instance state identifier of each service instance on the service deployment device to be detected.
[0084] In another implementation manner, the instance state identifier of any target service instance of the target service at the first monitoring time is an instance failure identifier, and the instance state identifier of any target service instance at the second monitoring time is an instance non-failure identifier;
[0085] The service management middleware 403 may also be used to, after receiving the instance status identifier of any target service instance at the first monitoring time, use any target service instance as a faulty service instance of the target service;
[0086] The service management middleware 403 may also be configured to, after receiving the instance status identifier of any target service instance at the second monitoring time, use the any target service instance as a non-faulty service instance of the target service.
[0087] In another implementation manner, the service management middleware 403 may also be used to receive a newly added service instance identifier of the target service sent by the name service system, where the newly added service instance identifier is used to indicate a newly added service instance of the target service;
[0088] The service management middleware 403 may also be used to use the newly added service instance of the target service as a non-faulty service instance of the target service based on the newly added service instance identifier, thereby opening the newly added service instance of the target service to the outside to provide the target service.
[0089] According to one embodiment of the present invention, Figure 4 Each unit in the service management system shown can be separately or completely combined into one or several other units to form, or one (some) of the units can be further divided into multiple smaller units in function to form, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units are divided based on logical functions. In practical applications, the functions of one unit can also be implemented by multiple units, or the functions of multiple units can be implemented by one unit. In other embodiments of the present invention, any service management system may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by the collaboration of multiple units.
[0090] In the embodiment of the present invention, the monitoring components in each target service deployment device in at least one target service deployment device can respectively monitor the target service instance on the corresponding target service deployment device, obtain the instance status identifier of the target service instance on the corresponding target service deployment device, and send the instance status identifier of the target service instance on the corresponding target service deployment device to the name service system. After receiving the instance status identifier of each target service instance of the target service, the name service system can store the instance status identifier of each target service instance. The service management middleware can receive the instance status identifier of each target service instance sent by the name service system, and based on the instance status identifier of each target service instance, isolate the faulty service instance of the target service, and open the non-faulty service instance of the target service to the outside to provide the target service, and the non-faulty service instance of the target service includes all target service instances in at least one target service instance except the faulty service instance of the target service. It can be seen that the embodiment of the present invention can achieve the isolation of faulty service instances without manual intervention, so as to avoid developing the faulty service instances to the outside, so that the faulty service instances do not have to take over user traffic; that is to say, the embodiment of the present invention can conveniently perform service management through monitoring components and service management middleware, so as to effectively achieve the isolation of faulty service instances while reducing costs and avoiding misoperation.
[0091] Based on the description of the above method embodiments and system embodiments, an exemplary embodiment of the present invention also provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to enable the computer to perform a method according to an embodiment of the present invention.
[0092] An exemplary embodiment of the present invention further provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor of a computer, the computer is used to enable the computer to perform a method according to an embodiment of the present invention.
[0093] An exemplary embodiment of the present invention also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor, the memory storing a computer program that can be executed by the at least one processor; wherein the electronic device is used to constitute a service management system, and the electronic device is used to enable the service management system to execute a method according to an embodiment of the present invention.
[0094] refer to Figure 5 , a block diagram of an electronic device 500 that can be used as a server or client of the present invention will now be described, which is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.
[0095] like Figure 5 As shown, the electronic device 500 includes a computing unit 501, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 502 or a computer program loaded from a storage unit 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 can also be stored. The computing unit 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.
[0096] A plurality of components in the electronic device 500 are connected to the I / O interface 505, including: an input unit 506, an output unit 507, a storage unit 508, and a communication unit 509. The input unit 506 may be any type of device capable of inputting information to the electronic device 500, and the input unit 506 may receive input digital or character information, and generate key signal inputs related to user settings and / or function control of the electronic device. The output unit 507 may be any type of device capable of presenting information, and may include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 508 may include, but is not limited to, a disk, an optical disk. The communication unit 509 allows the electronic device 500 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks, and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chipset, such as a Bluetooth™ device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.
[0097] The computing unit 501 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 501 performs the various methods and processes described above. For example, in some embodiments, the service management method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 500 via the ROM 502 and / or the communication unit 509. In some embodiments, the computing unit 501 may be configured to execute the service management method in any other appropriate manner (e.g., by means of firmware).
[0098] The program code for implementing the method of the present invention can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.
[0099] In the context of the present invention, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0100] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.
[0101] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0102] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.
[0103] A computer system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.
[0104] Furthermore, it should be understood that what is disclosed above is only a preferred embodiment of the present invention, and certainly cannot be used to limit the scope of rights of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.
Claims
1. A service management method, characterized in that: The method is applied to a service management system, the service management system includes service management middleware, a name service system and at least one target service deployment device, a target service deployment device includes a monitoring component and a target service instance in at least one target service instance of a target service, the method includes: The monitoring component in each target service deployment device of the at least one target service deployment device monitors the target service instance on the corresponding target service deployment device respectively, obtains the instance state identifier of the target service instance on the corresponding target service deployment device, and sends the instance state identifier of the target service instance on the corresponding target service deployment device to the name service system; After receiving the instance status identifiers of the target service instances, the name service system stores the instance status identifiers of the target service instances; The service management middleware receives the instance status identifiers of the target service instances sent by the name service system, and based on the instance status identifiers of the target service instances, isolates the faulty service instances of the target service, and opens the non-faulty service instances of the target service to the outside to provide the target service. The non-faulty service instances of the target service include all target service instances among the at least one target service instance except the faulty service instance of the target service.
2. The method according to claim 1, characterized in that The monitoring component in each target service deployment device of the at least one target service deployment device monitors the target service instance on the corresponding target service deployment device respectively, and obtains the instance state identifier of the target service instance on the corresponding target service deployment device, including: For any target service deployment device among the at least one target service deployment device, the monitoring component in the any target service deployment device monitors the target service instance on the any target service deployment device according to each monitoring indicator among the at least one monitoring indicator, and obtains the monitoring result of the target service instance on the any target service deployment device under the each monitoring indicator; The monitoring component in any target service deployment device determines the instance state identifier of the target service instance on any target service deployment device based on the monitoring results of the target service instance on any target service deployment device under the various monitoring indicators.
3. The method according to claim 2, characterized in that The at least one monitoring indicator includes a service process monitoring indicator and / or a service port monitoring indicator, and the determining the instance state identifier of the target service instance on any target service deployment device based on the monitoring result of the target service instance on any target service deployment device under each monitoring indicator includes: If the monitoring result of the target service instance on any target service deployment device under the service process monitoring indicator is a service process abnormality mark, and / or the monitoring result of the target service instance on any target service deployment device under the service port monitoring indicator is a service port not normally occupied mark, then the instance fault mark is used as the instance state mark of the target service instance on any target service deployment device; If the monitoring results of the target service instance on any target service deployment device under the various monitoring indicators do not include the service process abnormality flag and the service port abnormal occupation flag, the instance non-fault flag is used as the instance status flag of the target service instance on any target service deployment device.
4. The method according to any one of claims 1 to 3, characterized in that: The isolating the faulty service instance of the target service based on the instance status identifier of each target service instance includes: For any target service instance of the target service, if the instance status identifier of any target service instance is an instance fault identifier, the any target service instance is regarded as a faulty service instance of the target service, and the any target service instance is isolated, so as to isolate the faulty service instance of the target service; If the instance status identifier of any target service instance is an instance non-fault identifier, then any target service instance is treated as a non-faulty service instance of the target service and is not isolated to trigger the execution of opening any target service instance to the outside.
5. The method according to any one of claims 1 to 3, characterized in that: A service deployment device supports deployment of a service instance of each service in at least one service, a monitoring component in a service deployment device supports monitoring each service instance on the corresponding service deployment device, and the method further includes: When the name service system detects a service deployment device to be detected, the name service system sends a detection instruction to the service deployment device to be detected, so as to initiate detection of the service deployment device to be detected, wherein the service deployment device to be detected is a service deployment device for which the name service system has not received corresponding monitoring information within a preset time period, and the monitoring information of a service deployment device includes an instance state identifier of each service instance in at least one service instance on the corresponding service deployment device; After the name service system fails to detect the service deployment device to be detected, the name service system marks the service deployment device to be detected as a failure state, and uses the instance failure identifier as the instance state identifier of each service instance on the service deployment device to be detected.
6. The method according to any one of claims 1 to 3, characterized in that: The instance state identifier of any target service instance of the target service at the first monitoring time is an instance failure identifier, and the instance state identifier of any target service instance at the second monitoring time is an instance non-failure identifier, the method further includes: After receiving the instance status identifier of any target service instance at the first monitoring time, the service management middleware regards any target service instance as a faulty service instance of the target service; After receiving the instance state identifier of any target service instance at the second monitoring time, the service management middleware regards any target service instance as a non-faulty service instance of the target service.
7. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The service management middleware receives a newly added service instance identifier of the target service sent by the name service system, where the newly added service instance identifier is used to indicate a newly added service instance of the target service; Based on the newly added service instance identifier, the service management middleware uses the newly added service instance of the target service as a non-faulty service instance of the target service, thereby opening the newly added service instance of the target service to the outside to provide the target service.
8. A service management system, characterized in that: The service management system includes service management middleware, a name service system and at least one target service deployment device, wherein a target service deployment device includes a monitoring component and a target service instance in at least one target service instance of a target service, and the service management system includes: The monitoring component in each target service deployment device of the at least one target service deployment device is used to monitor the target service instance on the corresponding target service deployment device, obtain the instance state identifier of the target service instance on the corresponding target service deployment device, and send the instance state identifier of the target service instance on the corresponding target service deployment device to the name service system; The name service system is used to store the instance status identifiers of each target service instance of the target service after receiving the instance status identifiers of each target service instance of the target service; The service management middleware is used to receive the instance status identifiers of the target service instances sent by the name service system, and based on the instance status identifiers of the target service instances, isolate the faulty service instances of the target service, and open the non-faulty service instances of the target service to the outside to provide the target service. The non-faulty service instances of the target service include all target service instances among the at least one target service instance except the faulty service instance of the target service.
9. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to make a computer execute the method according to any one of claims 1-7.
