ApsaraMQ for RabbitMQ

Managed AMQP 0-9-1 broker compatible with the open-source RabbitMQ clients.

Provider: alibabacloud
Kind: Queue
Category: Messaging
Official docs: https://www.alibabacloud.com/help/en/apsaramq-for-rabbitmq

Properties · 3 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
ordering	enum	none \| per-key \| global	no	none	inherited
persistence	boolean	—	no	true	▸ true
protocol · component property	enum	amqp-0-9-1	no	amqp-0-9-1	inherited
replay	boolean	—	no	false	inherited
retentionDays	integer	—	no	—	inherited
role	enum	work \| dlq \| retry \| offline-mailbox \| frontier	no	work	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: "rabbitmq", component: "alibaba-rabbitmq" }

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# ApsaraMQ for RabbitMQ: a managed AMQP 0-9-1 broker compatible with the open-source RabbitMQ
3# clients ("What is ApsaraMQ for RabbitMQ"). RabbitMQ acknowledges and redelivers, so delivery is
4# at-least-once; queues are durable. A dead letter exchange is set per queue.
5schemaVersion: "1"
6type: "component"
7id: "alibaba-rabbitmq"
8kind: "queue"
9provider: "alibabacloud"
10docs: "https://www.alibabacloud.com/help/en/apsaramq-for-rabbitmq"
11defaults:
12  managed: true
13  delivery: "at-least-once"
14  persistence: true
15properties:
16  protocol:
17    type: "enum"
18    values: ["amqp-0-9-1"]
19    default: "amqp-0-9-1"

The same page as markdown, for an agent: /catalogue/components/alibaba-rabbitmq.md