Posted on March 9, 2023
Azure Function App is considered a serverless compute service because it allows developers to write and deploy code without worrying about the underlying infrastructure. Generally, when building and deploying applications, developers have to manage the infrastructure where their code runs, including servers, operating systems, and networking components. This is could take time and complex tasks for developers, especially when scaling up or down the infrastructure to handle demand in applications. Developers only need to write code and define triggers that will execute it. Azure will take care of preparing infrastructure and scaling up and down. A trigger is responsible for initiating the function execution, whereas a binding provides input and output data to the function. Here are some examples of triggers/bindings in Azure Function Apps: Blob Trigger: This trigger is used to execute the function when a new blob is added or deleted from an Azure Blob Storage container. Queue Trigger: This trigger is used to execute the function when a message is added to an Azure Storage Queue. HTTP Trigger: This trigger is used to execute the function when an HTTP request is sent to the function's URL. Timer Trigger: This trigger is used to execute the function on a schedule. Cosmos DB Binding: This binding provides input/output data to the function from/to an Azure Cosmos DB collection. Service Bus Binding: This binding provides input/output data to the function from/to an Azure Service Bus queue or topic. Event Grid Trigger: This trigger is used to execute the function when an event is published to an Azure Event Grid topic. Hit f5 and wait for the following screen to appear. See how we can deploy Azure Function App in this articleAzure Function App
Prerequisite
Triggers/Bindings in Azure Function App
Create a Basic Function App in C# using HTTP Trigger
Using Visual Studio
Or Using Azure Functions Core Tools
func init
Running Azure Function App
HTTP Trigger through GET/POST