Is creating a timer/separate thread within an ASP .Net MVC Web application a bad thing to do?
Posted on 2014-04-11
We have an ASP .Net MVC web application.
In order to do some processing on set intervals, I'm looking at the possibility
of creating a timer or a thread within the app (server side) to do the clean up.
Is this a good design practice (Am I breaking some kind of rules here)?
What are the possible short comings of such an approach?