Book Image

Mastering Azure Serverless Computing

By : Lorenzo Barbieri, Massimo Bonanni
Book Image

Mastering Azure Serverless Computing

By: Lorenzo Barbieri, Massimo Bonanni

Overview of this book

Application development has evolved from traditional monolithic app development to using serverless options and microservices. This book is designed to guide you through using Microsoft's Azure Functions to process data, integrate systems, and build simple APIs and microservices. You will discover how to apply serverless computing to speed up deployment and reduce downtime. You'll also explore Azure Functions, including its core functionalities and essential tools, along with understanding how to debug and even customize Azure Functions. In addition to this, the book will take you through how you can effectively implement DevOps and automation in your working environment. Toward the concluding chapters, you'll cover some quick tips, troubleshooting techniques, and real-world serverless use cases that will help you make the most of serverless computing. By the end of this book, you will have gained the skills you need to develop and deliver cost-effective Azure serverless solutions.
Table of Contents (19 chapters)
Free Chapter
Section 1: Azure Functions 2.0 Fundamentals
Section 2: Azure Functions 2.0 Deployment and Automation
Section 3: Serverless Orchestration, API Management, and Event Processing
Section 4: Real-World Serverless Use Cases

Creating the release pipeline

In the previous section, you created your first build pipeline to create your artifact. Now is the time to create your first release pipeline in order to deploy an artifact to an environment (for example, Azure).

A release pipeline starts from one or more artifacts and defines one or more stages to deploy them:

The Artifacts box contains all the artifacts that the release pipeline uses. For each artifact, you can configure the trigger (the continuous deployment trigger and pull request trigger) that activates the release. You can also configure schedules for the release (for example, to implement a nightly release).

When a trigger is fired, Azure DevOps creates a new release that is simply a potential release for one of the stages in the pipeline. Then, this new release can run the deployment on one or more stages, depending on the pre-deployment...