![]() My question: does this configuration bellow taking in account I am already using kafkatempla (i.e. 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. ![]() With Portia you can annotate a web page to identify the data you wish to extract, and Portia will understand based on these annotations how to scrape data from similar pages. Personal desire: I am working hard to provide a corporative architecture for our microservices logs be publish on Kafka topics. Portia is a tool that allows you to visually scrape websites without any programming knowledge required. 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: ".
0 Comments
Leave a Reply. |