Azure Functions is an event-driven serverless compute platform in Azure and Azure Stack. Its open-source runtime also works on multiple destinations including Kubernetes, Azure IoT Edge, on-premises, and other clouds.

- Wiki
16 articles, 0 books.

"Serverless Computing" doesn't really mean there's no server. Serverless means there's no server you need to worry about. That might sound like PaaS, but it's higher level that than.

In this blog post, we will discuss an Azure Service called Azure Functions and how we can use them within a Logic App. Azure Functions has gone GA (General Available) on 15th of November 2016 and provides a capability of running small pieces of code in Azure.

Azure Functions is serverless computing offer by Microsoft. Functions by Microsoft implementation are scripts that can be written in JavaScript, C#, F#, Python, PHP, Bash, Batch or PowerShell. Functions can be developed on Visual Studio using preview level tools or directly through browser in Azure portal. This blog post introduces Azure Functions and shows how to build your first function.

Azure Functions get you beyond the traditional client/server approach to app creation, right into the cloud.

There are a number of events that can cause functions to begin execution ("triggered"), one of which is in response to an HTTP request. These HTTP-triggered functions could, for example, perform CRUD operations for a single-page Web app or mobile front-end.

The consumption plan for Azure Functions is capable of scaling your app to run on hundreds of VMs, enabling high performance scenarios without having to reserve and pay for huge amounts of compute capacity up front.

I’m going to show you how you can move long running tasks such as PDF/report generation from your MVC website to their own Micro Service using Azure Functions.

Nowadays, people tend to search for things that are nearby. Search phrases include the words “near me”. This basically means, that people, for example, search for restaurants that are close to their current location. According to Google on-demand searches are actually one of the most common searches.

Azure Durable Functions is a new programming model based on Microsoft serverless’ platform Azure Functions. It allows you to write a workflow as code and have the execution run with the scalability and the reliability of serverless with high throughput.

A recent analysis of AWS customers discovered that serverless adoption is growing 2.5x faster than the adoption of server containers. From this, it becomes clear that serverless architecture in cloud computing is a ‘must have’ for companies now and in the future.

For the most part, Have I Been Pwned (HIBP) runs very smoothly, especially given how cheaply I run many parts of the service for. Occasionally though, I screw up and get something wrong that interrupts the otherwise slick operation and results in some outage. Last weekend was one such occasion and I want to explain what I got wrong, how you might get it wrong too and then, of course, how to fix it.

Oh no! Not more jargon! What exactly does the term Durable Functions mean? Durable functions have to do with Serverless architectures. It’s an extension of Azure Functions that allow you to write stateful executions in a serverless environment.

Taking one of the biggest downsides of serverless and making it work for you.

In this article, we'll look at how we can use Azure Functions and SignalR Service to broadcast real-time document changes in Azure Cosmos DB to clients over WebSockets.

This is the first part in a series demonstrating how to setup continuous deployment of an Azure Functions App using Azure DevOps build and release pipelines.

Azure Functions are awesome because they're "serverless" which, in theory at least, means no logical infrastructure boundaries and you simply pay per execution. Except there are boundaries.