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)

Versioning and production testing Logic Apps

Let's consider a scenario in which ShipAnyWhere is building a new version of an already existing Logic App. However, they do not want to roll out the new version to all customers. They would like to test the latest version of the Logic App with a customer, Contoso, who sends a very small number of orders on a daily basis. Once there are no issues found with the new version, it will be rolled out to all trading partners.

In order to achieve this, ShipAnyWhere has decided to make use of Azure APIM's ability to route messages based on content. In this case, Azure APIM needs to check the trading partner. If the trading partner is Contoso, the inbound message must be routed to a new Logic App, and if not, it has to be routed to the old version of the Logic App as shown:

This can be achieved by adding a policy in Azure APIM as...