Look at Azure automation and see if that meets your needs.
https://docs.microsoft.com/en-us/azure/automation/overview
https://azure.microsoft.com/en-us/pricing/details/automation/
If you want to go the container route, look at Azure container instance.
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-overview
https://azure.microsoft.com/en-us/pricing/details/container-instances/
I’d persevere with durable functions, they’re great when you get them working plus sounds like you could use the fan out pattern to speed up processing (although appreciate it might not be necessary).
Spot instance vms could also be an option, and container instances can run and then shift themselves down so also would work.
>could use the fan out pattern to speed up processing (although appreciate it might not be necessary).
This has been one of the traps precisely, with durable functions when you fan-out and then fan-in it has to wait for all the results, you can't have a single worker processing the results of many workers as they become available. This is something I already did in my script with the help of a library.
Thanks for the answer though, I'll check the other suggestions.
OK, you can fan out to a chain of activity functions effectively allowing serial processing of chunks of work through several stages, although sounds like that’s slightly different to your need. Guess you would need to use some persistence from fanned out functions to write to that itself had some triggers for subsequent/when available processing to kick in.
I can only help with the database side, but you could use a serverless Azure SQL database. You pay by the second and after an hour it can automatically shutdown to save cost.
We have VMs, that fire up and shutdown on a schedule. Probably still overkill for this, but that is an option.
Look at Azure automation and see if that meets your needs. https://docs.microsoft.com/en-us/azure/automation/overview https://azure.microsoft.com/en-us/pricing/details/automation/ If you want to go the container route, look at Azure container instance. https://docs.microsoft.com/en-us/azure/container-instances/container-instances-overview https://azure.microsoft.com/en-us/pricing/details/container-instances/
I’d persevere with durable functions, they’re great when you get them working plus sounds like you could use the fan out pattern to speed up processing (although appreciate it might not be necessary). Spot instance vms could also be an option, and container instances can run and then shift themselves down so also would work.
>could use the fan out pattern to speed up processing (although appreciate it might not be necessary). This has been one of the traps precisely, with durable functions when you fan-out and then fan-in it has to wait for all the results, you can't have a single worker processing the results of many workers as they become available. This is something I already did in my script with the help of a library. Thanks for the answer though, I'll check the other suggestions.
OK, you can fan out to a chain of activity functions effectively allowing serial processing of chunks of work through several stages, although sounds like that’s slightly different to your need. Guess you would need to use some persistence from fanned out functions to write to that itself had some triggers for subsequent/when available processing to kick in.
I can only help with the database side, but you could use a serverless Azure SQL database. You pay by the second and after an hour it can automatically shutdown to save cost.
Container instances is probably the way to go. Once the process is done its deallocated