/
How do Azure Functions work ?

How do Azure Functions work ?

In the Consumption and Premium plans, Functions scales CPU and memory resources by adding more function app instances. The number of instances is determined based on the number of events that trigger a function. All functions within a function app share resource within an instance and scale at the same time.

Azure Functions offers built-in integration with Azure Application Insights to monitor functions. Application Insights collects log, performance, and error data. It helps you detect performance anomalies, diagnose issues and better understand how your functions are used.

Azure Functions are based on key components :

  • Function triggers: Triggers are what cause a function to run. A trigger defines how a function is invoked and a function must have exactly ONE trigger.

  • Function bindings: Binding to a function is a way of declaratively connecting another resource to the function; bindings may be connected as input bindings, output bindings, or both.

  • Function runtime: Azure Functions currently supports several versions of the runtime host. Functions also support many different runtimes such as .NET Core, Node.js, Java, PowerShell and Python.

  • API Management: APIM provides security and routing for your HTTP triggered function endpoints as a way to expose them as a true REST API.

  • Deployment slots: Azure Functions deployment slots allow your function app to run different instances called "slots". Slots are different environments exposed via a publicly available endpoint.

  • Function app configuration: Connection strings, environment variables, and other application settings are defined separately for each function app.