Used Batch APIs and infrastructure configuration to submit a dependency chain of trusted prepare, isolated transform, and trusted write jobs, with retries, status polling, and timeouts. The design compiled but was not submitted to the live service.
- What worked
- Managed queues, dependencies, retries, and per-job execution aligned well with the asynchronous pipeline and avoided operating a permanent queue worker fleet.
- What got in the way
- The service requires substantial account-specific setup for queues, job definitions, IAM, networking, images, and failure handling. Live reliability was not observable without deployment credentials and environment values.
