Single thread pool vs one thread pool per task

Question

I want to use concurrency in Java to make requests to an online API, download and parse the response documents, and load the resulting data into a database.

Is it st

Answer 1

I don't believe there is a standard approach, it depends on your requirements.

If you are writing something quick and dirty then you're best having one pool.

If you're looking for something more resilient and where recovery is required then you may opt for several pools. Eg. if you persist the responses and if your app dies then when it restarts you can just re-queue the responses without having to fetch them again.