Queue storage basics in Azure - Mini Project: Build & Apply

Queue storage basics

📖 Scenario: You are building a simple messaging system using Azure Queue Storage. This system will store messages in a queue to be processed later by other services.

🎯 Goal: Create an Azure Queue Storage setup with a queue named taskqueue. Add a message to the queue and configure the queue properties.

📋 What You'll Learn

Create a queue client for the queue named taskqueue

Add a message with the exact text 'Process this task' to the queue

Set the queue's metadata with a key environment and value development

💡 Why This Matters

🌍 Real World

Azure Queue Storage is used to decouple components in cloud applications by storing messages that can be processed asynchronously.

💼 Career

Understanding queue storage basics is essential for cloud developers and architects to build scalable and reliable distributed systems.

1

Create the queue client

Create a variable called queue_client using QueueClient from azure.storage.queue with connection string conn_str and queue name 'taskqueue'.

Azure

from azure.storage.queue import QueueClient

conn_str = "DefaultEndpointsProtocol=https;AccountName=examplestorage;AccountKey=examplekey;EndpointSuffix=core.windows.net"

# Create queue_client for 'taskqueue'
# Your code here

Hint

Use QueueClient.from_connection_string with conn_str and 'taskqueue'.

2

Create the queue if it does not exist

Call the create_queue() method on queue_client to create the queue if it does not already exist.

Azure

from azure.storage.queue import QueueClient

conn_str = "DefaultEndpointsProtocol=https;AccountName=examplestorage;AccountKey=examplekey;EndpointSuffix=core.windows.net"

queue_client = QueueClient.from_connection_string(conn_str, "taskqueue")

# Create the queue if it does not exist
# Your code here

Hint

Use queue_client.create_queue() to ensure the queue exists.

3

Add a message to the queue

Use the send_message() method on queue_client to add the message 'Process this task' to the queue.

Azure

from azure.storage.queue import QueueClient

conn_str = "DefaultEndpointsProtocol=https;AccountName=examplestorage;AccountKey=examplekey;EndpointSuffix=core.windows.net"

queue_client = QueueClient.from_connection_string(conn_str, "taskqueue")

queue_client.create_queue()

# Add message 'Process this task' to the queue
# Your code here

Hint

Call queue_client.send_message() with the exact string 'Process this task'.

4

Set metadata on the queue

Set the metadata of queue_client to a dictionary with key 'environment' and value 'development' using the set_queue_metadata() method.

Azure

from azure.storage.queue import QueueClient

conn_str = "DefaultEndpointsProtocol=https;AccountName=examplestorage;AccountKey=examplekey;EndpointSuffix=core.windows.net"

queue_client = QueueClient.from_connection_string(conn_str, "taskqueue")

queue_client.create_queue()

queue_client.send_message('Process this task')

# Set metadata with {'environment': 'development'}
# Your code here

Hint

Use queue_client.set_queue_metadata() with the correct dictionary.

Practice

1. What is the main purpose of Azure Queue Storage?

easy

A. To store messages that help different parts of an app communicate

B. To store large files like videos and images

C. To run virtual machines in the cloud

D. To create databases for storing user data

Solution

1. Step 1: Understand the role of Azure Queue Storage

   Azure Queue Storage is designed to hold messages temporarily so different parts of an application can send and receive information reliably.

2. Step 2: Compare options with this purpose

   Options B, C, and D describe other Azure services like Blob Storage, Virtual Machines, and Databases, which are not for message passing.

3. Final Answer:

   To store messages that help different parts of an app communicate -> Option A

4. Quick Check:

   Queue Storage = Message storage for app communication [OK]

Hint: Queue Storage is for messages, not files or VMs [OK]

Common Mistakes:

• Confusing queue storage with blob storage
• Thinking queue storage runs code or VMs
• Mixing queue storage with database services

2. Which of the following is the correct way to add a message to an Azure queue using Azure SDK syntax?

easy

A. queueClient.addMessage('Hello World')

B. queueClient.sendMessage('Hello World')

C. queueClient.enqueueMessage('Hello World')

D. queueClient.pushMessage('Hello World')

Solution

1. Step 1: Recall Azure Queue Storage SDK method for adding messages

   The correct method to add a message to a queue is sendMessage.

2. Step 2: Check other options for correctness

   Methods like addMessage, enqueueMessage, and pushMessage are not valid Azure SDK methods for queues.

3. Final Answer:

   queueClient.sendMessage('Hello World') -> Option B

4. Quick Check:

   Send message = sendMessage() method [OK]

Hint: Use sendMessage() to add messages to Azure queues [OK]

Common Mistakes:

• Using incorrect method names like addMessage or pushMessage
• Confusing queue methods with blob storage methods
• Forgetting to call the method on the queue client object

3. Given this code snippet, what will be the output after reading the message?

const { QueueClient } = require('@azure/storage-queue');
const queueClient = new QueueClient('https://myaccount.queue.core.windows.net/myqueue', credential);

async function readMessage() {
  const response = await queueClient.receiveMessages();
  if (response.receivedMessageItems.length > 0) {
    return response.receivedMessageItems[0].messageText;
  } else {
    return 'No messages';
  }
}

readMessage().then(console.log);

medium

A. The text of the first message in the queue

B. An error because receiveMessages() does not exist

C. No messages if the queue is empty

D. The number of messages in the queue

Solution

1. Step 1: Understand receiveMessages() behavior

   The receiveMessages() method fetches messages from the queue. If messages exist, they are in receivedMessageItems.

2. Step 2: Analyze the code logic

   If there is at least one message, the code returns the text of the first message. Otherwise, it returns 'No messages'.

3. Final Answer:

   The text of the first message in the queue -> Option A

4. Quick Check:

   receiveMessages() returns messages array [OK]

Hint: receiveMessages() returns messages array, pick first text [OK]

Common Mistakes:

• Thinking receiveMessages() returns count or error
• Ignoring the check for empty message list
• Confusing method names or properties

4. You wrote this code to delete a message from an Azure queue but it fails:

const response = await queueClient.receiveMessages();
const message = response.receivedMessageItems[0];
await queueClient.deleteMessage(message.messageId);

What is missing to fix the error?

medium

A. You should use removeMessage() instead of deleteMessage()

B. You must call sendMessage() before deleteMessage()

C. You need to provide the message's popReceipt along with messageId to delete

D. No fix needed; the code is correct

Solution

1. Step 1: Understand deleteMessage() requirements

   To delete a message, Azure requires both the messageId and the popReceipt which proves you received the message.

2. Step 2: Identify missing parameter in code

   The code only passes messageId but misses popReceipt, causing failure.

3. Final Answer:

   You need to provide the message's popReceipt along with messageId to delete -> Option C

4. Quick Check:

   Delete needs messageId + popReceipt [OK]

Hint: Delete message requires popReceipt with messageId [OK]

Common Mistakes:

• Passing only messageId to deleteMessage()
• Using wrong method name like removeMessage()
• Assuming sendMessage() is needed before delete

5. You want to build a system where multiple workers process messages from an Azure queue without processing the same message twice. Which approach best achieves this?

hard

A. Workers use peekMessages() to read messages and delete them immediately

B. Workers read messages but never delete them, so messages stay in the queue

C. Workers delete messages before processing to avoid duplicates

D. Each worker calls receiveMessages(), processes the message, then deletes it using messageId and popReceipt

Solution

1. Step 1: Understand message processing with Azure queues

   To avoid duplicate processing, workers must receive messages, process them, then delete them to remove from the queue.

2. Step 2: Evaluate each option

   Each worker calls receiveMessages(), processes the message, then deletes it using messageId and popReceipt correctly describes the receive-process-delete cycle with required parameters. Workers read messages but never delete them, so messages stay in the queue leaves messages undeleted causing duplicates. Workers delete messages before processing to avoid duplicates deletes before processing risking lost messages. Workers use peekMessages() to read messages and delete them immediately uses peekMessages() which does not lock or remove messages, so duplicates occur.

3. Final Answer:

   Each worker calls receiveMessages(), processes the message, then deletes it using messageId and popReceipt -> Option D

4. Quick Check:

   Receive, process, then delete to avoid duplicates [OK]

Hint: Process then delete messages to prevent duplicates [OK]

Common Mistakes:

• Deleting messages before processing
• Using peekMessages() for processing
• Not deleting messages after processing