But did you ever thought that you can also use this service to host multiple web services which can work in parallel to give the desired output.
Think of a situation below:
"You have three web services each destined to perform a special task and return back a result. Now this result from each service individually doesn't makes any sense. You need to collate all the results, do some data massaging on it and return back the end result to the caller.". Very common scenario nowadays. Right?
Yes you can achieve this by
- Calling each service one-by-one, store their individual result and then write code to prepare the end result
- Azure Durable Functions with Orchestrator controller
- Azure API Management with APIM policies.
This article is not to discourage you from using any of the above but rather intended to give you one more thought process to achieve the same using Azure Logic Apps which is worth a shot. Let's check it out.
[Please note that is article expects you to have the basic understanding of Azure Logic Apps and Functions. You can check on Microsoft Azure documentation for such. 👍]
I will use three very simple web services for this article. The services are nothing but Azure Functions which would simply return an integer value to the caller (in this case the logic app) where all will get summarized before flushing out the end result.
I have used one .Net and two Node.JS HttpTrigger function apps just to give it a multi-language web service flavour. The apps are just returning 10,20 and 30 respectively as their output.
.Net Function app - 01
using System.Net;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Primitives;
using Newtonsoft.Json;
public static async Task<IActionResult> Run(HttpRequest req, ILogger log)
{
log.LogInformation("C# HTTP trigger function processed a request.");
return new OkObjectResult(10);
}
Node.JS Function app - 02
module.exports = async function (context, req) {
context.log('JavaScript HTTP trigger function processed a request.');
var responseMessage = 20;
context.res = {
body: parseInt(responseMessage)
};
}
Node.JS Function app - 03
module.exports = async function (context, req) {
context.log('JavaScript HTTP trigger function processed a request.');
var responseMessage = 30;
context.res = {
body: parseInt(responseMessage)
};
}
We are done with our three web services hosted as Azure Function apps. Cool 😊
Now let's put a Logic App in front which will act as an abstraction layer to all the web services and would give us a single http endpoint to consume. The logic app will call all the web services in parallel (Fan-Out), collect all results (Fan-In), do a summation and would flush out the end result. So, in our case the end result would be 60.. right!
Let's take a bird's eye view of our Logic App
The first three variables are declared to store the respective values from the three web services. The fourth and fifth variable are for doing the summation and final result.
Three web services are fanned-out in parallel as there is no dependency between each other. This will boost the speed as parallel processing is always faster. When all the runs are complete then the flow will be fanned-in for performing the data massaging (i.e. adding all the three results). The fourth and fifth variable are used to store the summation and ultimate flushing out the end result as a response to the caller.
Now our Logic App is in place and we are ready to test. Just copy the Logic App Http endpoint from the workflow and call it from Postman (or any other rest client is just fine). In a moment you will find the output of 60 flashing in your screen. Voila! It just worked as expected and we have successfully showcased a very rich design pattern with the help of Azure Logic App.
Great Job and Congratulations! for coming this far. Hope this article will help you to further explore more on this feature.
Do share with me about your experience and what you have built upon this
foundation. You can take it upto any level and integrate. I would love
to hear from you.