Microsoft Azure Documentation

Home > Azure > Storage > Queue Storage > Basics

Azure Queue Storage: Basics

Azure Queue Storage is a service that stores large numbers of messages that can be processed by a background task. Each message in the queue is typically up to 64 KB in size, and a queue can contain millions of messages up to the capacity limit of the storage account.

What is Queue Storage?

Queue Storage is a common pattern for decoupling applications. It allows different parts of an application to communicate asynchronously. For example:

  • A web application can add a message to a queue to trigger a longer-running process (e.g., image resizing, report generation).
  • Background workers can poll the queue for new messages and process them.
  • It provides a buffer between a web front-end and a backend processing system.

Key Concepts

Understanding the following concepts is essential for working with Azure Queue Storage:

  • Queue: A collection of messages. A queue is identified by a name.
  • Message: A unit of data stored in the queue. Messages are typically strings, but can encode any data, such as JSON.
  • Message ID: A unique identifier for each message.
  • Pop Receipt: A token that must be provided when updating or deleting a message. This ensures that a message is processed by only one consumer at a time.
  • Visibility Timeout: The duration for which a message becomes invisible to other queue consumers after being dequeued. After this timeout, the message reappears in the queue if it hasn't been deleted.

Common Operations

The primary operations you'll perform with Azure Queue Storage include:

  • Add Message: Enqueue a new message.
  • Get Messages: Dequeue one or more messages.
  • Update Message: Update the visibility timeout of a message.
  • Delete Message: Remove a message from the queue.
  • Peek Messages: View messages without dequeuing them.

Use Cases

Azure Queue Storage is ideal for scenarios such as:

  • Asynchronous Processing: Offload time-consuming tasks from a web application to background workers.
  • Load Leveling: Buffer requests to a service that might be under heavy load.
  • Work Distribution: Distribute tasks among multiple worker instances.
Note: Queue Storage is designed for high-throughput, high-volume message queuing. For complex messaging patterns like publish-subscribe or message ordering, consider Azure Service Bus.

Getting Started

To get started with Azure Queue Storage, you'll need:

  1. An Azure subscription.
  2. An Azure Storage account.

You can interact with Queue Storage using:

Example: Adding a message (Conceptual)

Here's a conceptual example of how you might add a message using a client library:


// Assuming you have an initialized QueueClient
await queueClient.SendMessageAsync("ProcessThisOrder");

Example: Dequeuing and Processing a message (Conceptual)

And here's a conceptual example of dequeuing and processing:


// Assuming you have an initialized QueueClient
PeekedMessage[] messages = await queueClient.PeekMessagesAsync(maxMessages: 1);

if (messages.Length > 0) {
    string messageContent = messages[0].Body.ToString();
    Console.WriteLine($"Processing message: {messageContent}");

    // ... process the message ...

    // Delete the message after successful processing
    await queueClient.DeleteMessageAsync(messages[0].MessageId, messages[0].PopReceipt);
    Console.WriteLine("Message processed and deleted.");
}
Important: Always ensure you handle potential errors and implement retry logic when interacting with queues. Messages that cannot be processed may need to be moved to a dead-letter queue.

Explore the following sections for more detailed information on using Azure Queue Storage: