About the operation of reading data at java intervals

on the java platform, if you want five or six hundred pieces of data, you have to read them every two or three seconds, and then save them to the database. What technology is better to use?

what I thought was that if there are a few data items, there are hundreds of threads to read them.
there is another one, such as quartz, which opens five or six hundred scheduled readings.

but because the quantity is larger than usual. Feel that the quality is not good.

excuse me, is there any good technology or plan to deal with this situation, mainly to read this process?

Mar.07,2021

it's not a good idea to open hundreds of threads to read, but if the data can be read together (read sequentially at once), it would be nice to open one thread. If multiple data needs to be read independently, you can consider ThreadPool (equivalent to opening multiple threads, one thread processing one type of data), or if the timing is complex, or if you need a repository, or multiple servers to execute together, you can use quartz.

Menu