Best practice of writing a program which has too many data collection processes C#

Question

I have to login in to various elements to retrieve some data, problem is each element has its own login credentials, I want to write all such data collection processes into one single program so that I dont have 10 different scheduled processes to look at.

Did any of you have such a challenge, if so how did you go about it? I am right now doing it the top down way, so its after the first data collection process gets implemented the program goes for the next...

I know that this is not the right way, I have threads and processes in mind, but being a beginner I'm kinda lost now.

Answer 1

if the process of collecting data of the different sources is taking longer you could get faster results if you do it with multithreading and callbacks, but if in normal case it takes not really long, why not make it as simple as possible.

Answer 2

Its going to depend on how you need to login to each element, and what it means to "collect" the data. If you can give some specific types of elements (SQL, Oracle, AS/400, etc) and what you are trying to get out of them, then we can help you get started with automating the process.