Queue Storage and reliability

Azure Queue Storage is a service for storing large numbers of messages that you can access from anywhere in the world through authenticated calls using HTTP or HTTPS. Queues are commonly used to create a backlog of work to process asynchronously.

For more information about Queue Storage, reference What is Azure Queue Storage?

To understand how Azure Queue Storage helps maintain a reliable workload, reference the following topics:

The following sections are specific to Azure Queue Storage and reliability:

  • Design considerations
  • Configuration checklist
  • Recommended configuration options
  • Source artifacts

Design considerations

Azure Queue Storage follows the SLA statements of the general Storage Account service.

Checklist

Have you configured Azure Queue Storage with reliability in mind?

Configuration recommendations

Consider the following recommendations to optimize reliability when configuring your Azure Queue Storage:

Recommendation Description
For an SLA increase, use geo-redundant storage. Use geo-redundant storage with read access and configure the client application to fail over to secondary read endpoints if the primary endpoints fail to respond. This consideration should be part of the overall reliability strategy of your solution.
Use geo-zone-redundant storage (GZRS) or read-access geo-zone-redundant storage (RA-GZRS) for durability and protection against failover if an entire data center becomes unavailable. For more information, reference Azure Storage redundancy.

Source artifacts

To identify storage accounts using locally redundant storage (LRS), use the following query:

Resources
| where
    type == 'microsoft.storage/storageaccounts'
    and sku.name =~ 'Standard_LRS'

To identify storage accounts using V1 storage accounts, use the following query:

Resources
| where
    type == 'microsoft.storage/storageaccounts'
    and kind == 'Storage'

Next step