Microsoft recently announced its Function as a Service (FaaS) offering Azure Functions now supports Node.js 14 and .NET 5. Developers can develop and deploy function applications leveraging the latest long-term supported (LTS) version of Node.js and the latest version of .NET.
The simultaneous release of both runtimes further evolves the Microsoft Faas offering. Developers can benefit from:
- Node.js 14, bringing more features such as Nullish coalescing and Optional chaining operator, Internationalization and Diagnostic reporting APIs, and ECMAScript modules
- .NET 5 introducing a new isolated process model that runs .NET function apps in a separate worker process outside the Azure Functions host runtime
The .NET 5 release is Microsoft's first iteration of running .NET in a separate process, which gives developers complete control over the application's startup and the dependencies it consumes. There is support for most Azure Functions triggers and binding with the isolated model, yet Durable Functions and rich types support are unavailable. Marc Duiker, Microsoft MVP and lead Azure consultant at Xpirit, told InfoQ:
The Azure Functions in-process model for .NET is a particular situation since all other supported languages are already running in an isolated process. I think the in-process model is both a blessing and a curse. It proved to be a quick way for many .NET developers, such as myself, to try out this new serverless technology and move workloads to a cheaper and more scalable alternative. But since the function code has to run in the same process as the runtime, the development experience was sometimes troublesome when you needed dependencies that we're not compatible, or when more control was required over the process (is it still serverless then?).
Also, he said:
I do think I will miss some of the strongly typed bindings. The idea of having more control over the startup and all dependencies is attractive, though, because it does allow more flexibility in how .NET-based functions are written.
Microsoft follows its competitors AWS and Google, both recently releasing versions of Lamdba- and Function's runtimes supporting Node.js 14. As for .NET, Lamdba and Google Functions support .NET languages such as C#. Microsoft itself also disclosed the future of .NET in the Azure Functions in a Tech Community blog post. The company plans to provide day-one support for future LTS and non-LTS .NET versions.
Source: https://techcommunity.microsoft.com/t5/apps-on-azure/net-on-azure-functions-roadmap/ba-p/2197916
With regards to the future roadmap, Duiker told InfoQ:
The most important thing from the announcement is the Azure Functions Roadmap that provides a rough timeline with the significant .NET versions and the transition from in-process to an isolated process. I welcome this transparency, and I hope more product teams will follow this example. For me, the visibility on Durable Functions compatibility is essential since I use that a lot.
Lastly, Developers can find more guidance and details on starting with .NET 5 for functions using either a command-line interface or IDE's Visual Code- or Studio through the Microsoft documentation page.