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

Having multiple instances of the function app, so that it can handle a large volume of incoming requests.

Having additional instances of the function app in case the primary instance fails.

Having multiple endpoints in the app that perform the same task in case any of them fails.

Having a backup of the data representing the state of the Function app.

What is redundancy in the context of Azure Functions?

What is redundancy in the context of Azure Functions?

Metrics represent basic measures, such as counts, while logs represent detailed information.

Logs record what happens inside the application while metrics record what happens inside the host.

Metrics only represent counts while logs represent everything else.

What is the difference between logs and metrics?

What is the difference between logs and metrics?

This setting is not configured via a C# attribute.

If we wanted to apply a retry policy on a timer trigger that would attempt to retry up to 5 times with 10-second intervals, what C# attribute would we use?

If we wanted to apply a retry policy on a timer trigger that would attempt to retry up to 5 times with 10-second intervals, what C# attribute would we use?

If we configure the logging level on our host to `Warning`, what kind of log messages would be recorded in the logs?

If we configure the logging level on our host to <code>Warning</code>, what kind of log messages would be recorded in the logs?

Which logging level would we typically use to record unexpected behavior that doesn't interrupt the flow of the application?

Which logging level would we typically use to record unexpected behavior that doesn’t interrupt the flow of the application?

Test your knowledge on reliability and availability in Azure 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: Azure Functions Reliability and Availability