Service fusing and degradation of Note Series

In the micro Service Architecture , Because the granularity of each service is fine , There will be complex calls between each other , Also, the request link is long , This leads to a problem , as follows ：

In the case of high concurrency , This complex dependency call , It will threaten the stability of the system , Like a login , Ten or more services were invoked , If one of the services is delayed, overtime, or down , It will cause abnormal login , There may be an avalanche

---

About avalanche concepts and solutions , Please go to the link below to view ：

https://blog.csdn.net/qq_38377525/article/details/122861284?spm=1001.2014.3001.5502https://blog.csdn.net/qq_38377525/article/details/122861284?spm=1001.2014.3001.5502

---

Speaking of this , I have to talk about the criteria for demotion , Nor can it be downgraded in any case , Not every place can be demoted , thus , Provide a reference index , as follows

1、 Mean response time ： such as 1s There are 5 A request , If the average response time at the corresponding time exceeds the threshold , Then it is necessary to downgrade and fuse the access of this method within a fixed time window

2、 Abnormal proportion ： That is, when the proportion of the total number of exceptions obtained by a method per second exceeds the previously set threshold , The resource will be automatically degraded , That is, in the next fixed window , All calls to this method will automatically return a complete set of data

3、 Number of exceptions ： Similar to the abnormal proportion , That is, when the number of exceptions obtained by a method within a specified time window exceeds the threshold, degradation or fusing will be triggered