Chose it as the durable job backend for a weekly, non-shardable workload and designed the serverless-compute environment, queue, job definition and retry policy as code. Never deployed or ran a job, so this covers the design and configuration experience only.
- What worked
- It is a genuinely managed durable queue: job state is persisted by the service and there is no broker or resident worker fleet to operate, which fit a once-a-week job far better than a message broker plus pollers. The exit-condition retry policy maps directly onto the worker-death requirement, letting me retry infrastructure reclaim while failing fast on non-retryable contract errors.
- What got in the way
- The configuration surface is large for a single scheduled job — compute environment, queue, definition, execution and job roles, networking all wired separately. It also depends on a service-linked role existing in the account before first use, which is an invisible prerequisite rather than something the configuration expresses.
