Node.js vs C# for Azure Functions : How to choose regarding performance and integration

Question

Node.js and C# are both described as 1st class support in Azure Functions.

Is there any comparative documentation (or feedback) on using Node.js vs C#?

My concerns are about Azure integrations and performances

What are the use cases on choosing either Node.js or C# (except language preference)

Answer 1

We're working hard to make sure there are no functional gaps between the first class languages like C# and Node.

You may notice small performance differences between the two depending on the scenario, but we're trying to make sure those are negligible (for example, currently, you may notice slower startup time with C# because of compilation requirements, but we'll be addressing that by GA, from there, C# functions are executed from a compiled assembly)

C# does offer some deeper integration with the model exposed by the WebJobs SDK, allowing you to bind to any supported binding type, but in Node, we offer mechanisms to address most of the scenarios that would require specific binding types.

Again, we are committed to providing a great experience for the first class languages we support and the choice will come down to personal preference/project requirements.

Answer 2

In terms of features and performance, you will most likely not notice any significant differences. However in terms of ecosystem and popularity , C# is the clear winner. C# docs are better, there's more C# tutorials, mode SO threads and more useful libraries written in C#.

A good example is the official C# swagger/openAPI extension that allows you to auto generate docs for your functions-based REST APIs. Good luck searching for something similar with Node/Python.