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

Using Azure Storage Queues

play-arrow
Start course
Overview
DifficultyIntermediate
Duration35m
Students40
Ratings
5/5
star star star star star

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-300 (Azure Cloud Architect) 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

Storage Queues in Azure fall under the broader category of Azure Storage which includes four main types: blob, table, queue, and SMB files. You must first create a Storage Account and then create the queues which will each have a unique endpoint or connection string for your code to access. 

The messages inside a Storage queue are limited to 64KB in size and are intended for internal communication for your application's internal components. Each Storage queue will have a unique Azure key but for security reasons, it should not be client facing. There is a large storage capacity of up to 500 terabytes and information is retained for up to seven days which makes it great for capturing and storing output from long-running tasks and processes than passing them on to other parts of your application.

About the Author

Students40
Courses1

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.