HatchBox VS Hangfire

Hatchbox is a deployment platform for Ruby-on-Rails. If you prefer, it's a Heroku competitor. - Source: dev.to / about 2 months ago

I think hatchbox.io is pretty much the best option. I also like fly.io though, pretty decent as well. Source: 11 months ago

Dont forget about Hatchbox by Chris Oliver at https://hatchbox.io/. Source: 11 months ago

You're missing hatchbox.io . They make your own servers feel like a PaaS for Rails. I can't recommend them enough. Source: 11 months ago

Https://hatchbox.io can do a lot of the heavy lifting for you. Regarding buckets, there are countless tutorials out there that walk you through the entire thing. Source: about 1 year ago

Hangfire (https://hangfire.io) includes default exception handling and is very extensible, I think it's a good mid-level choice and a good alternative to other queue mechanism, if you can't afford to host a separated queue service or can't manage a separated service; also scales pretty well (you can have multiple servers handling the same background job queue, or different queues). It runs on Sql Server and MySql... Source: almost 2 years ago

I used to just use hangfire.io in .net and worked wonderfully for any long running tasks or schedules. Had a great queuing system, UI to know if they failed , etc. That's how I'd send emails, pdf's, and other things along that nature. Then if it were more just a db related operation, just setup a schedule in mssql job service. Source: almost 2 years ago

You can use hangfire for cronjob, to run at a time in future, you can use Hangfire.Schedule(jobid, datetime). Source: almost 2 years ago

So another option is to use something like https://hangfire.io to pull the jobs and process them? Source: about 2 years ago

I've got a fairly large process I need to handle in background on my .net core web app so I've exported it to a background task using Hangfire. Source: almost 3 years ago