Introduction

A middleware is a software service that glues together multiple services. In today’s business needs, multiple software services and technologies need to work together and communicate with each other. It is not necessary that these distributed software services are compatible with each other and will be able to communicate.

Example Business Case

We have to develop a software service in which we have geo-coordinates of a location and we need to get weather information of the city based on those coordinates. We have a system X that needs to communicate with another system Y. These are distributed systems. System X has information about geo coordinates and system Y will store weather information of the city based on those coordinates.

Solution

We will develop a middleware between system X and system Y.

Middleware Architecture

1. System X will send geo coordinates to the receiver service (Http Triggered Azure Function) of the middleware in JSON format.
2. Receiver service will call reverse geocoder API and will extract city name from the response and finally sends the city name to the Service Bus queue.
3. Sender service will receive city name from service and call weather API and send weather data to System Y (Service Bus Queue Triggered Function).
4. System Y will receive weather information from the sender service and store it (For sake of simplicity, we will log the information at Sender Service).

Prerequisites

1. Microsoft Azure Subscription.
2. Deployed Service Bus resource on Microsoft Azure Portal.
3. Postman for testing
4. Visual Studio 2019
5. .NET Core 3.1

#functions #microsoft azure service #microsoft azure #azure