Azure Queue storage
What it is
Azure Queue storage is a managed message queue for decoupling application components. Producers add messages to a queue; consumers retrieve and process them asynchronously — smoothing bursts and enabling retry/backpressure without tight coupling.
Why it exists
Web/app tiers often need to hand work to a background worker (e.g., “resize this image”, “send email”). A queue stores that work durably so the producer never blocks and the consumer can scale independently.
Key ideas
- Queue = ordered list of messages within a storage account; URL
<account>.queue.core.windows.net/<queue>. - Message lifecycle: add → becomes visible → consumer dequeues (invisible during visibility timeout) → process → delete. If not deleted before timeout, message becomes visible again (automatic retry).
- Max message size 64 KB (default); base64 optional for binary.
- Not strictly FIFO — no guaranteed ordering across consumers (contrast with Service Bus which offers FIFO/sessions for enterprise messaging).
- Pairing: a poison-message pattern lets misprocessable messages be parked after retries.
How it fits (diagram)
Diagrams courtesy of Microsoft Learn / Azure docs: storage/queues/storage-queues-introduction
Exam notes
- Queue = durable, transient, decoupling; Service Bus = advanced enterprise messaging (FIFO, sessions, topics).
- Message stays until consumed & deleted; visibility timeout governs retries.
- Max 64 KB message default; queues live in a storage account.
- Part of the same storage account namespaces as blobs/tables.
Related
storage-account · azure-tables · blob-storage
📘 Source: Microsoft Learn — Azure Queues