1. Home
  2. Training Library
  3. Microsoft Azure
  4. Courses
  5. Configuring Serverless Computing on Azure

Azure Functions

The course is part of this learning path

play-arrow
Start course
Overview
DifficultyBeginner
Duration1h 20m
Students428
Ratings
4.7/5
star star star star star-half

Description

Course Overview

Learn Configuring Serverless Computing on Azure with this course. Allowing cloud engineers to leverage serverless technologies to deploy solutions is vital to any enterprise. In this course you will learn to do this without the hassle of maintaining actual servers or virtual machines. In addition, this course provides a true insight into the creation of a 'Function App'. This is an interesting feature because creating a basic Function App is actually deceptively easy. Develop your skills with this course by learning exactly how to create a basic Function App. 

We would recommend having an intermediate understanding of MS Azure along with knowledge of its principles and product offerings before starting, ensuring that you yield the maximum potential of the training content. This Azure training content is made up of 11 comprehensive lectures along with an overview and summary.

This course can also be found in the following Learning Paths:

Learning Objectives

  • Learn what serverless computing is and what it offers
  • You’ll learn how to create an Azure Function in the Azure Portal and how to manage Azure Function App settings
  • Learn how to create an automated workflow with Azure Logic Apps
  • Learn about Event Grid and how to use it to monitor for changes in an Azure subscription
  • Learn what Azure Service Bus is and how to use it

Intended Audience

  • IT professionals who are interested in earning Azure certification
  • IT professionals who need to deploy and configure serverless resources in Azure

Prerequisites

  • Access to an Azure tenant to follow along with demos
  • Moderate understanding of Azure

Related Training Content

Transcript

Azure Functions is a serverless computing solution available in Microsoft Azure. Leveraging Azure functions allows you to run small bits of code, otherwise known as functions, in Azure. Instead of writing an entire application or deploying an entire infrastructure to support that application, Azure Functions allows you to just write the code that's needed to perform specific tasks or solve a specific problem. What this does is make development more productive. Azure functions supports numerous development languages, including C, F, Node, Java, and PHP. Because it's billed on a consumption basis, you're only billed for time when code is run, and because it's Azure-based, serverless solutions can be deployed in Azure and they can be scaled when necessary. Key features of Azure Functions include choice of language, pay-per-use pricing, bring your own dependencies, stuff like integrated security, simplified integration, as well as flexible development, and an open-source runtime. 

By offering a choice of language, Azure functions allows you to write functions using your choice of development language. The pay-per-use pricing model allows you to pay only for the time spent running your code, and because Azure Functions supports NuGet and NPM, you can use your favorite libraries, or bring your own dependencies, so to speak. The Integrated security of Azure Functions protects HTTP-triggered functions with OAuth providers, including Azure AD, Facebook, Google, Twitter, and even Microsoft Accounts. The Simplified integration that Azure Functions supports allows you to leverage Azure services, as well as software-as-a-service offerings. With flexible development options, Azure Functions allow you to code functions right from the Azure Portal. However, you can also deploy your code through GitHub, Azure DevOps Services, and other supported development tools. For those that are so inclined, the open-source Azure Functions runtime is also available on GitHub. Azure Functions supports multiple triggers and multiple bindings. A trigger determines how a function is invoked. When coding a function, you can specify exactly one trigger, which will have associated data. 

The data that's associated with a trigger is typically the payload that triggers the function to begin with. Input and output bindings, which are both optional, are used to connect to data from within a function's code, and while a function can only have one trigger, it can have multiple input and output bindings. What triggers and bindings do is allow the developer to avoid hard-coding the details of services that he's working with. For example, a function might receive data in the form of a queue's message content in function parameters. Data can then be sent, for example, to create a queue message by using the return value of the function. When developing functions via the Azure Portal, triggers and bindings are included in a function JSON file. The Azure Portal offers a user interface for this configuration. However, you can also edit the file directly by switching to the advanced editor instead. So what exactly can you do with Azure Functions? Well, whether you need to process data, integrate systems, or build APIs or even do some IoT work, Azure Functions is a great offering to leverage. Virtually any task that needs to be run on a schedule can be addressed with Azure Functions. Common examples would be things like image processing and file maintenance. Built into Azure Functions are several trigger templates that are intended for common usage scenarios. Such trigger templates include those that you see on your screen. 

The HTTP trigger allows you to trigger execution of your code via an HTTP request while the TimerTrigger allows you to execute batch tasks on a predefined schedule. The CosmosDBTrigger processes CosmosDB documents when they are added or updated in collections within a NoSQL database. BlobTrigger allows you to process Azure Storage blobs when they are added to containers, while QueueTrigger allows you to respond to messages when they arrive in an Azure Storage queue. The EventGridTrigger responds to events that are delivered to a subscription in an Azure Event Grid, and EventHubTrigger does the same for events delivered to an Azure Event hub. The ServiceBusQueue and ServiceBusTopicTriggers connect code to other Azure or on-prem services by listening to message queues or by subscribing to topics. So how much does all of this functionality cost? Well, Azure Functions offers two kinds of pricing plans. It offers the Consumption plan and the App Service plan. The Consumption plan provides all necessary compute resources that are needed to run your functions. There's no need to be concerned with resource management. You'll only pay for the time that the code runs. When using the App Service plan, you run your functions just like you would web apps. If you are already using App Service for other apps, you're able to run your functions on the same plan at no additional cost.

About the Author

Students4553
Courses20
Learning paths2

Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.

In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.

In his spare time, Tom enjoys camping, fishing, and playing poker.