Azure Webjobs and functions explained

-

Recently I had questions from my customers asking the differences between Azure web jobs VS Functions. At Prometix we have developed numerous Azure based applications and here is my thought.

In the early days, Azure was a thin veneer over virtual machines, and since then it has grown to the point where,  you need to choose which service to use to host your code. From virtual machines to Azure Functions, we can tune just how much abstraction there is between our application code and the hardware. This article is about picking between two of the abstractions that run furthest from the hardware: WebJobs and Azure Functions.

App Service

Let’s start by talking about App Service, which is the technology that underlies both of these offerings. App Service started its life as a way of hosting applications inside of IIS (Internet Information Services) on Windows. The separation between the applications was provided by IIS and, as such, the configurability and isolation of these services were pretty limited.

However, the cost of those hosting sites was very low. At first, the capabilities were limited to hosting applications in IIS, but this soon changed.

One of the more common requirements for web applications is to be able to run background tasks. Batch processing, scheduled tasks, and long-running processes are all common in modern applications. The issue with running these on IIS is that it consumes one of the precious threads dedicated to serving content and the process may be interrupted by an app pool recycle. There are, of course, some tricks to push off app pool recycles until your task has completed, but ideally, we’d like to run the task outside of IIS. WebJobs were created to provide this capability. Developers can call out to a WebJob via a messaging system such as Storage Queues or Azure Service Bus and have it complete the task while the main application continues on.

WebJobs

WebJobs were the first attempt to solve this problem. WebJobs have built-in triggers for a number of different events inside of Azure: storage queues, blobs, service bus queues, topics and schedule triggers. This means that it is possible, even easy, to set up a WebJob that monitors a blob storage account for new items. Upon discovering a new item, it will be launched to process it.

Deploying WebJobs is quite easy since they deploy using the same infrastructure as any App Service. This allows deploying from source control, FTP, or even Dropbox (but please don’t do that). Deploying from Visual Studio is also possible (again, please don’t do that), although you’re much better off deploying from a continuous build tool such as TeamCity or Visual Studio Team Services (VSTS).

Azure Functions

Azure Functions take the concepts from WebJobs and expand on them. First, Functions enable a whole raft of new trigger types. It is now possible to trigger on such things as Cosmos DB’s change feed, Event Hubs, and WebHooks. As a web developer, the HTTP trigger is one of the most interesting. HTTP triggers enable building an entire website or web application entirely with triggers.

More interesting than the triggers is the change in hosting model. WebJobs are tightly coupled with the App Service plan that hosts them. This means that if you have one WebJob of 20 in a plan that requires additional resources, your only option is to scale the entire App Service plan.

This brings a lot of overhead since now each instance of the App Service is running all the WebJobs. Functions can be deployed using this same model, which may be desirable if you have few to deploy and an existing App Service, or they can be deployed in a pay-per-use model that some refer call Functions as a Service (FaaS) or serverless.

It is paramount that choosing right technology for the correct requirements. Otherwise the model will not cost effective and not serve the purpose.

If you are interested in developing solutions as part Azure environment using. Please contact Prometix for any assistance – enquires@prometix.com.au

Comments

Post a Comment

Popular posts from this blog

Microsoft 365 Records Management Compliance

-
As a SharePoint consulting practice, we at Prometix had a chance to implement a Microsoft 365 Records Management service This is a fairly new service and Microsoft announced in May the commercial release of the Microsoft 365 Records Management service. This service, which lets organisations apply "labels" to documents, as well as machine learning to automatically apply those labels, is designed to address legal compliance tracking issues for organisations. Microsoft claims it'll help demonstrate compliance with regulations through defensible audit trails and proof of destruction. This will assist in integrating with Business Intelligence such PowerBI, and artificial intelligence such as Azure services. The Records Management service is currently available through the  Microsoft 365 Compliance Center . Organisations need to have Microsoft 365 E5/A5 or Microsoft 365 Insider Risk Management licenses to use the service, which gives them the rights to automatically apply ...
Read more

Collaboration with SharePoint VS MS Teams

-
With all the hustle and bustle of the workplace, it can be hard to find exactly what you’re looking for or know who to ask. Defining who is working on what and how they’re involved in the project isn’t always a simple task. Although SharePoint has made managing and sharing content easier, it still isn’t as seamless as its end users would hope. Being able to access content and applications all in one place is useful but doesn’t solve the problem of how to organize information that is only relevant to certain groups. The main goal of SharePoint is to facilitate collaboration, but when content is broadcasted to the entire organization, it can make end users unsure which information applies to them. Microsoft has acknowledged this issue with the creation of its new collaboration tools, SharePoint team sites and Microsoft Teams . These allow end users to create separate areas specifically designed for certain projects they’re working on and for the teams they’re working with. By organizi...
Read more

Data Governance with Azure Purview

-
Image
The modern workplace his a data-centric world. Organisations are always increasing the amount of data they must collect, store, and analyse to inform critical business decisions and measure their organisation’s performance. As data becomes increasingly important, so do the tools needed to discover, manage, and track information in the absence of a data governance program. In the absence of a data governance program, the decisions made about key data systems are made by association staff who “own” the system. When there are different owners for systems (which is very common), the result is inconsistencies in data availability, collection, usability, integrity, and security. This instantly causes data quality problems. It also can negatively impact user experience if there is no integration or procedures to update the existing data within your environment. If you and your organisation find yourselves in such a predicament, Prometix highly recommends deploying an Azure Purview solution....
Read more