CODEWITHSUNDEEP
asp.netasp.net-mvcjob-queue
UpTheCreek
UpTheCreek

Reputation: 32391

Queueing solutions for ASP.NET MVC

I looking into the concept of queueing for web apps (i.e. putting some types of job in a queue for completion by a seperate worker, rather than being completed in the web request cycle).

I would like to know if there are any good solutions existing for this which can be utilised in an ASP.NET MVC environemnt.

Has anyone had any (good or bad) experiences?

Thank you!

UPDATE:

Just to clarify, I'm not talking about queueing incoming requests. I'll try to illustrate what I mean...

1) Standard situation:

2) What I'm looking into:

And in another process (possibly after the response was sent):

In the first instance the user has waited a long time for server resoponse, in the second it was quick.

Of course there are certain types of jobs that would be appropriate for this, some that would not be.

UPDATE2:

The client doesn't have to be updated immediately with the results of the long job. The changes would just show themselves in the application whenever the user happened to refresh a page (after the job had completed of course).

Think of some of the things that happen in stack overflow - they are not immediately updated in each part of the application, but this happends quite quickly - I suspect some of these jobs are being queued.

Upvotes: 8

Views: 2115

Answers (6)

Colin Desmond
Colin Desmond

Reputation: 4854

I have implemented this pattern by having the web server call a WCF service asynchronously. The VS wizards will generate async proxies for you when you consume a WCF service. If you must have guaranteed delivery on the request to the service, you could use MSMQ as the transport layer for the WCF service.

Upvotes: 1

Joel Martinez
Joel Martinez

Reputation: 47789

Since you mentioned in another comment that you were looking for an equivalent to amazon's sqs service ... you might want to look into Windows Azure. They have an equivalent queue api:
http://msdn.microsoft.com/en-us/library/dd179363.aspx

Upvotes: 1

Joel Martinez
Joel Martinez

Reputation: 47789

The Rhino Service Bus is another solution that may work for you:
http://ayende.com/Blog/archive/2008/12/17/rhino-service-bus.aspx

Upvotes: 3

Magnus Johansson
Magnus Johansson

Reputation: 28325

Post the job data in an MSMQ queue and have a Windows Service process the items in the queue. Or, let the web request spawn a process that process the items in the queue.

Upvotes: 5

Hal
Hal

Reputation: 1264

You might check into using an ESB. I've played around with MassTransit: http://code.google.com/p/masstransit/ - the documentation is (or at least was) a little sparse, but it's easy to implement.

In addition, I develop apps for running on Amazon EC2 and absolutely love their AmazonSQS Service.

Thanks,

Hal

Upvotes: 2

Martin
Martin

Reputation: 11041

I think Chrisitan's comment might be your answer, but considering I don't know much about IIS and queueing with it, my solution would be:

Make an asynchronous request and load the job details in the database. Then have a job to loop through the database and process the job details. I do this for one of my sites. Might not be the best solution out there, but it gets the job done.

EDIT

My answer might still work, but you will need to have some polling mechanism on the client to continuously check the database to see if that user's job is done, then grab the data you need.

Upvotes: 0

Related Questions