azure-functions-host

> There's not a single widely distributed infra application in C# out there. Azure has entered the chat. Microsoft Orleans has entered the chat. ASP .NET Core has entered the chat. Ever played Halo online? Used StackOverflow? (very likely) Visited any website on Azure? (most likely) Microsoft Orleans (Virtual Actor framework) powers the Halo server infrastructure since at least 2011 if not sooner, which arguably the Halo series is insanely popular, especially for online gaming. Also powers plenty of Azure itselfs own infrastructure. I've worked on dozens of scalable C# projects, and know plenty of devs from all over who have as well. Orleans was so good, EA made their own version in Java which was extensively used there as well, though it looks to be dead, but Orleans is as alive as ever. Not to mention plenty of Azure itself is open sour

As someone whose job involves maintaining uptime of a critical system that's dependent on Cosmos DB this sort of thing is scary. Where there's been other reliability issues with Cosmos before we've not had an understanding customer base, and it feels very out of my control. I'm finding a lot of the reliability guarantees of Azure PaaS services are overblown or come with big caveats when you start to work with them in a serious way. For example I've had some bad reliability issues with Azure Functions not firing, or their premium function runtimes becoming unresponsive. And it seems like that's just the start of the outstanding issues with them https://github.com/Azure/azure-functions-host/issues I think people need to look more carefully at these PaaS guarantees and look at what that 99.999% reliability Microsoft are claiming actually mea

Hi tremon. I work for the Azure Functions team. Sorry for the trouble. This should not happen. We should be giving you a proper response code when the deployment fails. It looks like you are using the sync version of the API but just double checking if you are using the sync or async version ? If you are using the async version then in that case we do return a 201 immediately and then you can use the status url to poll for the status. I would like to dig in and figure out what's happening here. For the PowerShell Az issue as well - it would be good to know what command you were using/what you were trying to do. We dont support deployment of code using the Functions PowerShell Module (https://www.powershellgallery.com/packages/Az.Functions/4.0....). Did you deploy using AZ CLI and then using the PowerShell Module ? You can either share y

The runtime for their serverless functions is also open source and (I guess) fairly portable: https://github.com/Azure/azure-functions-host

With Azure Functions, the runtime[1] is open source, and the development tooling for VSCode makes it easy to run them locally [2], starting up in a few seconds. You pass in your database keys etc as environmental variables, and it integrates nicely with the IoT Hub tooling so you can debug the whole device sends message -> function gets hit flow in one window. However, I have had this break in places before, and not really been able to figure out why from what is going on under the hood, needing to restart various parts to get it working. Checking the contents of the database is annoyingly manual, requiring a seperate GUI only tool[3] and hitting the refresh button a lot, a "watch" window would be much nicer. Profiling once deployed is also difficult, I ended up having to inject timestamps at various different places to try and measure en

It's MIT, and the host is built on .NET Core, so you can run it on Linux if you want: https://github.com/Azure/azure-functions-host Under Satya Nadella the change in Microsoft has been little short of astonishing. A few years ago, I could understand the continued cynicism - but if anything the pace of change has only intensified.

You should of gone a little further, the core tools are for local testing if I remember correctly, but the back-end is here: https://github.com/Azure/azure-functions-host

The Azure Functions (Azure's equivalent to AWS Lambda) Host is open source: https://github.com/Azure/azure-functions-host/ There's probably enough there to bootstrap a container version.

It's coming. The 2.0 runtime and the new out-of-process model required some changes, which are being tracked here: https://github.com/Azure/azure-webjobs-sdk-script/wiki/Azure... But you _can_ use Python right now in the stable runtime--it's just not as nice or full-featured, because of the way the 1.x runtime works. (I work for Microsoft on an unrelated team, and I too am waiting for Python to be back, hoping for 3.6 and asyncio)

We'll have more docs and guidelines on this coming out. Overall, its the same limitations as App Service, if you're familiar with that. We don't have phatomjs working out of the box today, but it's something I'd like to see. Not sure where it will fall on our roadmap. Feel free to file and issue and we can track it there. https://github.com/Azure/azure-webjobs-sdk-script

Whoops. I just added that to my profile. We don't have any current plans for that. Feel free to file a feature request. https://github.com/Azure/azure-webjobs-sdk-script

Slight correction, F# support is broken right now. But its being fixed as we speak :) https://github.com/Azure/azure-webjobs-sdk-script/pull/203

And event hubs? Based on https://github.com/Azure/azure-webjobs-sdk-script/tree/maste... I assume it's also coming soon?

I was waiting for this question to get asked here. :) We don't have any official plans, but because we're open source, you can take a look at how we're doing things and think about adding it yourself later on. We'll have some contributor guidelines up soon. We're going to try to clean up the code and write down a bunch of dev/test guidance this month. https://github.com/Azure/azure-webjobs-sdk-script/wiki