CN114157551A - Fusing identification method, device, equipment and storage medium suitable for micro-service - Google Patents
Fusing identification method, device, equipment and storage medium suitable for micro-service Download PDFInfo
- Publication number
- CN114157551A CN114157551A CN202111436716.2A CN202111436716A CN114157551A CN 114157551 A CN114157551 A CN 114157551A CN 202111436716 A CN202111436716 A CN 202111436716A CN 114157551 A CN114157551 A CN 114157551A
- Authority
- CN
- China
- Prior art keywords
- fusing
- target
- threshold
- service
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
- H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Telephonic Communication Services (AREA)
- Hardware Redundancy (AREA)
Abstract
The application relates to the technical field of micro services, and discloses a fusing identification method, a fusing identification device, fusing identification equipment and a storage medium suitable for micro services, wherein the method comprises the following steps: monitoring a single service call request received by a target micro service interface in real time; judging whether the target call link attribute corresponding to the single service call request is a core or not; if not, fusing and identifying the single service calling request by adopting the acquired first fusing trigger condition corresponding to the target micro-service interface to obtain a fusing and identifying result; and if so, carrying out fusing identification on the single service calling request by adopting the acquired second fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result. The method and the device realize fusing identification of the micro-service interface based on the calling link attribute corresponding to the single service calling request, avoid request overstock, avoid blockage of associated micro-service and ensure the execution stability of the core calling link.
Description
Technical Field
The present application relates to the field of micro-services, and in particular, to a method, an apparatus, a device, and a storage medium for identifying a fuse applicable to a micro-service.
Background
With the development of internet technology, micro-service architecture is widely applied. In the micro-service architecture, a large amount of micro-services provide services, and the micro-services are mutually dependent and chained to be called. When a micro service is abnormal, the request backlog is caused, the related micro service is blocked, and the stability of the system is influenced.
Disclosure of Invention
The application mainly aims to provide a fusing identification method, a fusing identification device, fusing identification equipment and a fusing identification storage medium suitable for micro services, and aims to solve the technical problems that in a micro service architecture, massive micro services provide services, the micro services are mutually dependent and chained to be called, and when the micro services are abnormal, requests are overstocked, the related micro services are blocked, and the stability of a system is influenced.
In order to achieve the above object, the present application provides a method for identifying a fuse applicable to a microservice, the method comprising:
monitoring a single service call request received by a target micro service interface in real time;
acquiring a target call link attribute corresponding to the single service call request;
judging whether the target call link attribute is a core or not;
if not, fusing and identifying the single service calling request by adopting the acquired first fusing trigger condition corresponding to the target micro-service interface to obtain a fusing and identifying result;
and if so, carrying out fusing identification on the single service calling request by adopting the acquired second fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result.
Further, the step of performing fusing identification on the single service invocation request by using the acquired first fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result includes:
acquiring the first fusing trigger condition, a first processing request number and a first window processing request total number in a preset first time length corresponding to the target micro service interface;
determining whether the first number of on-going processing requests is greater than a first on-going processing request threshold in the first fusing trigger condition and whether the first window processing request total number is greater than a first window request number threshold in the first fusing trigger condition;
if not, determining that the fusing identification result is not fusing;
and if any one is yes, determining that the fusing identification result is fusing.
Further, if any one of the results is yes, the step of determining that the fusing recognition result is fusing includes:
if any one is yes, acquiring a target dependency relationship attribute corresponding to the target microservice interface;
if the target dependency relationship attribute is weak, determining that the fusing identification result is fusing;
if the target dependency attribute is strong, determining whether the first number of processing requests is greater than a second threshold number of processing requests in the first fusing trigger condition, and determining whether the total number of processing requests of the first window is greater than the second threshold number of window requests in the first fusing trigger condition;
and if so, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing.
Further, the step of performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target micro service interface to obtain the fusing identification result includes:
acquiring the second fusing trigger condition, a second processing request number and a second window processing request total number in a preset second time length corresponding to the target micro service interface;
determining whether the second number of processing requests is greater than a third number of processing requests threshold in the second fusing trigger condition, and determining whether the second total number of window processing requests is greater than a third number of window requests threshold in the second fusing trigger condition, wherein the third number of processing requests threshold is greater than the first number of processing requests threshold in the first fusing trigger condition, and the third number of window requests threshold is greater than the first number of window requests threshold in the first fusing trigger condition;
if not, determining that the fusing identification result is not fusing;
and if any one is yes, determining that the fusing identification result is fusing.
Further, if any one of the results is yes, the step of determining that the fusing recognition result is fusing includes:
if any one is yes, acquiring a target dependency relationship attribute corresponding to the target micro-service interface;
if the target dependency attribute is weak, determining whether the second number of processing requests is greater than a fourth threshold number of processing requests in the second fusing trigger condition, and determining whether the total number of the second window processing requests is greater than a fourth threshold number of window requests in the second fusing trigger condition, if both, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing, wherein the fourth threshold number of window requests is greater than the second threshold number of window requests in the first fusing trigger condition, and the fourth threshold number of processing requests is greater than the second threshold number of processing requests in the first fusing trigger condition;
if the target dependency relationship attribute is strong, determining whether the second number of processing requests is greater than a fifth threshold of processing requests in the second fusing trigger condition, and determining whether the total number of processing requests of the second window is greater than a fifth threshold of the number of processing requests in the second fusing trigger condition, if both, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing, wherein the fifth threshold of the number of processing requests is greater than the fourth threshold of the number of processing requests, and the fifth threshold of the processing requests is greater than the fourth threshold of the processing requests.
Further, after the step of performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target micro service interface to obtain the fusing identification result, the method further includes:
when the fusing identification result is that the fusing is not conducted, acquiring a target response duration corresponding to the single service calling request;
judging whether the target response time length is greater than a preset response time length threshold value or not;
and if the response time length is larger than the response time length threshold, determining that the fusing identification result is fusing.
Further, after the step of performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target micro service interface to obtain the fusing identification result, the method further includes:
when the fusing identification result is fusing, setting the service state of the target micro-service interface to be closed;
acquiring a first interval time from the latest updating time of the fusing identification result to the current time, a target slow calling proportion corresponding to the target micro-service interface and a target abnormal thread proportion, judging whether the first interval time is greater than a preset first interval time threshold, judging whether the target slow calling proportion is less than a preset slow calling proportion threshold and judging whether the target abnormal thread proportion is less than a preset abnormal thread proportion threshold;
if yes, setting the service state of the target micro-service interface to be semi-open;
acquiring the service state of the target micro-service interface, determining the service state as a second interval duration between the semi-open time and the current time, and judging whether the second interval duration is greater than a preset second interval duration threshold value;
and if the service state of the target micro service interface is larger than the second interval duration threshold, setting the service state of the target micro service interface to be fully open.
The present application further proposes a fuse identification device suitable for micro-services, the device comprising:
the request acquisition module is used for monitoring the single service call request received by the target micro-service interface in real time;
a target call link attribute determining module, configured to obtain a target call link attribute corresponding to the single service call request;
the judging module is used for judging whether the target call link attribute is a core or not;
the first fusing identification module is used for carrying out fusing identification on the single service calling request by adopting the acquired first fusing triggering condition corresponding to the target micro-service interface if the single service calling request is not received, so as to obtain a fusing identification result;
and if so, performing fusing identification on the single service calling request by adopting the acquired second fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result.
The present application further proposes a computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the steps of any of the above methods when executing the computer program.
The present application also proposes a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method of any of the above.
The method, the device, the equipment and the storage medium for identifying the fusing of the micro-service interface realize the fusing identification of the micro-service interface based on the calling link attribute corresponding to the single service calling request, and timely fuse when the micro-service interface responds to the request and is abnormal, so that the request overstock is avoided, and the blocking of the associated micro-service is avoided; and when the calling link attribute is a non-core, the first fusing trigger condition is adopted, and when the calling link attribute is a core, the second fusing trigger condition is adopted, so that the response of the calling link of the core is preferentially ensured, and the execution stability of the calling link of the core is ensured.
Drawings
FIG. 1 is a flowchart illustrating a method for identifying a fuse for a microservice according to an embodiment of the present disclosure;
FIG. 2 is a block diagram illustrating a structure of a fuse identification device for micro services according to an embodiment of the present disclosure;
fig. 3 is a block diagram illustrating a structure of a computer device according to an embodiment of the present application.
The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Referring to fig. 1, in an embodiment of the present application, a method for identifying a fuse applicable to a micro service is provided, where the method includes:
s1: monitoring a single service call request received by a target micro service interface in real time;
s2: acquiring a target call link attribute corresponding to the single service call request;
s3: judging whether the target call link attribute is a core or not;
s4: if not, fusing and identifying the single service calling request by adopting the acquired first fusing trigger condition corresponding to the target micro-service interface to obtain a fusing and identifying result;
s5: and if so, carrying out fusing identification on the single service calling request by adopting the acquired second fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result.
The method and the device realize fusing identification of the micro-service interface based on the calling link attribute corresponding to the single service calling request, and timely fuse when the micro-service interface responds to the request and is abnormal, so that request overstock is avoided, and related micro-service blockage is avoided; and when the calling link attribute is a non-core, the first fusing trigger condition is adopted, and when the calling link attribute is a core, the second fusing trigger condition is adopted, so that the response of the calling link of the core is preferentially ensured, and the execution stability of the calling link of the core is ensured.
S1 may be a single service call request sent to the target micro service interface by another micro service in the same micro service architecture, or a single service call request sent to the target micro service interface by a system other than the server.
The target micro-service interface is an interface in the micro-service. It will be appreciated that one or more interfaces may be provided per microservice.
The single service call request is a request for calling a microservice providing software service.
For step S2, performing call link identifier matching on the request identifier carried by the single service call request in a preset call link table, and taking a call link attribute corresponding to the matched call link identifier as the target call link attribute.
Invoking the link table includes: a request identification, a call link identification, and a call link attribute. The call link identifier is a call link ID for uniquely identifying a call link. Invoking the link attributes includes: a core and a non-core. The request identification, which is a request ID, is used to uniquely identify a request.
The call link corresponding to the call link attribute as the core is a flow that affects the processing result of the service. For example, when the application is applied to the automobile insurance industry, the processing flow of the task of investigating and determining damage of automobile claims is an important flow for generating business results, and therefore the calling link attribute of the flow is the core.
The call link corresponding to the call link attribute of the non-core is a flow which does not affect the processing result of the service. For example, when the application is applied to the car insurance industry, the display flow of the customer identifier is a flow that does not affect the processing result of the car claims service, and the display flow of the customer identifier may be optional, so that the calling link attribute of the display flow of the customer identifier is non-core.
Optionally, the step of obtaining the target call link attribute corresponding to the single service call request includes: acquiring the number of calling link abnormal threads corresponding to the single service calling request; judging whether the calling link abnormal thread number is larger than a preset single link abnormal thread number threshold value or not; if the number of the abnormal threads of the single link is larger than the threshold value, determining that the fusing identification result is fusing; and if the number of the single-link abnormal threads is not greater than the threshold value, acquiring a target call link attribute corresponding to the single-service call request. Therefore, the single service calling request of the calling link with the abnormal thread number exceeding the threshold value is directly set to be fused, and the invalid consumption of the abnormal calling link to resources is avoided.
The number of exceptional threads of the call link is the total number of exceptional threads of the call link.
For S3, it is determined whether the target call link attribute value is a core, and it is also determined whether the single service call request is a request sent by a call link of the core.
For S4, if no, it means that the single service invocation request is a request of a non-core invocation link, so that the first fusing trigger condition corresponding to the target micro service interface may be obtained from a database, or the first fusing trigger condition corresponding to the target micro service interface may be obtained from a third-party application system, or the first fusing trigger condition corresponding to the target micro service interface may be written into a program implementing the present application.
And judging whether the parameter corresponding to the single service call request meets the first fusing triggering condition, if so, determining that the fusing identification result is fusing, and if not, determining that the fusing identification result is not fusing.
If yes, S5 means that the single service invocation request is a request of a core invocation link, and therefore, the second fusing trigger condition corresponding to the target micro service interface may be obtained from a database, or obtained from a third-party application system, or written into a program implementing the present application.
And judging whether the parameters corresponding to the single service call request meet the second fusing triggering condition, if so, determining that the fusing identification result is fusing, and if not, determining that the fusing identification result is not fusing.
And the second fusing trigger condition is used for realizing the priority guarantee of the response to the core calling link and ensuring the execution stability of the core calling link. That is, for the threshold value of the same condition, the value corresponding to the second fusing trigger condition is greater than the value corresponding to the first fusing trigger condition.
In an embodiment, the performing fusing recognition on the single service invocation request by using the obtained first fusing triggering condition corresponding to the target micro service interface to obtain a fusing recognition result includes:
s41: acquiring the first fusing trigger condition, a first processing request number and a first window processing request total number in a preset first time length corresponding to the target micro service interface;
s42: determining whether the first number of on-going processing requests is greater than a first on-going processing request threshold in the first fusing trigger condition and whether the first window processing request total number is greater than a first window request number threshold in the first fusing trigger condition;
s43: if not, determining that the fusing identification result is not fusing;
s44: and if any one is yes, determining that the fusing identification result is fusing.
According to the method and the device, the fusing identification of the single service call request is realized according to the number of the processing requests, the total number of the processing requests of the first window in the preset first duration and the first fusing trigger condition, so that when the number of high concurrent requests is limited, the target micro-service interface is prevented from being in failure due to the fact that the number of the requests needing to be responded is too large.
For S41, the first fusing triggering condition corresponding to the target micro service interface may be obtained from a database, or the first fusing triggering condition corresponding to the target micro service interface may be obtained from a third-party application system, or the first fusing triggering condition corresponding to the target micro service interface may be written in a program implementing the present application.
The first ongoing processing request number corresponding to the target micro service interface may be acquired from a database, or the first ongoing processing request number corresponding to the target micro service interface may be acquired from a monitoring tool or monitoring software.
The first number of requests being processed, i.e., the number of requests being processed by the target microservice interface at the current time.
The total number of the first window processing requests within the preset first time duration corresponding to the target micro service interface may be obtained from a database, or the total number of the first window processing requests within the preset first time duration corresponding to the target micro service interface may be obtained from a monitoring tool or monitoring software.
The first window handles the total number of requests, i.e., the number of requests responded to by the target micro service interface during the history window period immediately preceding the current time (i.e., during the first duration).
For S43, if both are negative, that is, the first number of processing requests is less than or equal to the first threshold of processing requests in the first fusing trigger condition, and the total number of processing requests of the first window is less than or equal to the first threshold of the number of processing requests in the first fusing trigger condition, this means that the fusing requirement corresponding to any one of the first threshold of processing requests and the first threshold of the number of window requests has not been reached yet, so that the fusing identification result is determined to be not fused, so that the target micro service interface normally responds to the single service call request.
For S44, if any one of the two conditions is yes, that is, the first number of in-process requests is greater than the first threshold value of in-process requests in the first fusing trigger condition, or the first total number of window-process requests is greater than the first threshold value of in-window requests in the first fusing trigger condition, this means that the fusing requirement corresponding to at least one of the first threshold value of in-process requests and the first threshold value of window-number of requests has been reached, so that the fusing identification result is determined to be fused, so that the target micro-service interface does not respond to the single-service call request, and the target micro-service interface is prevented from failing due to an excessive number of requests that need to be responded.
In an embodiment, the step S44 of determining that the fusing identification result is fusing if any one of the above is yes, includes:
s441: if any one is yes, acquiring a target dependency relationship attribute corresponding to the target microservice interface;
s442: if the target dependency relationship attribute is weak, determining that the fusing identification result is fusing;
s443: if the target dependency attribute is strong, determining whether the first number of processing requests is greater than a second threshold number of processing requests in the first fusing trigger condition, and determining whether the total number of processing requests of the first window is greater than the second threshold number of window requests in the first fusing trigger condition;
s444: and if so, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing.
In this embodiment, when the number of the first processing requests is greater than the first processing request threshold in the first fusing trigger condition or the total number of the first window processing requests is greater than the first window request number threshold in the first fusing trigger condition, whether the fusing identification result is fused is determined according to the dependency relationship attribute, which is beneficial to avoiding request backlog and avoiding causing blocking of associated micro-services.
For S441, if either is yes, that is, the first number of in-process requests is greater than the first in-process request threshold in the first fusing trigger condition or the first window processing request total number is greater than the first window request number threshold in the first fusing trigger condition, it means that the fusing requirement corresponding to at least one of the first in-process request threshold and the first window request number threshold has been reached, perform dependency attribute matching on the parameter carried by the single service invocation request in a dependency table, and use the matched dependency attribute as the target dependency attribute.
The dependency relationship table includes: the request sender identification is the unique identification of the application sending the request, and the micro-service identification is the unique identification of the micro-service receiving the request sent by the application corresponding to the request sender identification. The dependency attribute has only one value, and the value range of the dependency attribute includes: strong and weak.
And the strong dependency relationship attribute is a service for providing core functions. For example, when the application is applied to a customer service system in the car insurance industry, the core function of the customer service system is customer service, so that the dependency attribute of the user service and the user identification service is strong, and the dependency attribute of the user service and the claim settlement service is weak.
Is a weak dependency attribute and is a service providing non-core functionality. For example, when the application is applied to the insurance system in the automobile insurance industry, the core function of the insurance system is claim settlement, so that the dependency attribute of the user service and the investigation and damage assessment service is weak, and the dependency attribute of the application service and the investigation and damage assessment service is strong.
For S442, if the target dependency attribute is weak, it means that the dependency between the request sender corresponding to the single service invocation request and the micro service corresponding to the target micro service interface is weak, and the execution influence on the call link corresponding to the single service invocation request due to the fusing of the single service invocation request is relatively small, so that it is determined that the fusing identification result is fusing, and the service resource of the micro service is also saved.
For S443, if the target dependency attribute is strong, it means that a dependency between a request sender corresponding to the single service invocation request and the micro service corresponding to the target micro service interface is strong, and the impact on the fusing of the single service invocation request on the execution of the invocation link corresponding to the single service invocation request is large, so that it is determined whether the number of the first ongoing processing requests is greater than a second ongoing processing request threshold in the first fusing trigger condition, and whether the total number of the first window processing requests is greater than a second window request number threshold in the first fusing trigger condition, so as to determine whether the single service invocation request meets the condition of serving with the reserved micro service resource.
Wherein the second in-flight request threshold is greater than the first in-flight request threshold, and the second window request count threshold is greater than the first window request count threshold.
For S444, if yes, that is, the first number of in-flight processing requests is greater than a second threshold of in-flight processing requests in the first fusing trigger condition, and the first total number of window processing requests is greater than the second threshold of in-flight processing requests in the first fusing trigger condition, at this time, the single service invocation request does not meet the condition of performing service by using the reserved micro service resource, and thus, it is determined that the fusing identification result is fused.
If any one of the two conditions is false, that is, the first number of the processing requests is less than or equal to the second threshold value of the processing requests in the first fusing triggering condition, or the total number of the processing requests in the first window is less than or equal to the second threshold value of the processing requests in the first fusing triggering condition, at this time, the single service invocation request meets the condition of adopting the reserved micro service resources for service, and therefore, the fusing recognition result is determined to be not fused.
In an embodiment, the performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target micro service interface to obtain the fusing identification result includes:
s51: acquiring the second fusing trigger condition, a second processing request number and a second window processing request total number in a preset second time length corresponding to the target micro service interface;
s52: determining whether the second number of processing requests is greater than a third number of processing requests threshold in the second fusing trigger condition, and determining whether the second total number of window processing requests is greater than a third number of window requests threshold in the second fusing trigger condition, wherein the third number of processing requests threshold is greater than the first number of processing requests threshold in the first fusing trigger condition, and the third number of window requests threshold is greater than the first number of window requests threshold in the first fusing trigger condition;
s53: if not, determining that the fusing identification result is not fusing;
s54: if any one is yes, determining that the fusing identification result is fusing
According to the embodiment, the fusing recognition of the single service call request is realized according to the number of the processing requests, the total number of the processing requests of the second window in the preset second time and the second fusing trigger condition, so that when the number of high concurrent requests is limited, the target micro-service interface is prevented from being in failure due to the fact that the number of the requests needing to be responded is too large.
For S51, the second fusing triggering condition corresponding to the target micro service interface may be obtained from a database, or the second fusing triggering condition corresponding to the target micro service interface may be obtained from a third-party application system, or the second fusing triggering condition corresponding to the target micro service interface may be written in a program implementing the present application.
The second number of in-process requests corresponding to the target micro service interface may be obtained from a database, or the second number of in-process requests corresponding to the target micro service interface may be obtained from a monitoring tool or monitoring software.
The second number of requests being processed, i.e., the number of requests being processed by the target microservice interface at the current time.
The total number of the second window processing requests within the preset second time duration corresponding to the target micro service interface may be obtained from a database, or the total number of the second window processing requests within the preset second time duration corresponding to the target micro service interface may be obtained from a monitoring tool or monitoring software.
The second window handles the total number of requests, i.e., the number of requests responded to by the target micro service interface during the history window period immediately preceding the current time (i.e., during the second duration).
Optionally, the second duration is equal to the first duration.
For S52, the third ongoing processing request threshold is greater than the first ongoing processing request threshold in the first fusing trigger condition, and the third window request number threshold is greater than the first window request number threshold in the first fusing trigger condition, so as to facilitate serving the call link of the core with the reserved micro service resources, implement priority guarantee of response to the call link of the core, and ensure stability of execution of the call link of the core.
For S53, if both are negative, that is, the second number of processing requests is less than or equal to the third threshold value of processing requests in the second fusing trigger condition, and the total number of processing requests in the second window is less than or equal to the third threshold value of processing requests in the second fusing trigger condition, this means that the fusing requirement corresponding to any one of the third threshold value of processing requests and the third threshold value of window requests has not been reached yet, so that the fusing identification result is determined to be not fused, so that the target micro service interface normally responds to the single service call request.
For S44, if any one of the two results is yes, that is, the second number of processing requests is greater than the third threshold value of the second fusing trigger condition, or the total number of the second window processing requests is greater than the third threshold value of the second fusing trigger condition, this means that the fusing requirement corresponding to at least one of the third threshold value of the processing requests and the third threshold value of the window number has been reached, so that the fusing identification result is determined to be fused, so that the target micro service interface does not respond to the single service call request, and the target micro service interface is prevented from failing due to an excessive number of requests that need to be responded.
In an embodiment, the step S54 of determining that the fusing identification result is fusing if any one of the above is yes, includes:
s541: if any one is yes, acquiring a target dependency relationship attribute corresponding to the target micro-service interface;
s542: if the target dependency attribute is weak, determining whether the second number of processing requests is greater than a fourth threshold number of processing requests in the second fusing trigger condition, and determining whether the total number of the second window processing requests is greater than a fourth threshold number of window requests in the second fusing trigger condition, if both, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing, wherein the fourth threshold number of window requests is greater than the second threshold number of window requests in the first fusing trigger condition, and the fourth threshold number of processing requests is greater than the second threshold number of processing requests in the first fusing trigger condition;
s543: if the target dependency relationship attribute is strong, determining whether the second number of processing requests is greater than a fifth threshold of processing requests in the second fusing trigger condition, and determining whether the total number of processing requests of the second window is greater than a fifth threshold of the number of processing requests in the second fusing trigger condition, if both, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing, wherein the fifth threshold of the number of processing requests is greater than the fourth threshold of the number of processing requests, and the fifth threshold of the processing requests is greater than the fourth threshold of the processing requests.
In this embodiment, when the number of the second ongoing processing requests is greater than the threshold of the third ongoing processing request in the second fusing trigger condition, whether the fusing identification result is fusing is determined according to the total number of the window processing requests in the window period and the dependency relationship attribute, which is beneficial to avoiding request backlog and avoiding causing blocking of associated micro-services.
For S541, if any one of the two is yes, that is, the second number of processing requests is greater than a third threshold of processing requests in the second fusing trigger condition, or the total number of processing requests of the second window is greater than the third threshold of the number of processing requests in the second fusing trigger condition, this means that the fusing request corresponding to at least one of the third threshold of processing requests and the third threshold of the number of requests of the window has been reached, performing dependency attribute matching on the parameter carried by the single service invocation request in a dependency table, and taking the matched dependency attribute as the target dependency attribute.
For S542, if the target dependency attribute is weak, it means that the dependency between the request sender corresponding to the single service invocation request and the micro service corresponding to the target micro service interface is weak, and the impact on the fusing of the single service invocation request on the execution of the invocation link corresponding to the single service invocation request is relatively small.
If the two processing requests are all the same, that is, the second number of processing requests is greater than a fourth threshold of the second fusing triggering condition, and the total number of the second window processing requests is greater than the fourth threshold of the second fusing triggering condition, at this time, the single service invocation request does not meet the condition of using the reserved micro service resources for service, and therefore, the fusing identification result is determined to be fused.
If the second window processing request count is less than or equal to a second current processing request threshold in the second fusing trigger condition, the single service invocation request meets the condition of using the reserved micro-service resource for service, and therefore the fusing identification result is determined to be not fused.
Because the fourth window request number threshold is greater than the second window request number threshold in the first fusing trigger condition, and the fourth ongoing processing request threshold is greater than the second ongoing processing request threshold in the first fusing trigger condition, the method is beneficial to adopting the reserved micro service resources to serve the call link of the core, realizes the preferential guarantee of the response to the call link of the core, and ensures the execution stability of the call link of the core.
For S543, if the target dependency attribute is strong, it means that a request sender corresponding to the single service invocation request and a micro service corresponding to the target micro service interface are strong, and the impact on the execution of the invocation link corresponding to the single service invocation request due to the fusing of the single service invocation request is large, so as to determine whether the number of the second ongoing processing requests is greater than a fifth ongoing processing request threshold in the second fusing trigger condition, and determine whether the total number of the second window processing requests is greater than a fifth window request number threshold in the second fusing trigger condition, so as to determine whether the single service invocation request meets the condition of using the reserved micro service resource for service.
If the two are true, that is, the second number of the processing requests is greater than a fifth threshold of the processing requests in the second fusing trigger condition, and the total number of the processing requests in the second window is greater than a fifth threshold of the processing requests in the second fusing trigger condition, at this time, the single service invocation request does not meet the condition of using the reserved micro service resource for service, and thus, the fusing identification result is determined to be fusing.
If the second window processing request count is not less than the second fusing triggering condition, the second window processing request count is greater than the second fusing triggering condition, or the second window processing request count is greater than the second window processing request count threshold, the single service invocation request meets the condition of using the reserved micro service resources for service, and the fusing identification result is determined to be not fused.
The fifth threshold number of window requests is greater than the fourth threshold number of window requests, and the fifth threshold number of in-flight requests is greater than the fourth threshold number of in-flight requests. The single service invocation request with strong target dependency attribute of the reserved micro-service resource priority service is advantageously adopted.
In an embodiment, after the step of performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target micro service interface to obtain the fusing identification result, the method further includes:
s61: when the fusing identification result is that the fusing is not conducted, acquiring a target response duration corresponding to the single service calling request;
s62: judging whether the target response time length is greater than a preset response time length threshold value or not;
s63: and if the response time length is larger than the response time length threshold, determining that the fusing identification result is fusing.
In this embodiment, when the first fusing triggering condition or the second fusing triggering condition is determined as not fusing, fusing recognition is performed on the single service invocation request according to the response duration threshold, so that request backlog is further avoided, and blocking of associated micro-services is further avoided.
For S61, when the fusing identification result is not fusing, it means that the first fusing trigger condition or the second fusing trigger condition is determined to be not fusing, and the target response duration corresponding to the single service call request may be obtained from a monitoring tool or monitoring software.
For S63, if the response duration is greater than the response duration threshold, that is, the target response duration is greater than the preset response duration threshold, at this time, the response of the target micro service interface to the single service invocation request is overrun, so that it is determined that the fusing recognition result is fusing, and blocking of the associated micro service is avoided.
In an embodiment, after the step of performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target micro service interface to obtain the fusing identification result, the method further includes:
s71: when the fusing identification result is fusing, setting the service state of the target micro-service interface to be closed;
s72: acquiring a first interval time from the latest updating time of the fusing identification result to the current time, a target slow calling proportion corresponding to the target micro-service interface and a target abnormal thread proportion, judging whether the first interval time is greater than a preset first interval time threshold, judging whether the target slow calling proportion is less than a preset slow calling proportion threshold and judging whether the target abnormal thread proportion is less than a preset abnormal thread proportion threshold;
s73: if yes, setting the service state of the target micro-service interface to be semi-open;
s74: acquiring the service state of the target micro-service interface, determining the service state as a second interval duration between the semi-open time and the current time, and judging whether the second interval duration is greater than a preset second interval duration threshold value;
s75: and if the service state of the target micro service interface is larger than the second interval duration threshold, setting the service state of the target micro service interface to be fully open.
When the first fusing triggering condition or the second fusing triggering condition is judged to be fusing, the target micro-service interface is automatically closed and reopened without manual intervention, and the automation degree of the application is improved.
For S71, when the fuse identification result is fuse, it means that the first fuse trigger condition or the second fuse trigger condition is determined to be fuse, and therefore, the service status of the target micro service interface is set to off so as not to receive new requests.
For step S72, a first interval duration between the latest update time of the fusing recognition result and the current time is obtained, and a target slow call proportion and a target abnormal thread proportion corresponding to the target micro service interface are obtained.
The target slow calling proportion is the proportion that the response time length is greater than the maximum response time length in the request processed by the target micro service interface in unit time length.
And the target abnormal thread proportion is the proportion of the abnormality in the thread of the micro service corresponding to the target micro service interface in unit time length.
For S73, if both, that is, the first interval duration is greater than a preset first interval duration threshold, the target slow call proportion is determined to be less than a preset slow call proportion threshold, and the target abnormal thread proportion is determined to be less than a preset abnormal thread proportion threshold, at this time, the fusing duration exceeds the cool-still period (that is, the first interval duration threshold), and at this time, being less than the slow call proportion threshold and the abnormal thread proportion threshold, it means that the target micro service interface has initially recovered the service capability, and therefore, the service state of the target micro service interface is set as semi-open. When the service state of the target micro-service interface is set to be semi-open, requests with strong calling links and dependency relationship attributes of some cores can be processed, so that responses to the requests with strong calling links and dependency relationship attributes of the cores are guaranteed preferentially, and stability of execution of the requests with strong calling links and dependency relationship attributes of the cores is guaranteed.
For S75, if it is greater than the second interval duration threshold, that is, the second interval duration is greater than the second interval duration threshold, this means that a semi-open cold quiet period (second interval duration threshold) is exceeded, so the service status of the target micro-service interface is set to be fully open, so that the target micro-service interface can normally respond to the request.
Referring to fig. 2, the present application also proposes a fuse identification device suitable for micro-services, the device comprising:
the request acquisition module 100 is configured to monitor a single service call request received by a target micro service interface in real time;
a target call link attribute determining module 200, configured to obtain a target call link attribute corresponding to the single service call request;
a judging module 300, configured to judge whether the target call link attribute is a core;
the first fusing recognition module 400 is configured to, if the single service call request is not received, perform fusing recognition on the single service call request by using the acquired first fusing trigger condition corresponding to the target micro service interface to obtain a fusing recognition result;
and the second fusing recognition module 500 is configured to, if yes, perform fusing recognition on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target micro service interface to obtain the fusing recognition result.
The method and the device realize fusing identification of the micro-service interface based on the calling link attribute corresponding to the single service calling request, and timely fuse when the micro-service interface responds to the request and is abnormal, so that request overstock is avoided, and related micro-service blockage is avoided; and when the calling link attribute is a non-core, the first fusing trigger condition is adopted, and when the calling link attribute is a core, the second fusing trigger condition is adopted, so that the response of the calling link of the core is preferentially ensured, and the execution stability of the calling link of the core is ensured.
Referring to fig. 3, a computer device, which may be a server and whose internal structure may be as shown in fig. 3, is also provided in the embodiment of the present application. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the computer designed processor is used to provide computational and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used for storing data such as a fusing identification method suitable for micro services. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method for identifying a fuse for a microservice. The fusing identification method suitable for the micro service comprises the following steps: monitoring a single service call request received by a target micro service interface in real time; acquiring a target call link attribute corresponding to the single service call request; judging whether the target call link attribute is a core or not; if not, fusing and identifying the single service calling request by adopting the acquired first fusing trigger condition corresponding to the target micro-service interface to obtain a fusing and identifying result; and if so, carrying out fusing identification on the single service calling request by adopting the acquired second fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result.
The method and the device realize fusing identification of the micro-service interface based on the calling link attribute corresponding to the single service calling request, and timely fuse when the micro-service interface responds to the request and is abnormal, so that request overstock is avoided, and related micro-service blockage is avoided; and when the calling link attribute is a non-core, the first fusing trigger condition is adopted, and when the calling link attribute is a core, the second fusing trigger condition is adopted, so that the response of the calling link of the core is preferentially ensured, and the execution stability of the calling link of the core is ensured.
An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements a method for identifying a fuse applicable to a micro service, including the steps of: monitoring a single service call request received by a target micro service interface in real time; acquiring a target call link attribute corresponding to the single service call request; judging whether the target call link attribute is a core or not; if not, fusing and identifying the single service calling request by adopting the acquired first fusing trigger condition corresponding to the target micro-service interface to obtain a fusing and identifying result; and if so, carrying out fusing identification on the single service calling request by adopting the acquired second fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result.
The executed fusing identification method suitable for the micro-service realizes fusing identification of the micro-service interface based on the calling link attribute corresponding to the single service calling request, and timely fuses when the micro-service interface responds to the request and is abnormal, so that request overstock is avoided, and related micro-service blockage is avoided; and when the calling link attribute is a non-core, the first fusing trigger condition is adopted, and when the calling link attribute is a core, the second fusing trigger condition is adopted, so that the response of the calling link of the core is preferentially ensured, and the execution stability of the calling link of the core is ensured.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium provided herein and used in the examples may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double-rate SDRAM (SSRSDRAM), Enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and bus dynamic RAM (RDRAM).
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A method for identifying a fuse for a microservice, the method comprising:
monitoring a single service call request received by a target micro service interface in real time;
acquiring a target call link attribute corresponding to the single service call request;
judging whether the target call link attribute is a core or not;
if not, fusing and identifying the single service calling request by adopting the acquired first fusing trigger condition corresponding to the target micro-service interface to obtain a fusing and identifying result;
and if so, carrying out fusing identification on the single service calling request by adopting the acquired second fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result.
2. The method for identifying fusing applicable to microservice according to claim 1, wherein the step of performing fusing identification on the single service invocation request by using the acquired first fusing trigger condition corresponding to the target microservice interface to obtain a fusing identification result comprises:
acquiring the first fusing trigger condition, a first processing request number and a first window processing request total number in a preset first time length corresponding to the target micro service interface;
determining whether the first number of on-going processing requests is greater than a first on-going processing request threshold in the first fusing trigger condition and whether the first window processing request total number is greater than a first window request number threshold in the first fusing trigger condition;
if not, determining that the fusing identification result is not fusing;
and if any one is yes, determining that the fusing identification result is fusing.
3. The method for identifying the fusing of the micro service according to claim 2, wherein if any one of the fusing is yes, the step of determining that the fusing identification result is fusing comprises:
if any one is yes, acquiring a target dependency relationship attribute corresponding to the target microservice interface;
if the target dependency relationship attribute is weak, determining that the fusing identification result is fusing;
if the target dependency attribute is strong, determining whether the first number of processing requests is greater than a second threshold number of processing requests in the first fusing trigger condition, and determining whether the total number of processing requests of the first window is greater than the second threshold number of window requests in the first fusing trigger condition;
and if so, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing.
4. The method for identifying fusing applicable to microservice according to claim 1, wherein the step of performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target microservice interface to obtain the fusing identification result comprises:
acquiring the second fusing trigger condition, a second processing request number and a second window processing request total number in a preset second time length corresponding to the target micro service interface;
determining whether the second number of processing requests is greater than a third number of processing requests threshold in the second fusing trigger condition, and determining whether the second total number of window processing requests is greater than a third number of window requests threshold in the second fusing trigger condition, wherein the third number of processing requests threshold is greater than the first number of processing requests threshold in the first fusing trigger condition, and the third number of window requests threshold is greater than the first number of window requests threshold in the first fusing trigger condition;
if not, determining that the fusing identification result is not fusing;
and if any one is yes, determining that the fusing identification result is fusing.
5. The method for identifying the fusing of the micro service according to claim 4, wherein if any one of the fusing identification results is yes, the step of determining that the fusing identification result is fusing comprises:
if any one is yes, acquiring a target dependency relationship attribute corresponding to the target micro-service interface;
if the target dependency attribute is weak, determining whether the second number of processing requests is greater than a fourth threshold number of processing requests in the second fusing trigger condition, and determining whether the total number of the second window processing requests is greater than a fourth threshold number of window requests in the second fusing trigger condition, if both, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing, wherein the fourth threshold number of window requests is greater than the second threshold number of window requests in the first fusing trigger condition, and the fourth threshold number of processing requests is greater than the second threshold number of processing requests in the first fusing trigger condition;
if the target dependency relationship attribute is strong, determining whether the second number of processing requests is greater than a fifth threshold of processing requests in the second fusing trigger condition, and determining whether the total number of processing requests of the second window is greater than a fifth threshold of the number of processing requests in the second fusing trigger condition, if both, determining that the fusing identification result is fusing, otherwise, determining that the fusing identification result is not fusing, wherein the fifth threshold of the number of processing requests is greater than the fourth threshold of the number of processing requests, and the fifth threshold of the processing requests is greater than the fourth threshold of the processing requests.
6. The method for identifying fusing applicable to microservice according to claim 1, wherein after the step of performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target microservice interface to obtain the fusing identification result, the method further comprises:
when the fusing identification result is that the fusing is not conducted, acquiring a target response duration corresponding to the single service calling request;
judging whether the target response time length is greater than a preset response time length threshold value or not;
and if the response time length is larger than the response time length threshold, determining that the fusing identification result is fusing.
7. The method for identifying fusing applicable to microservice according to claim 1, wherein after the step of performing fusing identification on the single service invocation request by using the obtained second fusing trigger condition corresponding to the target microservice interface to obtain the fusing identification result, the method further comprises:
when the fusing identification result is fusing, setting the service state of the target micro-service interface to be closed;
acquiring a first interval time from the latest updating time of the fusing identification result to the current time, a target slow calling proportion corresponding to the target micro-service interface and a target abnormal thread proportion, judging whether the first interval time is greater than a preset first interval time threshold, judging whether the target slow calling proportion is less than a preset slow calling proportion threshold and judging whether the target abnormal thread proportion is less than a preset abnormal thread proportion threshold;
if yes, setting the service state of the target micro-service interface to be semi-open;
acquiring the service state of the target micro-service interface, determining the service state as a second interval duration between the semi-open time and the current time, and judging whether the second interval duration is greater than a preset second interval duration threshold value;
and if the service state of the target micro service interface is larger than the second interval duration threshold, setting the service state of the target micro service interface to be fully open.
8. A fuse identification device adapted for use with a microservice, the device comprising:
the request acquisition module is used for monitoring the single service call request received by the target micro-service interface in real time;
a target call link attribute determining module, configured to obtain a target call link attribute corresponding to the single service call request;
the judging module is used for judging whether the target call link attribute is a core or not;
the first fusing identification module is used for carrying out fusing identification on the single service calling request by adopting the acquired first fusing triggering condition corresponding to the target micro-service interface if the single service calling request is not received, so as to obtain a fusing identification result;
and if so, performing fusing identification on the single service calling request by adopting the acquired second fusing triggering condition corresponding to the target micro-service interface to obtain a fusing identification result.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111436716.2A CN114157551B (en) | 2021-11-29 | 2021-11-29 | Fusing identification method, device, equipment and storage medium suitable for micro-service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111436716.2A CN114157551B (en) | 2021-11-29 | 2021-11-29 | Fusing identification method, device, equipment and storage medium suitable for micro-service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114157551A true CN114157551A (en) | 2022-03-08 |
| CN114157551B CN114157551B (en) | 2023-07-21 |
Family
ID=80784171
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111436716.2A Active CN114157551B (en) | 2021-11-29 | 2021-11-29 | Fusing identification method, device, equipment and storage medium suitable for micro-service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114157551B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115037653A (en) * | 2022-06-28 | 2022-09-09 | 北京奇艺世纪科技有限公司 | Service flow monitoring method and device, electronic equipment and storage medium |
| CN116980480A (en) * | 2023-09-25 | 2023-10-31 | 上海伊邦医药信息科技股份有限公司 | Method and system for processing fusing information based on micro-service network model |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108712309A (en) * | 2018-06-11 | 2018-10-26 | 郑州云海信息技术有限公司 | A kind of micro services node means of defence under micro services framework and system |
| CN111049670A (en) * | 2019-11-07 | 2020-04-21 | 苏宁云计算有限公司 | Method and device for fusing isolation of micro-service |
| CN111078453A (en) * | 2019-12-17 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Method and device for automatically fusing and recovering micro-service, computer equipment and storage medium |
| CN111756601A (en) * | 2020-06-24 | 2020-10-09 | 中国平安财产保险股份有限公司 | Microservice architecture monitoring method and device, computer equipment and readable storage medium |
| US20200364035A1 (en) * | 2019-05-16 | 2020-11-19 | Citrix Systems, Inc. | Systems and methods for using a call chain to identify dependencies among a plurality of microservices |
| CN112131036A (en) * | 2020-10-09 | 2020-12-25 | 腾讯科技（深圳）有限公司 | Overload protection method, device, equipment and computer readable storage medium |
| CN113382080A (en) * | 2021-06-25 | 2021-09-10 | 中关村智慧城市产业技术创新战略联盟 | Micro-service management system and method |
-
2021
- 2021-11-29 CN CN202111436716.2A patent/CN114157551B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108712309A (en) * | 2018-06-11 | 2018-10-26 | 郑州云海信息技术有限公司 | A kind of micro services node means of defence under micro services framework and system |
| US20200364035A1 (en) * | 2019-05-16 | 2020-11-19 | Citrix Systems, Inc. | Systems and methods for using a call chain to identify dependencies among a plurality of microservices |
| CN111049670A (en) * | 2019-11-07 | 2020-04-21 | 苏宁云计算有限公司 | Method and device for fusing isolation of micro-service |
| CN111078453A (en) * | 2019-12-17 | 2020-04-28 | 深圳前海环融联易信息科技服务有限公司 | Method and device for automatically fusing and recovering micro-service, computer equipment and storage medium |
| CN111756601A (en) * | 2020-06-24 | 2020-10-09 | 中国平安财产保险股份有限公司 | Microservice architecture monitoring method and device, computer equipment and readable storage medium |
| CN112131036A (en) * | 2020-10-09 | 2020-12-25 | 腾讯科技（深圳）有限公司 | Overload protection method, device, equipment and computer readable storage medium |
| CN113382080A (en) * | 2021-06-25 | 2021-09-10 | 中关村智慧城市产业技术创新战略联盟 | Micro-service management system and method |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115037653A (en) * | 2022-06-28 | 2022-09-09 | 北京奇艺世纪科技有限公司 | Service flow monitoring method and device, electronic equipment and storage medium |
| CN115037653B (en) * | 2022-06-28 | 2023-10-13 | 北京奇艺世纪科技有限公司 | Service flow monitoring method, device, electronic equipment and storage medium |
| CN116980480A (en) * | 2023-09-25 | 2023-10-31 | 上海伊邦医药信息科技股份有限公司 | Method and system for processing fusing information based on micro-service network model |
| CN116980480B (en) * | 2023-09-25 | 2024-02-27 | 上海伊邦医药信息科技股份有限公司 | Method and system for processing fusing information based on micro-service network model |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114157551B (en) | 2023-07-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114157551A (en) | Fusing identification method, device, equipment and storage medium suitable for micro-service | |
| CN108874618B (en) | Cognos process monitoring method and device, computer equipment and storage medium | |
| CN112231054B (en) | Multi-model inference service deployment method and device based on k8s cluster | |
| CN108845869B (en) | Concurrent request control method, device, computer equipment and storage medium | |
| CN112631701A (en) | Page request method and device, computer equipment and storage medium | |
| CN112667424A (en) | Abnormal data processing method and device, computer equipment and storage medium | |
| CN109639759B (en) | Mail sending method and device based on cloud transmission and computer equipment | |
| CN112685669A (en) | Page rendering method and system | |
| CN108846763A (en) | Core protects request processing method, device, computer equipment and storage medium | |
| CN110727588A (en) | Network application testing method, system, computer equipment and readable storage medium | |
| CN110147258B (en) | Method and device for improving program loading efficiency, computer equipment and storage medium | |
| CN113301161B (en) | Seamless upgrading method, device, equipment and storage medium of application service | |
| CN111224939A (en) | Task request intercepting method and device, computer equipment and storage medium | |
| CN111949421B (en) | SDK calling method, device, electronic equipment and computer readable storage medium | |
| CN111008377A (en) | Account monitoring method and device, computer equipment and storage medium | |
| CN114237931A (en) | Configuration method and device for interface call, computer equipment and storage medium | |
| CN113342670A (en) | Interface test method, device, equipment and medium | |
| CN113608962A (en) | Method, device and equipment for predicting abnormal application interface and storage medium | |
| CN112527639A (en) | Remote debugging method and device in production environment, computer equipment and storage medium | |
| CN111814174A (en) | Data access control method and device and computer equipment | |
| CN112162993A (en) | Data updating method and device of blacklist and computer equipment | |
| CN112925997B (en) | Task dependency graph display method suitable for Azkaban and related equipment | |
| CN112559063A (en) | CPU switching method and device, intelligent terminal and storage medium | |
| CN115509766A (en) | Micro-service registration and detection method and device based on theme queue | |
| CN111385149A (en) | Internet of things card early warning method, device, equipment and medium for connection management platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |