ApsaraMQ for RocketMQ

Distributed message queue for asynchronous communication, with ordered, transactional and scheduled messages.

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

Properties · 4 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
instanceVersion · component property	enum	4.x \| 5.x	no	—	inherited
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ true
maxAttempts	integer	—	no	—	inherited
messageType · component property	enum	normal \| ordered \| transactional \| scheduled	no	normal	inherited
ordering	enum	none \| per-key \| global	no	none	inherited
persistence	boolean	—	no	true	▸ true
replay	boolean	—	no	false	▸ true
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: "rocketmq", component: "alibaba-rocketmq" }

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# ApsaraMQ for RocketMQ: "a distributed message queue service that supports reliable message-based
3# asynchronous communication among microservices, distributed systems, and serverless applications"
4# ("Introduction to ApsaraMQ for RocketMQ"). Messages are persisted and redelivered until consumed,
5# with ordered, transactional and scheduled messages as message types.
6schemaVersion: "1"
7type: "component"
8id: "alibaba-rocketmq"
9kind: "queue"
10provider: "alibabacloud"
11docs: "https://www.alibabacloud.com/help/en/apsaramq-for-rocketmq"
12defaults:
13  managed: true
14  delivery: "at-least-once"
15  persistence: true
16  replay: true
17properties:
18  instanceVersion:
19    type: "enum"
20    values: ["4.x", "5.x"]
21  messageType:
22    type: "enum"
23    values: ["normal", "ordered", "transactional", "scheduled"]
24    default: "normal"

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