QuartzNet VS DurableTask

I would agree with using Job over Queue. Therefore I would recommend looking at Quartz.Net https://www.quartz-scheduler.net/

You can use something like https://www.quartz-scheduler.net/ to create multiple recurring jobs based on the definition you load from a DB.

Or use an existing open source scheduling solution like https://www.quartz-scheduler.net/

If you're interested in using Quartz, you can check out their GitHub repo here: https://github.com/quartznet/quartznet. They also have extensive documentation available on their website: https://www.quartz-scheduler.net/documentation/index.html.

You should use an actual scheduler. https://www.quartz-scheduler.net/

Better to use a framework like Quartz.NET for scheduling background tasks. How it works inside the box I have no idea, but I have used it extensively in my web applications, and those background tasks run 24/7, come hell or high water. It's a good library, and it's easy to use.

Might want to checkout DurableTasks[1] for that

[1] https://github.com/Azure/durabletask

Azure Durable Tasks are great for this. It’s open source too: https://github.com/Azure/durabletask

AWS Simple Workflows or Azure Logic Apps are both services that let you define S2S workflows however you like without any particular bias to CI/CD or business operations.

If you want to go even lower level, a framework like DTFx lets you define long-running, distributed and resilient orchestrations in code:

https://github.com/Azure/durabletask

The fast and less official way to clean up state is to use the underlying Durable Task Framework storage APIs directly. Durable Functions has an internal dependency on the Durable Task Framework, so no new packages need to be added to your app to access them. Here's an example function that demonstrates how to clean up Azure Storage state quickly (disclaimer: use any of my code samples at your own risk).

Netherite is a distributed workflow execution engine for Durable Functions (DF) and the Durable Task Framework (DTFx).

To give context - this table would track long running operations that were initiated and being executed by our worker machines (we use this c sharp framework).

Behind the scenes, the Durable Functions extension is built on top of the Durable Task Framework, an open-source library on GitHub that's used to build workflows in code. Like Azure Functions is the serverless evolution of Azure WebJobs, Durable Functions is the serverless evolution of the Durable Task Framework. Microsoft and other organizations use the Durable Task Framework extensively to automate mission-critical processes. It's a natural fit for the serverless Azure Functions environment.

I could clearly see that the developers building applications on Microsoft Azure were facing eerily similar challenges to what I had seen back at AWS. The same challenges we had tried to address with SWF. So I used one of the internal team hackathons as an opportunity to pair up with Affan Dar and take another stab at solving the problem. Affan had a very deep understanding of Azure ServiceBus so he was the perfect person to build the backend for the stateful C# experience I had in mind. Microsoft had recently added async/await capabilities into C# and it turned out to be an amazing fit for writing stateful applications which need to orchestrate calls among microservices. Since Java lacked an async/await like primitive, we had to rely on Promise-based async approach when building SWF. But with C#, we were able to deliver a much cleaner and synchronous programming model using async/await. This hackathon project resulted in Azure Durable Task Framework as an OSS client SDK which uses Azure ServiceBus as the backend to provide a stateful workflow-as-code experience for applications. I'm so glad to see Microsoft has continued investing in the experience with Azure Durable Functions as the latest reincarnation of the original effort. An effort which started with that hackathon project.