When to reach for Azure Functions – and when not to
Model the event
A receipt processor begins when a document arrives. It needs a document identifier, a retry policy and a durable record of completion. A queue-triggered function is a candidate when each unit of work can be handled independently.
Select the hosting plan
Estimate execution duration, concurrency, memory and network requirements before selecting a Functions hosting option. Scaling behaviour and supported capabilities vary by plan. Measure the first request after idle as well as steady traffic.
Test a duplicate
Deliver the same document event twice. Use a unique processing key and record the committed result so a retry cannot create a second payable. For a long-running worker with stable utilisation, compare the operational cost of a continuously running service.