The last in the series, a walk through on taking our problem statement and implementing it with the new abstraction from the Azure Functions team, Durable Functions
Create a simple workflow orchestration using Azure Functions, executed both sequentially and in parallel
A quick walkthrough on taking the Flow created in Part 1 and upgrading to Azure’s workflow orchestration offering: Logic Apps
A walkthrough of an example using Microsoft Flow to perform a common backend operation: data validation
A walkthrough of creating an Azure Function to convert XML to JSON and vice-versa, including pitfalls and gotchyas of returning XML from Azure Functions
Here’s a quick helper class to make publishing to a custom topic in an Event Grid instance a one-line operation.
Event Grid subscriptions point to an https endpoint. When using Azure Functions as the subscriber, how can you locally debug your events?
While it would be high near impossible to DDoS a solution running on a serverless platform (scaling would just continue to handle all the requests it needed to), somebody still has to pay for the execution. Most (good) serverless implementations use what is often called “micro-billing” whereby you are billed only for each *actual execution* of your code. But, if we think of this nefariously and I send a few thousand requests/second to your endpoints guess what happens. Yup, one hefty bill. This has become known as a Denial of Wallet attack.