Operations | Monitoring | ITSM | DevOps | Cloud

Recently, I had a scenario in which it was necessary to access the content of the source JSON message and extract a property that contains a date-time. That property was in the last object (a repeating object) for control purposes, and my first idea was to get it done with Azure Function and that’s it. But then I was thinking, if I need to use Function for all these simple tasks, what’s the point?

Azure Functions is a serverless compute service that lets you run event-triggered code without having to explicitly provision or manage infrastructure, in other words, Microsoft’s Azure Functions is a modern serverless architecture, offering event-driven cloud computing that is easy for developers to use. This blog is about Azure Functions triggers and bindings.

You may know my series of blog posts about BizTalk Server Tips and Tricks that I normally write in the BizTalk360 blog. Well, the goal of this Logic Apps Tips and Tricks series will be the same; to provide simple tips or tricks that may improve your performance on developing Logic Apps workflows, avoiding issues, apply best practices and so on. But you may think, “What a strange way to start this topic, deprecated actions? Why should I use deprecated actions?”.

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.