Azure Queue Storage

azure Queueazure-queue-storage

Managed at-least-once message queue in a storage account; 64 KiB messages kept seven days by default.

Provider: azure
Kind: Queue
Category: Messaging
Official docs: https://learn.microsoft.com/en-us/azure/storage/queues/storage-queues-introduction

Properties · 5 set by this component

property	type	values	required	kind default	this component
backoff	enum	none \| fixed \| exponential \| exponential-jitter	no	—	inherited
deadLetterQueue	boolean	—	no	false	inherited
delivery	enum	at-most-once \| at-least-once \| exactly-once	yes	—	▸ at-least-once
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ true
maxAttempts	integer	—	no	—	inherited
maxMessageSizeKib · component property	integer	—	no	64	inherited
maxMessagesPerRead · component property	integer	—	no	1	inherited
ordering	enum	none \| per-key \| global	no	none	▸ none
persistence	boolean	—	no	true	▸ true
redundancy · component property	enum	lrs \| zrs \| grs \| gzrs \| ra-grs \| ra-gzrs	no	lrs	inherited
replay	boolean	—	no	false	inherited
retentionDays	integer	—	no	—	▸ 7
role	enum	work \| dlq \| retry \| offline-mailbox \| frontier	no	work	inherited
visibilityTimeoutSeconds · component property	integer	—	no	30	inherited

Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Queue without dead-letter queueerror

queue-missing-dlq

A queue that receives asynchronous traffic and has no dead-letter queue either drops poison messages or retries them forever. Neither outcome leaves anything for a human to investigate.

— all of these hold:
— the node's `deadLetterQueue` is false
— the node has at least one asynchronous incoming edge

Retry queue without dead-letter queueerror

retry-queue-without-dlq

A retry queue is where poison messages end up. With no dead-letter queue they are retried forever or dropped in silence, and nobody ever looks at the failed payment.

— all of these hold:
— the node's `role` is "retry"
— the node's `deadLetterQueue` is false

Retry queue without backoffwarning

retry-without-backoff

Retrying a transient failure at full speed turns one slow dependency into a retry storm. A retry queue backs off, preferably exponentially and with jitter.

— all of these hold:
— the node's `role` is "retry"
— any of these hold:
— the node's `backoff` has no value
— the node's `backoff` is "none"

Use it in a design

nodes:
  - { id: "queue-storage", component: "azure-queue-storage" }

Other Queue products · 23

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Azure Queue Storage: managed point-to-point queue in a storage account. A retrieved message is
3# only hidden for the visibility timeout and reappears if it is not deleted, so delivery is
4# at-least-once; the default message time-to-live is seven days ("Introduction to Azure Queue
5# Storage", "Get Messages (REST API)").
6schemaVersion: "1"
7type: "component"
8id: "azure-queue-storage"
9kind: "queue"
10provider: "azure"
11docs: "https://learn.microsoft.com/en-us/azure/storage/queues/storage-queues-introduction"
12defaults:
13  delivery: "at-least-once"
14  ordering: "none"
15  persistence: true
16  retentionDays: 7
17  managed: true
18properties:
19  maxMessageSizeKib:
20    type: "integer"
21    default: 64
22  visibilityTimeoutSeconds:
23    type: "integer"
24    default: 30
25  maxMessagesPerRead:
26    type: "integer"
27    default: 1
28  redundancy:
29    type: "enum"
30    values: ["lrs", "zrs", "grs", "gzrs", "ra-grs", "ra-gzrs"]
31    default: "lrs"

The same page as markdown, for an agent: /catalogue/components/azure-queue-storage.md