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

Re:HangFire – Reliable and transparent background job proces... by russ519 on Wednesday May 28, 2014 @11:01AM (#7810302)

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.

[ Parent | on HN ]

Re:HangFire – Reliable and transparent background job proces... by anton_gogolev on Wednesday May 28, 2014 @11:11AM (#7810361)

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

[ Parent | on HN ]

Re:HangFire – Reliable and transparent background job proces... by russ519 on Wednesday May 28, 2014 @11:29AM (#7810739)

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?

[ Parent | on HN ]

Re:HangFire – Reliable and transparent background job proces... by odinserj on Thursday May 29, 2014 @01:13PM (#7817294)

Why?

[ Parent | on HN ]