Book Image

Serverless computing in Azure with .NET

Book Image

Serverless computing in Azure with .NET

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 (23 chapters)
Title Page
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Version Control System


Version Control System (VCS), also known as source control, is a system that records changes to sets of files, and maintains a history of all the past file versions. A VCS can be used for any type of files, but it is commonly used to track changes in software development projects.

By this point in the book, you may have already checked your project into source control. In fact, you may have done so as soon as you had a working version of your very first function. Being accustomed to using source control creates an automatic desire to commit any meaningful changes, and for a good reason. Using a VCS may seem so obvious that I have questioned whether this book should even cover the source control benefits. There are, however, some scary survey statistics out there claiming that less than 50% of all software projects are in any type of VCS.

I prefer not to make authoritative statements about software development, but I will make this one:

If you are not using source control...