Simliar to Does gRPC server spin up a new thread for each request? but on the client side and a more specific question than Making Grpc calls In Spring Webflux
I have a related problem which made me think about this question.
When I use the default executor or a custom built one from a Executors.newFixedThreadPool, I get a TimeoutException under load (as it should). With the directExecutor, Resilience4J timelimitter seems to kick in and just route to my unavailable page.
I am thinking I should be using directExecutor to avoid having another thread pool that the app will manage and reuse the existing pool/schedulers provided by Reactor.
