Microsoft Azure Functions

Quick Starts

Azure Functions

Azure Functions are the individual functions created in a Function App. Every Function can be invoked using the configured trigger. Azure portal provides the capabilities to create, manage, monitor and integrate inputs & outputs of the Azure Functions.

An Azure function can also be tested by providing some raw inputs. When it comes to monitoring the Functions, portal offers solutions like Application insights for live status monitoring through the invocation logs. Functions in the Function App can be monitored based on the app metrics.

Runtime Versions

Azure Functions runtimes versions are related to the major version of .NET. Below are the Azure Functions runtime version with equivalent .NET version:

Runtime Version	Availability	.NET Version
3.x	Preview	.NET Core 3.x
2.x	GA	.NET Core 2.x
1.x	GA	.NET Framework 4.6

GA – Generally Available

Azure Function 2.x is Generally available and 1.x is in the maintenance mode. Migrating from 1.x to later version is simple and straight forward which can be done from the Azure portal itself.

How Long Can Azure Functions Run?

For any Azure Functions, a single Function execution has a maximum of 5 minutes by default to execute. If the Function is running longer than the maximum timeout, then the Azure Functions runtime can end the process at any point after the maximum timeout has been reached.

What Languages Does Azure Functions Support?

Azure Function supports multiple languages and it is based on the Runtime versions.

Functions 1.x:

Azure Functions 1.x supports C#, F#, JavaScript. But Functions 1.x is only in maintenance mode.

Functions 2.x:

Azure Functions 2.x supports C# (.NET Core 2.2), JavaScript (Node 8 & 10), F# (.NET Core 2.2), Java 8, PowerShell Core 6, Python 3.7.x, Typescript.

Functions 3.x:

Azure Functions 3.x is a preview version that supports C# (.NET Core 3.x), JavaScript (Node 8 & 10), F# (.NET Core 3.x), Java (Java 8), PowerShell Core 6, Python 3.7.x, TypeScript (Preview).

How Do You Call Azure Function?

Azure Functions can be called when triggered by the events from other services. Being event driven, the application platform has capabilities to implement code triggered by events occurring in any third-party service or on-premise system.

Azure Functions provides templates to get you started with key scenarios, including the following:

• HTTPTrigger-Trigger the execution of your code by using an HTTP request.
• TimerTrigger– Execute clean up or other batch tasks on a predefined schedule.
• CosmosDBTrigger-Process Azure Cosmos DB documents when they are added or updated in collections in a NoSQL database.
• BlobTrigger-Process Azure Storage blobs when they are added to containers. You might use this function for image resizing.
• QueueTrigger-Respond to messages as they arrive in an Azure Storage queue.
• EventGridTrigger-Respond to events delivered to a subscription in Azure Event Grid. Supports a subscription-based model for receiving events, which includes filtering. A good solution for building event-based architectures.
• EventHubTrigger-Respond to events delivered to an Azure Event Hub. Particularly useful in application instrumentation, user experience or workflow processing, and internet-of-things (IoT) scenarios.
• ServiceBusQueueTrigger-Connect your code to other Azure services or on-premises services by listening to message queues.
• ServiceBusTopicTrigger-Connect your code to other Azure services or on-premises services by subscribing to topics.

Proxies

With Azure Function Proxies, user can have a >unified API endpoint for all the Azure Functions consumed by external resources. It is simple to create a proxy URL by only defining the backend URL and HTTP Method. It is also possible to modify the requests and responses of the Proxy. The advanced configurations are also available.

Below is a good read on Azure Function Proxies:

Next steps:

• Introduction to Azure Function Proxies

Slots

With Slots, Azure Functions can run in different instances. The Different environment of Functions can be exposed publicly by the API provided by the slots. When the need is to maintain the Functions by different environment like Production, Development and Staging, Slots will be the choice. An instance will be mapped with the Production environment and It can be swapped on Demand. Swapping can be done either through the portal or Azure CLI.

Concepts

How Do I Make an Azure Function App?

Azure Functions can be built in two ways either through Azure portal or using Visual Studio. Below are the step by step process to create and deploy Azure Functions.

Create Azure Functions in Azure Portal:

1. Click on Create a resource, select on Azure Functions App in Compute section and Click Create
2. Provide the necessary details and create it

To Create Azure Functions in Visual Studio:

1. Select File -> New Project. Select Azure Function project.
2. Provide the necessary details like Name, path, Function App version and Trigger option. Click Create

After creating the Azure Functions in Visual studio, publishing it will be even more easy.

To Publish the Azure Functions from Visual studio:

1. Right Click on the Project Name, Select Publish .
2. Provide the details like Resource group name, storage account and more. After this process, the profile will be created and ready to publish
3. Click Publish. Now the Azure functions can be accessed in read- only mode in the Azure Portal.

Compare 1.x vs 2.x

Azure Functions 1.0 challenges

• Need for additional language support, e.g. Java, Python, PowerShell
• Only able to host on Windows
• No support for development on Mac and Linux
• Assembly probing and binding issues for .NET developers
• Performance issues on a range of scenarios/languages
• Lack of UX guidance to production success

What’s new in Azure Functions 2.0?

• New Functions quick start by selected programming language
• Updated runtime built on .NET Core 2.1 (supported .NET Framework on the previous version)
• Deployment: Run code from a package
• .Net Function loading changes
• Tooling Update: Visual Studio, CLI and VS Code
• Consumption-based SLA

Key differences between Azure Functions 1.0 and 2.0

Some of the highlighted differences between both the versions of Azure Functions are highlighted in the picture,

Bindings and Integration

Previously in Azure Functions 1.0, there were a lot of native bindings available, so the runtime had to be changed in order to make changes to them (Bindings), but in Azure Functions 2.0, the runtime will be developed separately (Version independent) to get more clarity on the extensibility model.

For More details, refer the blog on Azure Functions Internals.

Pricing Details

Azure Function App pricing is based on Execution time and Total Executions. It also includes monthly free grant of 1 million requests and 4,00,000 GB-s of resource consumption per month.

• Execution Time – $0.000016/GB-s
• Total Executions – $0.20 per million executions

With Azure Function Premium plan, user can get the enhanced performance. It is billed based on vCPU-s and GB-s.

• vCPU Duration – $0.173 vCPU/hour
• Memory Duration – $0.0123 GB/hour

Next steps:

• What’s new in Azure Functions

Understanding Metrics

There are exhaustive set of metrics of the Azure Function Apps which can be monitored to detect the performance, availability and reliability of Azure Functions. Below is the detailed list of metrics and their descriptions:

Metric Name	Description	Monitoring Perspective
Average Response Time	The Average time taken for a response from the Function App Unit: Seconds Aggregation: Average Dimension: Entity Name	Performance
Average Memory working set	Average memory consumed by a Function App execution Unit: Bytes Aggregation: Average Dimension: Entity Name	Performance
Function Execution count	Number of Functions executions Unit: Count Aggregation: Total Dimension: Entity Name	Reliability
Thread Count	Number of threads allocated for a function execution Unit: Count Aggregation: Total Dimension: Entity Name	Performance
Http 1xx	Number of Information responses Unit: Count Aggregation: Total Dimension: Entity Name	Availability
Http 2xx	Number of Successful responses Unit: Count Aggregation: Total Dimension: Entity Name	Availability
Http 3xx	Number of Redirection responses Unit: Count Aggregation: Total Dimension: Entity Name	Availability
Http 4xx	Number of Error responses Unit: Count Aggregation: Total Dimension: Entity Name	Availability
Http Server Error	Number of Server Error responses Unit: Count Aggregation: Total Dimension: Entity Name	Availability

What Are Azure Functions Used For?

For Better understanding of the Azure Functions, let’s take a simple Order Processing scenario of an E-Commerce application.

Below is the workflow:

1. Customer places an order in the eCommerce website
2. The website submits a new order message to the Service Bus Queue
3. Azure Function filters all the orders for the focused item (Books) to push them to a Topic
4. The other orders will be sent to a Service Bus Queue
5. The Book order will be further be segregated based on order copy type using Topic Subscription Rules
6. The Azure function will retrieve the price of the ordered Book from the storage table and compute the order price
7. An invoice will be created based on the computed price returned by the function
8. The notification will be sent to the customer with Product details and invoice through Microsoft Outlook

In the Above scenario, there are two Functions used. One validates the product type whether it is a book or other products. And other Function retrieves the price of the book. Both the Functions are used for the validation operation that can be triggered through the Logic Apps.

Where Are Azure Functions Used?

Azure Functions are best suited for smaller apps have events that can work independently of other websites. Some of the common azure functions are sending emails, starting backup, order processing, task scheduling such as database cleanup, sending notifications, messages, and IoT data processing.

Azure Functions Advantages

Being as a cloud service, Azure function has lot of advantages. Some of those advantages are highlighted below:

Pay as you go model- Azure Functions comes in the Pay as you go model. User can pay only for what they use. For Azure functions, cost is based on the Number of Executions per month. Cost structure of Azure Functions are mentioned above in the Pricing Section.

Supports variety of Languages- Azure Function supports major languages like Java, C#, F#, Python and more. Refer above to know more about Azure Functions supported languages.

Easy Integration with Other Azure services – Azure Functions can be easily integrated with the other Azure Services like Azure Service bus, Event Hubs, Event Grids, Notification Hubs and more without any hassle.

Trigger based executions Azure Functions get executed based on the configured triggers. It supports various triggers like HTTP Triggers, Queue Trigger, Event Hub Trigger and more. Being as a trigger-based service, it run on demand. Refer the Trigger section above to know more about the available triggers.

Why Azure Functions Are Serverless?

Functions provides serverless compute for Azure. You can use Functions to build web APIs, respond to database changes, process IoT streams, manage message queues, and more. As Azure Functions can be connected to many other applications running in On-prem or on Cloud, making it a Serverless offering provides better scalability and efficiency.

Azure Durable Functions

Azure Durable Functions is an extension of Azure Function that is used to write Stateful Functions. It consists of Orchestrator function and entity functions that can be defined as a workflow. As a state-based services, it enables checkpoint and restarts from it.

Azure Durable Function supports languages like C#, JavaScript and F#

Orchestrator Client:

The Orchestrator Client is the starting point of the Azure Durable Function. It calls the orchestrator Function which defines the workflow of the orchestration.

Orchestrator Function:

This Orchestrator Function has the workflow of the orchestration. This workflow consists of several pieces of code as Functions named Activity. It may also call other orchestration functions as well. This Orchestrator function is called by an Orchestrator Client.

Activity Function:

Activity Functions are the basic unit of work in a durable function. Each Activity performs an asynchronous task. Activity Function supports all languages that the Azure Function supports. But Orchestration Function can support only C#.

Below are the articles that speaks about Azure Durable Function and its patterns:

Next steps:

• Introduction to Azure Durable Functions
• Azure Durable Functions best practices and patterns

Tools

Application Insights

Application Insights is an Application Performance Management (APM) service for monitoring Application performance and latency. With this tool, user can detect anomalies and diagnose issues. It can be used in various platforms like .NET, Node.js, Java EE, python(preview) and more. It has various capabilities like Smart Detection, API Testing, Failure Detection, Application Map, Live Metrics Stream, Analytics and more. It is also having Integration with Alerts, Power BI, Visual Studio, Rest API and Continuous Export.

Azure Monitor

Azure Monitor can be used to monitor the Azure services in various perspectives. It maximizes the availability and performance of the application or service. This Azure Monitor offers several services like Application Insights, Log Analytics, Alerts and Dashboards. It is also having integration with Power BI, Event Hubs, Logic Apps and API.

Metrics Explorer:

With Metrics Explorer, user can detect the performance, latency of the Application or the service in the chart view. This Metric explorer shows the analytics results based on the filters configured on the extensive set of metrics.

Log Analytics:

Log Analytics is tool used to manage Azure Monitor queries. With Log Analytics, user can perform monitoring and diagnostics logging for Azure Logic Apps. User can also query the log for efficient debugging.

Alerts:

With Alerts in Azure Monitor, user can get the alert report when there is a violation. These Alerts are also based on the metrics that was configured while creating it. Single Alert can only monitor the single Entity based on the couple of metrics configured.

Below is the comparison on Serverless360 vs Azure Monitor:

Are Azure Functions Free?

Azure Functions are billed by pay as you go approach. But for the initial start, Azure provides you free bandwidth of 5GB. Above that will be charged as usage. However, Azure Functions can be used with Azure IoT Edge at no charge.

Serverless360

Azure Function Apps can solve huge business challenges but managing and monitoring them in Azure Portal is quite challenging. So Here comes Serverless360 that offers managing and monitoring the Azure resources in Application context. With Serverless360, Azure Functions can be managed, monitored and analyzed in various perspectives.

Serverless360 Vs Application Insights

Though Application Insights have various features for App services, it is not possible to monitor other services like Azure Service bus, Logic Apps etc., It is also not possible to monitor the Azure entities in application context.

Whereas with Serverless360, it is possible to monitor the entities at the context of the business application and user can also get the consolidated monitoring report that reveals the health status of all the entities with the root cause of error. Serverless360 also provides intelligent automations to ensure the production environment in Enabled state.

With BAM in Serverless360, user can perform end-to-end distributed tracing on the Business processes (i.e., workflow of Logic Apps, Azure Durable Functions or Custom Web Application). Find below the detailed analysis on Serverless360 and Application Insights comparison

Next steps:

• Serverless360 Vs Application Insights