#Consumption synonyms code#

Use SQL bindings to read or write data from Azure SQL Use Functions and SignalR to respond to data in the moment Process message queues using Queue Storage, Service Bus, or Event HubsĬollect and process data from IoT devices

#Consumption synonyms code#

Run custom logic when a document is created or updated in Azure Cosmos DBĮxecute code on pre-defined timed intervals Run code when a file is uploaded or changed in blob storageĬreate an event-driven workflow from a series of functions using durable functions Implement an endpoint for your web applications using the HTTP trigger The following are a common, but by no means exhaustive, set of scenarios for Azure Functions. In many cases, a function integrates with an array of cloud services to provide feature-rich implementations. Providing compute resources on-demand is the essence of serverless computing in Azure Functions.

Where do all the compute resources come from? Azure Functions provides as many or as few compute resources as needed to meet your application's demand. As requests fall, any extra resources and application instances drop off automatically. Second, as requests increase, Azure Functions meets the demand with as many resources and function instances as necessary - but only while needed. Different functions can run anytime you need to respond to critical events. These code blocks are called 'functions'. To meet this need, Azure Functions provides 'compute on-demand' in two significant ways.įirst, Azure Functions allows you to implement your system's logic into readily available blocks of code. Whether you're building a web API, responding to database changes, processing IoT data streams, or even managing message queues - every application needs a way to run some code as these events occur. We often build systems to react to a series of critical events.