The course is part of this learning path
This Course will show practical applications of key Azure features to meet the programming and configuration challenges introduced by long-running tasks.
We'll start with Azure Batches and how you can use them to create large-scale, parallel, and high-performance apps in the Azure cloud. Then we'll go over Azure Queues and how they can add resiliency to your web applications. Next, you'll look at Webhooks and how they can address events in your cloud apps. Finally, we'll show you WebJobs and how they can deal with continuous processing tasks.
By the end of this Course, you should be able to understand and apply these four Azure features to solve some of the challenges you face with long-running tasks, especially in high-performance computing applications.
- Create large-scale, parallel, and high-performance apps by using Azure Batches
- Build resilient apps by using Azure Queues
- Implement code to address application events by using Azure Webhooks
- Address continuous processing tasks by using Azure WebJobs
- People pursuing the Microsoft AZ-300 (Azure Cloud Architect) certification
- IT professionals, web developers, DevOps administrators
- Basic understanding of cloud concepts
- Familiarity with web programming
- Exposure to Azure configuration (Portal, CLI, or PowerShell)
We’d love to get your feedback on this Course, so please give it a rating when you’re finished.
You may want to run these smaller jobs on a regular basis or after an event that triggered it. You might even want to kick it off manually from the portal or on demand. By design, you have two types of WebJob that you can choose from.
One choice is a continuous WebJob that runs in a loop. You can start, stop and delete them as needed. Examples of this could be providing a console for administrative access or sending email notifications. Some other ideas could be processing queued messages, aggregating RSS feeds, processing images to change the resolution, and any other long-running task that might need to run in a background thread.
The other type is triggered. A triggered WebJob starts only when triggered manually or on a schedule. You could use a triggered WebJob to occasionally clean up the back-end files and data in your web app for example.
Continuous WebJobs support remote debugging. This comes in handy for long-running tasks as you may want to inspect the status over a period of time.
About the Author
Derrick is a content contributor and trainer for Microsoft cloud technologies like Azure, Office 365 and Dynamics 365. He works across North America and Europe to help companies and organizations with these technology shifts. Before that he has worn many hats but prefers to wear them one at a time.
When he is not night walking during his travels, you can find him on a bicycle path or performing guitar solos to an imaginary audience in his basement.