HangFire – Reliable and transparent background job processing for ASP.NET • Hacker News Board

This post could not have come at a better time! I literally spent the better part of yesterday researching best practices for queueing jobs from ASP.NET (WEB API) hosted on Windows Server, not Azure. I was considering NetMSMQ based WCF, Windows Service Bus 1.1, NServiceBus, MassTransit, ServiceStack, Windows Azure Pack, Redis or RabbitMQ hosting Worker Processes as Windows Services.

I had settled on the later as I wanted to avoid the complicated configuration of WCF, if possible, and just wanted a simple, reliable, and scalable way, to queue messages and process them. Ideally, I wanted a way to host/launch the worker processes from the web app to avoid complicating the development environment by having to install and run separate processes (Windows Service).

I will definitely be looking at this project today and putting it through a PoC.

Update: Forgot to mention ServiceStack in list of frameworks considered.

Re: HangFire – Reliable and transparent background job processing for ASP.NET

#6

Post by anton_gogolev » Wed, May 28, 2014, 3:11 PM UTC

russ519 wrote: post #5

This post could not have come at a better time! I literally spent the better part of yesterday researching best practices for queueing jobs from ASP.NET (WEB API) hosted on Windows Server, not Azure. I was considering NetMSMQ based WCF, Windows Service Bus 1.1, NServiceBus, MassTransit, ServiceStack, Windows Azure Pack, Redis or RabbitMQ hosting Worker Processes as Windows Services. I had settled on the later as I wa…

You will inevitably end up with a separate Windows service, mainly for maintanability reasons.

Re: HangFire – Reliable and transparent background job processing for ASP.NET

#7

Post by jamra » Wed, May 28, 2014, 3:22 PM UTC

rcarmo wrote: post #4

jamra wrote: post #3

How is this any different than using MSMQ?

Well, it looks like it might run inside Mono, for one.

So something like RabbitMQ would do exactly the same.

Re: HangFire – Reliable and transparent background job processing for ASP.NET

#8

Post by russ519 » Wed, May 28, 2014, 3:29 PM UTC

anton_gogolev wrote: post #6

russ519 wrote: post #5

This post could not have come at a better time! I literally spent the better part of yesterday researching best practices for queueing jobs from ASP.NET (WEB API) hosted on Windows Server, not Azure. I was considering NetMSMQ based WCF, Windows Service Bus 1.1, NServiceBus, MassTransit, ServiceStack, Windows Azure Pack, Redis or RabbitMQ hosting Worker Processes as Windows Services. I had settled on the later as I wa…

You will inevitably end up with a separate Windows service, mainly for maintanability reasons.

I would love it if you would elaborate on this thought. Are you referring specifically to a solution build with Hangfire or any solution involving worker processes on Windows?

Re: HangFire – Reliable and transparent background job processing for ASP.NET

#9

Post by mattmanser » Wed, May 28, 2014, 4:48 PM UTC

jamra wrote: post #3

How is this any different than using MSMQ?

MSMQ is a colossal PITA to set up. As is RabbitMQ, etc.

I've wanted something like this for a very long time.

Re: HangFire – Reliable and transparent background job processing for ASP.NET

#10

Post by odinserj » Wed, May 28, 2014, 4:51 PM UTC

jamra wrote: post #3

How is this any different than using MSMQ?

HangFire provides you a unified programming model for background job processing on shared, dedicated and cloud hosting. It takes the complexity of background processing itself and lets you to concentrate only on background jobs.