Design for creating new thread and thread pool execution or how to execute async code in imperative mode

[lecogiteur]

Hi,

I want to know with Quarkus if it's a best practice to create other Thread Pool out of Quarkus?
Like "CompletableFuture.runAsync" or "parallelStream" which use ForkJoinPool in order to execute async code, this pool takes some CPU so, I suppose it could block thread pools of Quarkus (event loops and worker pool).
I see ManagedExecutor , ThreadContext and Mutiny some solution in order to execute async code.

So in impérative mode, Is it a best practice to use custom executor or "CompletableFuture.runAsync" or "parallelStream" with Quarkus?

In another way I read the documentation but it's not clear for me. Quarkus uses a Multi Reactor Pattern like Vert.x or not? Which pool existing in Quarkus (event loop, worker, other?) ?

I need clarification :) Thanks