CODEWITHSUNDEEP
asp.netasp.net-mvcmultithreading
Yogurt The Wise
Yogurt The Wise

Reputation: 4499

.Net MVC Threading Long running process

I have a long running process in my MVC application(C#). Its building data for many reports.

Some of the clients could take several minutes or longer to calculate. Is running the process in a separate thread the best option? Is there another way to allow the process to run, while allowing the user to still use the rest of the site?

If threading is the best solution, any good sites or stackoverflow threads to look at on how to do this?

Upvotes: 1

Views: 1337

Answers (2)

hatchet - done with SOverflow
hatchet - done with SOverflow

Reputation: 16257

I've used two methods to solve this. If the work is guaranteed to not be TOO long running, I've kicked off a thread to do the work and return immediately to the user. When we couldn't make that guarantee, we used a queue (we happened to use MSMQ) for executing long running tasks. This processing was done on a different server apart from IIS. A benefit of this is that we built in a wait and retry on failure mechanism. So besides it handling long running tasks, we also used it for anything that might fail in a way that was inconvenient to handle in our MVC app. The main example of this is sending an email. Rather than do that in the MVC app we would just toss an email task on the queue. We used the Command Pattern for the task objects placed on the queue. Once we had that mechanism in place, we stopped using the technique of spawning a thread from our MVC code.

Upvotes: 2

user610217
user610217

Reputation:

When I've had cases like those, I usually would build a service to asynchronously process requests, and return a handle that I could use to check on its status in a database. IMHO, splitting it off as a thread in the web application seems like you'd be trying to shove a square peg into a round hole.

Upvotes: 3

Related Questions