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

Storing the function results


We previously implemented the result storing procedure in each function separately. In most applications, different functions will serve unrelated purposes and may call different external APIs or store the results in different data stores. In some cases, however, the functions are accessing the same data store in a similar fashion. In such cases, there may be value in implementing this procedure in a shared method to prevent code repetition. Of course, how much code can be reused and how much value the shared method may provide depends on the use case.

Let's demonstrate such a "shared" procedure for storing the data in our SQL Azure database. Keep in mind that the output binding for the table still needs to be defined in each function, but using JObject as the object type allows us to generalize a significant part of the code. We will define a common StoreOutput class to handle the data store.

Since we are treating SQL databases as an external API, this shared...