Microsoft Azure

Serverless — Azure Functions

Run event-triggered code with automatic scaling and consumption-based billing.

Azure Functions is Azure's serverless compute: you write a function with a trigger and Azure runs it on demand, scaling out automatically. A defining feature is the trigger/binding model — a function has exactly one trigger (HTTP, Timer, Queue/Service Bus message, Blob created, Event Grid/Hub event, Cosmos DB change feed) and optional input/output bindings that wire it to other services declaratively, reducing boilerplate for reading and writing data.

A vending machine wired to the building: a coin (trigger) makes it act, and chutes connect it directly to supply and delivery (bindings) so it does not need its own plumbing. It powers down completely between customers and costs nothing while idle.

Key Concepts

1
Hosting plans control the trade-offs. The Consumption plan scales to zero and bills per execution and GB-seconds (with cold starts). The Premium plan keeps pre-warmed instances to remove cold starts and adds VNet integration. The Dedicated/App Service plan runs on existing app-service compute. Functions are often composed into workflows with Durable Functions (stateful orchestration — chaining, fan-out/fan-in, human-in-the-loop) which is distinctive among serverless platforms.