Building and Deploying Azure Functions on NET..png

azurefunctions.tar.gz

Basic Function Job

Function with a HTTP client

Basic Function Job with HTTPS

Azure Functions allows businesses and individual developers to run workloads of varying intensity in the cloud without the need to manage servers. These serverless applications can automatically scale based on demand, ensuring that resources are always available when needed. Azure Functions is also very cost-effective since it bills you only for the functions you use.

In this course, you’ll focus on the .NET implementations of Azure Functions. You’ll start by learning how to build, configure, and deploy these functions. Next, you’ll explore running Azure Functions in a development environment and examine the different types of functions and the various ways to trigger them. Finally, you’ll learn how to orchestrate, scale, and secure Azure Functions.

By the end of this course, you will have gained a comprehensive understanding of the full development cycle of .NET-based Azure functions. You will be equipped to build, deploy, and manage Azure functions in a .NET environment.

Building and Deploying Azure Functions in .NET

Which component is *not* typically used in a durable function?

Which component is not typically used in a durable function?

A parameter of the `IDurableOrchestrationContext` type with the `[OrchestrationTrigger]` attribute.

Any parameter with the `[OrchestrationTrigger]` attribute

A parameter of the `IDurableOrchestrationContext` type

A parameter of the `IDurableOrchestrationContext` type with the `[DurableClient]` attribute

What is a mandatory parameter in an orchestrator in a durable function?

What is a mandatory parameter in an orchestrator in a durable function?

It can be executed like any normal `async` task in C# code.

Only activities can be called by the orchestrator as asynchronous tasks.

Asynchronous tasks cannot be executed from the orchestrator.

Only private and internal `async` tasks can be executed from the orchestrator.

What is the correct way of executing an asynchronous task from the orchestrator of a durable function?

What is the correct way of executing an asynchronous task from the orchestrator of a durable function?

It cannot since it doesn't support asynchronous tasks.

By explicitly putting messages on a queue.

By triggering many of them without awaiting and then awaiting for all of them at the same time.

How can a durable function orchestrator run multiple activities simultaneously?

How can a durable function orchestrator run multiple activities simultaneously?

The orchestrator and all scheduled activities get stopped.

Only the orchestrator is stopped while activities already scheduled still run.

Currently running activities will run to completion, and only then the orchestrator will stop.

When a cancellation of a durable function is triggered, what happens?

When a cancellation of a durable function is triggered, what happens?

Test your knowledge of Durable Functions.

Introduction

Azure Functions Basics

Azure Functions Triggers and Bindings

Using Durable Functions For Long-Running Operations

Azure Functions Reliability and Availability

Scaling Azure Functions

Securing Azure Functions

Conclusion

Appendix

Quiz: Durable Azure Functions