IBM MQ on Cloud

ibm Queueibm-mq-on-cloud

Managed IBM MQ queue manager on IBM Cloud with persistent, transactional message delivery.

Provider: ibm
Kind: Queue
Category: Messaging
Official docs: https://cloud.ibm.com/docs/mqcloud

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
deployment · component property	enum	single-instance \| high-availability	no	—	inherited
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
plan · component property	enum	lite \| reserved-deployment \| reserved-capacity	no	—	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: "mq-on-cloud", component: "ibm-mq-on-cloud" }

Other Queue products · 23

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# IBM MQ on Cloud: IBM MQ delivered as a managed service on IBM Cloud; the placed node is a queue
3# manager ("IBM MQ on Cloud"). Persistent messages are logged to disk and delivered once inside a
4# unit of work, as with the self-hosted product (`ibm-mq` under default). A backout queue is set
5# per queue, so deadLetterQueue keeps the kind default.
6schemaVersion: "1"
7type: "component"
8id: "ibm-mq-on-cloud"
9kind: "queue"
10provider: "ibm"
11docs: "https://cloud.ibm.com/docs/mqcloud"
12defaults:
13  managed: true
14  delivery: "at-least-once"
15  persistence: true
16properties:
17  deployment:
18    type: "enum"
19    values: ["single-instance", "high-availability"]
20  plan:
21    type: "enum"
22    values: ["lite", "reserved-deployment", "reserved-capacity"]

The same page as markdown, for an agent: /catalogue/components/ibm-mq-on-cloud.md