Book Image

Serverless Integration Design Patterns with Azure

By : Abhishek Kumar, Srinivasa Mahendrakar
Book Image

Serverless Integration Design Patterns with Azure

By: Abhishek Kumar, Srinivasa Mahendrakar

Overview of this book

With more enterprises adapting cloud-based and API-based solutions, application integration has become more relevant and significant than ever before. Parallelly, Serverless Integration has gained popularity, as it helps agile organizations to build integration solutions quickly without having to worry about infrastructure costs. With Microsoft Azure’s serverless offerings, such as Logic Apps, Azure Functions, API Management, Azure Event Grid and Service Bus, organizations can build powerful, secure, and scalable integration solutions with ease. The primary objective of this book is to help you to understand various serverless offerings included within Azure Integration Services, taking you through the basics and industry practices and patterns. This book starts by explaining the concepts of services such as Azure Functions, Logic Apps, and Service Bus with hands-on examples and use cases. After getting to grips with the basics, you will be introduced to API Management and building B2B solutions using Logic Apps Enterprise Integration Pack. This book will help readers to understand building hybrid integration solutions and touches upon Microsoft Cognitive Services and leveraging them in modern integration solutions. Industry practices and patterns are brought to light at appropriate opportunities while explaining various concepts.
Table of Contents (15 chapters)

Event filtering through Azure Event Grid subscription

In this section, we will describe the different ways to filter events when we create an Event Grid listener endpoint through subscription. An Azure Event Grid topic provides us with three options to filter out the event of our choosing:

  • Event type filtering
  • Subject filtering
  • Advanced fields and operators

Event type filtering

By default, all the events broadcast via Event Grid should have the event type property in the actual event payload. We can use the event type within the filter condition to route events to the specified listener, which can then process those events. When filtering events on a subscription level, end client listeners can be saved from throttling conditions...