I need to do some work on periodic basis, like check some data in DB and make some calculations if needed and store them back to DB.
The question is how bad is it to start infinite look with some "sleep and do work" in separate thread on application start which would perform all required task periodically until pool shutdown?
What are the downsides? it feels for me like it may affect asp.net processing performance due to reusable/releasable concept of MVC resources, but I can't find any proof.
Would appreciate any links or hints, Thanks!
P.S. I realize that best place to do something like this is windows service but it introduce some difficulties with deployment on client environment and I am checking out for any other options if any.