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)

B2B disaster recovery

Transactions such as orders, invoices, and shipping notices all involve quite a lot of monetary transactions. Businesses are heavily dependent on the uninterrupted running of their EDI solutions. If for any reason, disaster was to strike and the region in which the B2B solutions are deployed was to go down, business would be halted by the disruption of the transactions. This would be catastrophic for the business. To mitigate the risk of disaster and to ensure business continuity, every EDI provider must provide a disaster recovery plan.

Microsoft's B2B transaction disaster recovery depends on deploying redundant services in different geographical regions. In our scenario, ShipAnyWhere has to implement a disaster recovery plan. They have to deploy all the resources under the ShipAnyWhere-B2B resource group to a new region:

...