It is really exciting to see the Azure Functions team back again to the monthly live webcast after quite a long time. Here is a bit of introduction about this webcast who is new to the community, the Azure Functions team at Microsoft has been conducting a webcast every month to let the community stay up-to-date on the latest developments. This is a nice way for them to reach out and engage with the community to gain feedback on the features.

This blog focuses on implementing the Dependency Injection design pattern to the Azure Functions. For a better understanding of Dependency Injection and Azure Function, Let’s take a simple Cab booking validation scenario, in which there will be a Function app implemented with the Dependency Injection that validates the user email Id that is valid or not. Before diving into the orchestration, let us know what the Dependency Injection is.

This blog will brief on Azure Logic App Triggers. Let us see a short introduction of what a Logic App is and how does it work before getting deep into Logic App Triggers.

There are scenarios where we want to de-couple logic across multiple logic apps. Generally, this is a straight forward endeavor, unless the downstream logic app has a long-running process. When this does occur, the client (or publisher) will experience an HTTP timeout if the request takes more than 2 minutes. This scenario is captured within the Azure Logic Apps documentation.

This blog focuses on Dashboard capabilities in Serverless360 and its use cases. Let us take a simple cab booking application scenario to have a better understanding of the Composite Application Dashboard.

Queues are a very common piece of infrastructure. It offers First In, First Out (FIFO) message delivery to one or more competing consumers. As the queue grows the last item added to the queue typically must wait longer to be processed. Just like someone waiting in line to order food, the first one in line gets to order first. Microsoft Azure Service Bus (ASB) is Microsoft’s premier enterprise-level messaging technology that uses this principle of FIFO.

API Management (APIM) helps organizations publish APIs to external, partner, and internal developers to unlock the potential of their data and services. API Management provides the core competencies to ensure a successful API program through developer engagement, business insights, analytics, security, and protection. This blog will cover the key concepts about Azure API Management followed by monitoring them in various perspectives using Serverless360.

This blog will brief on Azure Logic App Expressions. Before getting deep into Logic App expressions let us have a short introduction about Workflow Definition Language in Azure Logic Apps.

Azure Event Grid facilitates building event-driven serverless apps that can effectively solve a real-time business problems with a focus on the core logic rather than the infrastructure. Event Grid is designed for high availability, consistent performance, and dynamic scale. Event Grid can simplify event-based apps, as this serves as a single service to manage routing of all events from any source to any destination. Before we proceed further, it is important to understand what an ‘event’ is.

Calling a flow from another flow is nothing new. Makers can wire up multiple flows using the HTTP Request Trigger and HTTP Action. While this is possible, it creates additional friction as makers have to manually construct request and response messages using JSON. Microsoft recently provided first-class support for calling a flow from another flow by introducing a new action called Run a Child Flow.