.net - Entity Framework Architecture for long running windows service -

I have a question about how best to architecture your solution using the ATI Framework in the Windows service.

I want to provide an online (web) service that allows users to execute long-lasting tasks, view progress of work, cancel them, etc.

So far, I'm actually using a window service to execute the tasks that bring WCF intervals to the new job and manage existing tasks.

I am using the unit framework to store the history of all jobs. Although I am not completely convinced that the background process (with current progress) and WCF services should be exposed to this situation. The background process periodically records the database and WCF services from there to the current situation?

Or does it come to understand that the WCF service directly identifies with a static member or background process reaching something similar? Can they share a datacentext?

I have to turn on the information and it seems that the background process and WCF service are both running in the same process, but then communicating through the database seems a little strange, but on the other hand it is a Good architecture is ...

Thanks a lot!

I would recommend separating the two parts. And save the state to the database, where in the future you can easily increase your structure to many machines. Your database and web client access can stay on one server and long-running tasks can stay on multiple servers.

No Crashing Will Affect You Otherwise you will be able to log in properly. If the state is correctly saved in the database then Review the information and prepare reports while performing performance and forecasts.