Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Serverless computing in Azure with .NET
  • Toc
  • feedback
Serverless computing in Azure with .NET

Serverless computing in Azure with .NET

By : Rosenbaum
4.3 (3)
close
Serverless computing in Azure with .NET

Serverless computing in Azure with .NET

4.3 (3)
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)
close

Continuous Integration and delivery


Continuous Integration (CI) is a practice of merging all of the developers' working copies into a shared source control "mainline" frequently, perhaps several times a day.

In the past, some development teams would work on segregated code branches for weeks or even months, implementing somewhat separate features. This created a situation where the project versions grew out of sync, and merging the changes became a very time consuming and painful process of trying to reconcile the versions. This process was referred to as "integration hell". The main purpose of CI is to eliminate these integration issues.

CI is a prerequisite of continuous delivery, and using both is commonly referred to as the CI/CD approach.

Continuous Delivery (CD) is the practice of producing software in short cycles, ensuring that the software can be reliably released at any time. Unlike continuous deployment, CD doesn't aim to push every code change to production, but aims to ensure that...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete