The FaaS platform gained a lot of popularity which resulted in many competitors. There was OSS providers like OpenFaaS or Fission. There were of course the commercial versions to like Azure Functions and Google Cloud Functions. - Source: dev.to / 19 days ago

Serverless technology helps React Native developers create more robust, adaptable, and efficient mobile applications that meet the demands of today's dynamic digital landscape. By seamlessly integrating cloud functions from providers like AWS Lambda or Azure Functions, developers can tap into a world of possibilities to enrich their mobile apps. - Source: dev.to / 7 months ago

Azure Functions: Here’s the official Azure Functions product page, where you can learn about the features, benefits, and pricing of Microsoft’s serverless computing service. - Source: dev.to / 11 months ago

UNIX is irrelevant on the cloud, unless one is stuck deploying legacy workloads on VMs, this is what we use in modern applications not stuck in the past. https://aws.amazon.com/eks/ https://azure.microsoft.com/en-us/products/kubernetes-service https://cloud.google.com/kubernetes-engine/ https://cloud.google.com/appengine https://azure.microsoft.com/en-us/products/app-service https://aws.amazon.com/lambda/... - Source: Hacker News / about 1 year ago

Microsoft recently announced the general availability of the .NET 7 for Azure Functions isolated worker process. Azure Functions will support .NET 7 serverless apps hosted on all Windows and Linux SKUs, including Consumption plan, Elastic Premium plan, and App Service plans.  More details: https://www.infoq.com/news/2022/11/azure-functions-dotnet-7/. Source: over 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: about 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