Azure WebJob In its own AppService or in an AppService with Api - azure

I have an AppService which hosts an Api. I also have two WebJobs. My question is should I host the WebJobs in the same AppService as the Api or would it be better to host each WebJob in their own AppService.

My question is should I host the WebJobs in the same AppService as the Api or would it be better to host each WebJob in their own AppService.
When you deploy WebJobs, you need to host it in the Azure App Service as a background task. WebJobs is a feature of Azure App Service that enables you to run a program or script in the same context as a web app, API app, or mobile app.
Also, Azure App Service payment is determined by the App Service plan that you run your apps on, while WebJobs is no need for additional cost.
For more details, you could refer to this article.

WebJobs are coupled with App services or Web app in the app service plan and they run as a background task of app service. We can't have an webjob independently running without the web app on the App service plan . We can control the scaling of web job in the case of multiple instance but web job has to be run as background task of app service.

Related

Unable to provision API App on Linux App Service Plan hosted in ASE

Unable to provision API App on Linux App Service Plan hosted in ASE. Is there any constrain or limitations.
When i create API APP Windows app service plans are showing up but not Linux app service plan.
I can reproduce your issue in the portal, looks Linux service plan hosted in ASE v1 not support API App, just Windows plan supports it.

What are the advantages of using Azure App Service to deploy a docker application instead of Azure Container Instance?

What are the advantages of using Azure App Service to deploy a docker application instead of Azure Container Instance?
I found out that Azure Container instances don't have any networking-related capabilities in terms of restricting app access. Are there any more advantages of using Azure App Service to deploy a container?
There are many advantages of using Azure app service over azure container instance
Azure app service is PAAS(platform as a service) on the other side azure container the instance is an IAAS(infrastructure as a service).
In azure app service directly integration of custom domain is available
Integration with the application gateway to handle the traffic load
It offers auto-scaling and high availability.
Automated deployments from GitHub, Azure DevOps, or any Git repo to support a continuous deployment model
Host background jobs(Web Jobs)

Can I change the App Service Plan/App Service to use the App Services Environment

I first created the App Service Plan and App service and later created the App Services Environment. Now I want to change the App Service Plan to use the newly configured ASE, but not able to change it. I created another App Service Plan to use the ASE, but then it was not visible under the Change App Service Plean within App Services.
I created another App Service Plan to use the ASE, but then it was not visible under the Change App Service Plean within App Services.
If apps have already been deployed into existing App Service Plan. Unfortunately there is no straight way option to move to an ASE.
All you can do is to clone it into a new ASP which has been deployed into your ASE or redeploy the app in ASE.
Follow this for more information : Cloning an existing App to an App Service Environment

Publish an Asp.Net Web Api Self-hosted console application as Azure Webjob

I have an ASP.NET Web API Self-host console application and I want to publish it as a Azure Webjob service. Is it possible, is it advisable?.
I'm using Topshelf to install it as a windows service on my local server.
I haven't a web application only the console application.
In a Webjob, no. See Azure App Service sandbox limitations here - assuming you need to listen for inbound requests on a socket.
Installing stuff (think .msi or writing to registry) is also not supported.
Look at Cloud Services (Worker Role), Service Fabric or IaaS VMs.
They're all options.
EDIT (sometime in 2017):
Now there's even more option: Docker containers in Azure App Service Linux, Azure Container Service (DC/OS, Swarm or Kubernetes as orchestrator) or Azure Container Instance.

SignalR on Azure: Web or Worker Role?

I need to deploy my SignalR back-end application on Azure, without any dependency to ASP.NET (I use a console app for testing purposes).
So, I need an Azure Cloud Service, and I don't know if I should go for a worker role or a web role. According to this link, I successfully created a worker role hosting my SignalR app, but I want to know if this is the best way to go.

Resources