Note that such a decorator is not necessarily being applied to the user-supplied Runnable/Callable but rather to the actual execution callback (which may be a wrapper around the user-supplied task). My question: does this configuration bellow taking in account I am already using kafkatempla (i.e. Specify a custom TaskDecorator to be applied to any Runnable about to be executed. I am running the bellow code succesfully in local desktop but I am wondering if I am providing a custom Task Executor properly. It seems reasonble the statement " risky caused by not limit concurrent threads and not reuse it" mainly for my case that is based on logs. Personal desire: I am working hard to provide a corporative architecture for our microservices logs be publish on Kafka topics. But I can find any guidance explaining what are the consequences and some worth cases to apply it.
" and from baeldung a very simple example how to add our own Task Executor. So to be safe, we will also add a task executor bean. SimpleAsyncTaskExecutor is ok for toy projects but for anything larger than that it’s a bit risky since it does not limit concurrent threads and does not reuse threads. Personal knowlegedment: I read from javacodegeeks: ". Springboot Simpleasynctaskexecutor Web Scraping Total Recorder 8.
0 kommentar(er)
