We have the requirement to implement some fire and forget long running tasks that fit perfectly into windows services (remote data acquisition and processing, etc) but the requirement is to deploy them into hosts without remote administration rights.
We are thinking on the possibility of hosting these tasks as background tasks that run on the IIS and that are stored into the Application object (or some other global variable-like approach).
Issues with this solution that I can think ok:
- Scalability: if there is more than one server you will have more than one task and this is not allowed. Workaround: to implement a control mechanism so there is only one running at the same time.
- Shortages: the service will stop everytime we deploy a new version of the application. Workaround: to implement the service into a separate application so it is only restarted when there is a new version of the service.
Is there something else you can think of that could pose a problem to this approach?