Hangfire VS Azure File Storage

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: about 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

Azure Files perhaps? Or if you need frequently accessed files to be quicker then Azure File Sync. Source: 12 months ago

​To know more details: https://azure.microsoft.com/en-us/products/storage/files/. - Source: dev.to / about 1 year ago

If you have a use case that affords any kind of budget, maybe consder Azure Files. It is an SMB share you access over the internet. Basically, windows file server but hardened and entirely managed by Microsoft. This is as hands-off as it gets for an SMB share. Source: about 1 year ago

I have a client that (finally!) decided to go all-in on Azure; I had prepared the owner to expect additional costs based on their need for a file share -- I was expecting to have to use Azure Files. Source: over 1 year ago

I agree with the SharePoint, though another option would be Azure Files. Source: almost 2 years ago