Chapter 7: Serverless and Azure Functions

1. In the Consumption pricing model, you pay for each execution of your functions individually.
2. GB-s is the unit of consumption on Azure Functions; it is gigabytes-per-second and defines how much memory was used in a unit of time.
3. Yes, you can, however it is not the advised model of services.
4. It is called a Function App.
5. There was experimental support for this language in the V1 version of Azure Functions. Currently (in V2), it is not supported.
6. Yes—this is how Azure Storage bindings work.
7. When your Function App is deployed automatically, it is set as read-only to avoid manual changes within the process.
8. Not really—in Azure Function, all settings are available via environmental variables.