Hi, 陆 The scenario you described in last post is more like a scene in which a protector may participate in. General implementation includes hystrix[1], sentinel[2], etc. . They can introduce abilities like flow control, traffic shaping, circuit breaking to various systems including Dubbo, servlet, gateway and so on. You can take a look and have a try with any of them to see whether it can match your concern.
For your information :) [1] Hystrix https://github.com/Netflix/Hystrix [2] Sentinel https://github.com/alibaba/sentinel/ best regards, Jason > On Jul 21, 2020, at 22:25, 陆 錞斐 <[email protected]> wrote: > > Hello everyone, I'm trying to make a little contribution to Dubbo by adding a > new feature. In this feature, threads can be allocated dynamically according > to service invocations, so as to achieve thread isolation between services. > In this way, we can set the minimum number of threads per service to prevent > thread pool resources from being exhausted by some services and thus > affecting other services. > > Now the problem is how to set up an evaluation model according to the service > call situation, such as QPS, RT, success, exception, reject, and so on, so as > to reasonably allocate threads to each service. > > I am lack of experience in this area, I hope you can give some suggestions, > either algorithm or book is OK, thank you!
