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

Sharing code between functions


As we've seen previously, it is fairly common to need to share code between functions. In the first two examples in this book, we copy-pasted the code that does the text processing. Now, as we move forward and introduce more and more possible inputs, we may want to plug them into a unified processing unit instead of following the error-prone copy-paste process.

A great advantage of encapsulating a common functionality used by the functions in a separate class is the improved testability of the code. The new class will generally have a single responsibility, which can be tested with a suite of unit tests. The test class can rely on Dependency Injection, which is not yet available in function implementation itself. Dependency Injection makes it easier to "mock" any of the external components used in the code. To learn more about Dependency Injection, visit https://en.wikipedia.org/wiki/Dependency_injection

Furthermore, the separation of concerns makes it easier...