I need an application which reads some tables and generates some new data from the data read and save it to another tables. It is like: I have a database which gives me information about some clients that comes from one application. According to this information I might create some alerts about the clients in order to show it in another application.
I have got a service which generates the first data, it works fine, it was not developed by me and I do not have to worry about that . But I created a windows service to read and create new data and it uses DataSets like "temp" tables and for communication with database and at the end of the process, everything is saved in database at once, using tableAdapter.update();
I would like to improve this windows service because DataSets do not seem the best option in my point of view and I have studied about Entity Framework and its advantages, but I am not sure if it is the best way to build a windows service. What are the best practices for building an application like that? What is the best way not to go to database every record generated, but save a bunch of records and keep it in memory before? I mean, like to have temp tables in runtime and at the end of process, save everything generated.