Azure Web Job - Performance impact of multiple features on the same web job and / or multiple web jobs in the same web application?

Question

There are 3 ways to deploy a new feature through web work:

• Create a new web application and deploy your web work using the function in it.
• Add a new function to an existing web task (so now you have several functions in one web task).
• Add a new web page to the web application (you now have several web tasks in the same web application).

All web tasks and web task functions that are in the same web application are hosted on the same virtual machine, so it is possible that the material impact of all 3 is the same. But I wonder what the difference is.

What is the guide to resolving the issue of how to add a new web job feature to my cloud solution?

• New web application with web service
• or a new web work in an existing web application with other web works.
• or a new feature in an existing web job with other features.

I wonder how it works, leadership, best practices and the impact of performance on these 3 options.

Answer 1

This is a difficult question and I will try to give you some tips. Here are a few things you should keep in mind:

• . , jobhost . , . , . google " ", . , , , , .

• . , 2 . , . , .

• . - ( ). , ( app.config), - , .

• . webjob webapp webapp. - , , -, .

• "": Webjob . . , .

Azure Functions. , , . , : -)

Answer 2

, WebJob (, ..) -. WebJobs -, Azure Web App -, , - , .. best-practices-background-jobs. , Azure Webjobs: 1 , .