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

Understanding event delivery and retries

One of the key features that Event Grid provides is the durable delivery of the events that it manages. Event Grid assures you that every message it manages will be delivered, at least once, for each subscription.

Every time an event is received on one of its topics from Event Grid, it will be sent immediately to the corresponding registered endpoint and then to the subscription registered for that endpoint.

If the endpoint doesn't return the acknowledgment for the event (that is, if the event isn't delivered correctly to the subscription), Event Grid will try to deliver the event again.

By default, Event Grid waits for 30 seconds for a timeout after sending an event to an endpoint; then, if the endpoint doesn't respond or responds with an error, Event Grid puts the event in the retry queue.

The retry policy is, as usual...