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
1
Section 1: Azure Functions 2.0 Fundamentals
5
Section 2: Azure Functions 2.0 Deployment and Automation
10
Section 3: Serverless Orchestration, API Management, and Event Processing
15
Section 4: Real-World Serverless Use Cases

Function types

When you implement Durable Functions, you have three types of function you can use:

  • Client functions
  • Orchestrator functions
  • Activity functions

The relationship between these types of functions is shown in the following diagram:

Let's look at client functions in the following section.

Client functions

The client function is a triggered function (like the standard Azure Function you saw earlier in this book) that can create or manage an orchestrator function.

When you implement a Durable Function, you have at least one client that allows you to start the orchestration.

The client can be triggered using one of the triggers you saw in the previous chapters (for example, HTTP, timer, or queue) and uses an...