Book Image

Serverless computing in Azure with .NET

By : Rosenbaum
Book Image

Serverless computing in Azure with .NET

By: Rosenbaum

Overview of this book

Serverless architecture allows you to build and run applications and services without having to manage the infrastructure. Many companies have started adopting serverless architecture for their applications to save cost and improve scalability. This book will be your companion in designing Serverless architecture for your applications using the .NET runtime, with Microsoft Azure as the cloud service provider. You will begin by understanding the concepts of Serverless architecture, its advantages and disadvantages. You will then set up the Azure environment and build a basic application using a sample text sentiment evaluation function. From here, you will be shown how to run services in a Serverless environment. We will cover the integration with other Azure and 3rd party services such as Azure Service Bus, as well as configuring dependencies on NuGet libraries, among other topics. After this, you will learn about debugging and testing your Azure functions, and then automating deployment from source control. Securing your application and monitoring its health will follow from there, and then in the final part of the book, you will learn how to Design for High Availability, Disaster Recovery and Scale, as well as how to take advantage of the cloud pay-as-you-go model to design cost-effective services. We will finish off with explaining how azure functions scale up against AWS Lambda, Azure Web Jobs, and Azure Batch compare to other types of compute-on-demand services. Whether you’ve been working with Azure for a while, or you’re just getting started, by the end of the book you will have all the information you need to set up and deploy applications to the Azure Serverless Computing environment.
Table of Contents (16 chapters)

Software debugging


Software debugging is an iterative activity involving execution testing and code correction. It differs significantly from implementation testing, which will be covered in the next chapter. Implementation testing is aimed at demonstrating the application's correctness, and can be performed in various ways, some of which might not even involve code execution. Debugging, on the other hand, is aimed at locating and correcting code defects.

Debugging is a multi-step process, which can be outlined by the following process diagram:

As seen in the preceding diagram, the process starts with executing the code under a particular set of conditions, and with a specific end result in mind. The list of possible start conditions used in debugging typically covers the common success and error cases. During debugging, it is important to verify that the code handles errors gracefully in common scenarios, such as incorrect input or inaccessible data store. This means that the "success criteria...