morganc20287

Proposal: Job Orchestration Architecture with Azure Queue Storage

Context

Multiple scheduled tasks (Windows Task Scheduler) run across several Azure VMs to generate documents and data. This makes it hard to:

• trigger jobs on demand,
• centralize observability,
• coordinate/sequence tasks.

morganc20287

Engineering Standards – Observed Issues & Recommendations

Summary of Points

1. Avoid “Everything Static”
2. Hard‑coded Connection Strings
3. EF Core DbContext Usage (using var context = ...GetContext())
4. Missing CancellationToken in Async Methods
5. HttpClient Misuse (new per call)

---

morganc20287

Proposal: Job Orchestration Architecture with Azure Queue Storage

Context

Multiple scheduled tasks (Windows Task Scheduler) run across several Azure VMs to generate documents and data. This makes it hard to:

• trigger jobs on demand,
• centralize observability,
• coordinate/sequence tasks.

We propose an incremental architecture: HTTP API + Azure Queue Storage + per-VM Agents, keeping existing executables while removing direct dependence on Windows Task Scheduler.