The plan is to develop generic solution for long running task initiated in web site by users such as: 1. upload large file and do some custom processing and then insert in the database. 2. export large amount of data

But we do not want to run these tasks on web servers and instead run on dedicated other sever. I have a couple of following solutions but looking for suggestion on these solutions or a new option.

  1. Web site calls WCF service on other server (one-way operations / fire-forget). WCF service has all the information to process request and task will run in WCF service.

  2. Window service but not sure how Window service will start the job as soon as possible as we do not want any delay between user submitted the form and process start time. Need some kind of flag for Window service to start.

  • Windows service should be always running, and it should have one thread monitor for event (upload...etc) and process in a separate thread preferably using a thread pool. The trigger would be a record written to db by your web server polled by windows service, or hosted wcf service on windows service called by web server, or simply dumping the uploaded file to a shared folder and it's picked up by file system watcher. Feb 27, 2015 at 4:24

1 Answer 1


Actually, one way to host WCF services is as a windows services. The difference is how customized those services can be.

The windows service can keep listening a port and response at real time when you use them. Actually a service can have several clients connected at the same time. for example IIS.

To me, seems to be easier the WCF fire and forget option; less coding for the same result.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.