I'm still getting familiar with Azure Storage and need a simple, reliable way to save a variable's state between WebJob executions. I initially tried writing the value to a local file, but the process environment doesn't allow that. Should I use Blob Storage, Table Storage, or another Azure service?
3 Answers
It’s worth reconsidering whether a WebJob is the right host for a long-running process. Depending on how the job runs and how much state it needs, another Azure compute option or Durable Functions may be a better fit. Either way, don’t rely on the local file system for persistent state because the instance can be restarted or replaced.
Blob Storage or Table Storage can both work, depending on the data shape. Also consider Durable Functions if this is a long-running or asynchronous workflow, since they provide built-in patterns for tracking execution state instead of managing it manually.
For a single value, Blob Storage is probably the simplest option. Your WebJob can connect using the AzureWebJobsStorage connection string, load the current value when it starts, and save the updated value when it finishes. If you have several structured fields or many records, Table Storage is a better fit. A small state-store wrapper can keep the storage code clean.
Thanks, that clears things up. I’ll start with Blob Storage and use a small wrapper to load and save the value.