Azure Function Apps

Content copied from AI.

Azure Function Apps provide a serverless, event-driven compute service that lets you run code in languages like C#, Python, JavaScript, and Java without managing infrastructure. They scale automatically, offering a cost-effective "pay-per-use" model suitable for processing data, integrating systems, and building APIs.

Key Aspects:

• Serverless Architecture: You focus solely on code, while Azure handles infrastructure, provisioning, and maintenance.
• Event-Driven Triggers: Functions run in response to events, such as HTTP requests, queue messages, or timer schedules.
• Development Flexibility: Supports multiple languages including C#, Java, JavaScript, PowerShell, Python, TypeScript, and more.
• Integration: Easily connects to other services using triggers and bindings without writing extensive code.
• Deployment Options: Allows deployment via the Azure portal, Visual Studio Code, GitHub, and Azure DevOps.
• Task Automation: Executing scheduled tasks or timer-based jobs.
• Security: Inherits security features from Azure App Service, including Azure Active Directory (AD) integration.
• Hosting Plans: Options include Consumption (pay-per-use), Premium (enhanced performance), and Dedicated (App Service plan)

Prerequisites:

1. Visual Studio
2. Azure Subscription

Azure Functions => Trigger types (Most commonly used triggers)

1. HTTP trigger: Triggers your function via HTTP requests.
2. Timer trigger: Executes your function at specified time intervals.
3. Blob trigger: Executes your function on any creation or modification of a blob in Azure Storage.
4. Queue trigger: Executes your function when a new message is added to an Azure Storage queue.
5. Event Grid trigger: Listens for events published by Azure services or custom applications via Azure Event Grid.
6. Service Bus trigger: Listens for messages on an Azure Service Bus queue or topic subscription.
7. Event Hub trigger: Processes events from an Azure Event Hub.
8. Durable Functions: Provides patterns for long running and stateful workflows, including orchestration and chaining of multiple function calls. 
9. Etc, Lof of other trigger also availables.