Book Image

Enterprise Integration with Azure Logic Apps

By : Matthew Bennett
Book Image

Enterprise Integration with Azure Logic Apps

By: Matthew Bennett

Overview of this book

Logic Apps are a visual flowchart-like representation of common programming actions, and are a flexible way to create logic without writing a single line of code. Enterprise Integration with Azure Logic Apps is a comprehensive introduction for anyone new to Logic Apps which will boost your learning skills and allow you to create rich, complex, structured, and reusable logic with instant results. You'll begin by discovering how to navigate the Azure portal and understand how your objects can be zoned to a specific environment by using resource groups. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will teach you the benefits and foundations of Logic App logic design. As you advance, you'll find out how to manage your Azure environment in relation to Logic Apps and how to create elegant and reliable Logic Apps. With useful and practical explanations of how to get the most out of Logic App actions and triggers, you'll be able to ensure that your Logic Apps work efficiently and provide seamless integration for real-world scenarios without having to write code. By the end of this Logic Apps book, you'll be able to create complex and powerful Logic Apps within minutes, integrating large amounts of data on demand, enhancing your systems, and linking applications to improve user experience.
Table of Contents (17 chapters)
1
Section 1: Logic App Fundamentals
7
Section 2: Logic App Design
13
Section 3: Logic App Maintenance and Management

The impact of losing messages

If you are planning to use the HTTP POST action, please bear in mind that this is different from a Request/Response action in that HTTP POST sends the message but does not read the output (it operates on the fire and forget principle). Therefore, if you are sending to a resource that could be busy, will the message be actioned? If the resource is turned off, do you have a mechanism to be able to rerun the message at a later point? Here, setting the retry policy to the default (four tries) when sending a Web API message that inserts a record into a database would not be a good idea as the HTTP call could be sent four times. The record you are trying to add will effectively be added to the database four times!

For this reason, when using HTTP calls to keep systems in sync, I always set Retry Policy to None:

Figure 9.9 – Setting Retry Policy to None

Therefore, by setting the policy to none, we can avoid additional and unwanted...