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)

Example 3 – Messages with API Management, Event Grid, Logic App, and Azure Functions

In this example, we are going to describe how we can broadcast custom messages using API Management, Azure Event Grid, and Logic Apps, with Azure Functions, Logic Apps, and a web app as a listener to the broadcasted messages. The high-level architectural overview of the solution is as follows:

When working with third-party enterprise solutions, it is always advisable to make your integration solution flexible enough to onboard new solutions and patterns. In the broadcast pattern, we used the API Management layer in front of Azure Event Grid to secure the Event Grid backend resource. This process provides sufficient flexibility to modify security properties such as the authentication type, the security key, or the rate policy:

  1. For this implementation, the first step is creating a new instance...