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

Using Azure Service Bus Queues

play-arrow
Start course
Overview
DifficultyIntermediate
Duration35m
Students95
Ratings
4.2/5
star star star star star-border

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

The Service Bus in Azure can store messages in a way that decouples the senders or producers from the receivers, which are also called consumers. Decoupling means that the producers and consumers do not need to be online or available at the same time which makes the service a good fit for long running tasks and distributed transactions. Messages are sent and received in a First In, First Out manner. 

ASB queues can handle larger messages sizes compared to Message queues, with an upper limit of 256K. They are also intended for more structured messages which might further be broken down into topics. Another key difference is that you can use the Service Bus for client-facing components with authentication provided by Azure Active Directory. 

With ASB, the receivers of the messages can subscribe to the messages and tune in to the messages that are relevant. As a developer, you may want to give a module access to a single stream of messages where only some of them get used by that module. Service Bus topics are a special kind of queue where you can have multiple subscribers to the same message stream or producer. 

There are a few ways to work with Service Bus queues, which can be useful at design time, including Azure Portal, and the Service Bus Explorer. When you want to put the queue into production, you would first create a namespace and then use the REST API or the .NET Service Bus Libraries.

About the Author

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