1. Home
  2. Training Library
  3. Microsoft Azure
  4. Courses
  5. Developing Long-Running Tasks on Azure

Asynchronous Messaging

play-arrow
Start course
Overview
DifficultyIntermediate
Duration35m
Students125
Ratings
4.3/5
star star star star star-half

Description

Introduction
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.

Learning Objectives

  • 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

Intended Audience

  • People pursuing the Microsoft AZ-203 certification
  • IT professionals, web developers, DevOps administrators

Prerequisites

  • Basic understanding of cloud concepts
  • Familiarity with web programming
  • Exposure to Azure configuration (Portal, CLI, or PowerShell)

Feedback 
We’d love to get your feedback on this course, so please give it a rating when you’re finished.

Transcript

Before we look at Azure, let's look closer at messaging. The importance of timing allows messaging techniques to fall into two main categories: synchronous and asynchronous. With synchronous queues, the messages go in and come out the other end on a regular schedule, like you would on an automated car wash. Cars go in and come out and you don't have any control over how fast the car wash goes once your car is latched in. 

With asynchronous messaging, you can have new messages arriving at random times. They get stored for a while and then are either pulled out of the queue or simply looked at. This is known as peeking. This is more like the grocery store with multiple cashiers and lanes. During a holiday sale, you may have a flood of customers. At those times, the grocer can add more cashiers increasing their ability to handle and store those customers until they can be looked after. Solutions to the queuing problem show up in mathematics or business as queuing theory and in cloud computing too. 

Most cloud vendors have some sort of queue feature to deal with a flood of messages. There is the message passing interface and a host of open source protocols that you could bring in to provide resilience and buffering. 

In Azure, we want to focus on two features, Storage Queues, and Azure Service Bus. That way, you can leverage the built-in functionality to solve messaging problems. We also want to keep in mind the overall subject of long-running tasks.

About the Author

Students210
Courses2

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.