I’ve created some Azure Webjobs that use triggers and I’ve just learnt about Azure Functions.
From what I understand Azure Functions seem to overlap with Azure Webjobs features and I have some difficulty to understand when to choose between Function and Webjob:
-
Unlike Webjobs, Functions can only be triggered, it hasn’t been designed to run continuous process (but you can write code to create a continuous function).
-
You can write Webjobs and Functions using many languages (C#, node.js, python …) but you can write your function from the Azure portal so it is easier and quicker to develop test and deploy a Function.
-
Webjobs run as background processes in the context of an App Service web app, API app, or mobile app whereas Functions run using a Classic/Dynamic App Service Plan.
-
Regarding the scaling, Functions seems to give more possibilities since you can use a dynamic app service plan and you can scale a single function whereas for a webjob you have to scale the whole web app.
So for sure there is a pricing difference, if you have an existing web app running you can use it to run a webjob without any additional cost but if I don’t have an existing web app and I have to write code to trigger a queue should I use a webjob or a Function ?
Is there any other considerations to keep in mind when you need to choose ?
