Azure
Serverless
starter
Queue-Based Worker Processing — Azure Architecture Template
Intake API hands work to a Service Bus queue consumed by an elastic worker function writing results to Cosmos DB.
Why this architecture works
- The queue absorbs bursts so the intake API responds instantly regardless of backlog depth
- Service Bus dead-lettering isolates poison messages instead of blocking the queue
- Worker concurrency scales with queue length automatically via the Functions runtime
- Idempotent writes to Cosmos DB make at-least-once delivery safe
- Both functions share Application Insights so a message can be traced from intake to completion
What's inside (7 resources)
Intake API
function-app
Work Queue
service-bus-namespace
Function Storage
storage-account
Queue Worker
function-app
Results Store
cosmos-db
Secrets
key-vault
APM
application-insights
From template to running infrastructure
- Open this template in the CloudForge visual designer (free account, no credit card).
- Customize resources, names, and connections on the drag-and-drop canvas — or ask Vani, the AI architect, to adapt it.
- Generate production-ready Terraform, ARM, or Bicep in one click.
- Review the plan diff and security scan, then deploy with human approval.