Azure Function Fundamental

This post is to learn about Azure Function. 

What is Azure Function?

Azure Function allow us run a piece of code/ don’t worry about infrastructure (Cloud infrastructure provide all, application scale )

Key Features:

• Serverless: No need to manage or provision infrastructure. Azure takes care of everything for you.
• Event-driven: Functions can be triggered by various events, such as file uploads, database changes, or HTTP requests.
• Pay-per-use: You only pay for the resources consumed during function execution. This makes it a cost-effective option for lightweight, event-driven applications.

Azure Function Pricing Plans

Azure Functions operates on a pay-per-use pricing model, offering flexibility based on how your app scales. There are three main hosting plans:

• Consumption Plan: The default option, where you are billed based on the resources consumed during function execution. This plan automatically scales based on demand.
• Premium Plan: Adds additional features like VNET Integration and more control over scaling, while still following the pay-per-use model.
• Dedicated (App Service) Plan: Allows you to run Azure Functions on dedicated VMs with more predictable scaling and resource allocation.

You can choose a plan based on your application's performance needs and budget. Check out Azure Functions Scaling documentation for more details.

Function Scenarios

Here are some common scenarios where Azure Functions excel:

1. Process File Uploads: Automatically trigger actions such as file validation or transformation when files are uploaded to storage.
2. Run Scheduled Tasks: Create scheduled functions to automate recurring tasks such as sending emails or database maintenance.
3. Build a Scalable Web API: Easily build REST APIs that scale automatically based on traffic.
4. Create a Reliable Messaging System: Azure Functions can integrate with Azure Service Bus or Kafka to process message queues and build asynchronous message-driven systems.

For more examples and use cases, visit Azure Functions Scenarios.

Triggers and Bindings

Azure Functions work based on triggers and bindings that define how a function is activated and how it interacts with other Azure services.

Triggers

A trigger is what causes your function to execute. Some common trigger types include:

• HTTP requests
• File uploads to Azure Blob Storage
• Messages on Azure Service Bus queues or topics
• Timer triggers for scheduled jobs

Bindings

Bindings provide a way to input and output data to and from your function. There are two types of bindings:

• Input Binding: Provides data to your function from a source like a database or a file.
• Output Binding: Sends data to a destination, such as a database or messaging service.

Azure Functions support various types of bindings such as for Azure Blob Storage, Service Bus, Event Hubs, and more.

Dependency Injection in Azure Functions

In a real-world application, your functions may depend on services like databases, caches, or APIs. Azure Functions support dependency injection (DI), which allows you to inject these services into your functions. This is especially useful when your function needs to manage resources or interact with external services.

In Azure Functions, you can configure DI through the IFunctionsHostBuilder interface. There are three service lifetimes you can configure for dependency injection:

• Transient: New instance is created each time the function is invoked.
• Scoped: A new instance is created per request within a function execution.
• Singleton: A single instance is used for the lifetime of the application.

Best Practices for Azure Functions

To make the most of Azure Functions, here are some best practices you should follow:

1. Choose the Correct Hosting Plan: The hosting plan affects how your app is scaled, how instances are allocated, and what resources are available. Ensure that you choose the appropriate plan for your app's size and functionality.
2. Configure Storage Correctly: Azure Functions rely on Azure Storage for managing triggers and logging. Ensure that you have sufficient storage and that it’s configured properly.
3. Organize Your Functions: Functions are deployed together and scale together. It’s essential to keep your functions organized to ensure they work well together.
4. Write Robust Code: Ensure your functions are stateless, avoid long-running operations, and handle errors gracefully.
5. Manage Connections Efficiently: Properly manage connections, whether it's with an HTTP client, Azure client, or SQL client to ensure optimal performance and resource usage.
6. Error Handling and Retry: Azure Functions provides built-in retry policies, including fixed delay and exponential backoff strategies, to handle transient errors effectively.

Developing with .NET

Azure Functions supports .NET, and you can choose between the in-process model and the isolated worker process model.

• In-Process Model: The function executes within the same process as the Azure Functions runtime, allowing for faster execution and easier debugging.
• Isolated Worker Process: A more flexible model that runs the function in a separate process, providing better isolation and allowing the use of features like dependency injection in a .NET standard way.

For more details on developing with .NET, check out the following resources:

• In-process model
• Isolated worker process

Example: C# Isolated Worker Process Model

Check it out here: C# Isolated Worker Functions.

If you refer to a simple version only highlight the keys information, click here