OCI Queue

Managed at-least-once queue with visibility timeouts and dead-lettering.

Provider: oci
Kind: Queue
Category: Messaging
Official docs: https://docs.oracle.com/en-us/iaas/Content/queue/overview.htm

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
ordering	enum	none \| per-key \| global	no	none	▸ none
persistence	boolean	—	no	true	▸ true
replay	boolean	—	no	false	inherited
retentionDays	integer	—	no	—	▸ 1
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", component: "oci-queue" }

Other Queue products · 23

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Oracle Cloud Queue: managed at-least-once queue with visibility timeouts and a dead-letter queue option.
3schemaVersion: "1"
4type: "component"
5id: "oci-queue"
6kind: "queue"
7provider: "oci"
8docs: "https://docs.oracle.com/en-us/iaas/Content/queue/overview.htm"
9defaults:
10  managed: true
11  delivery: "at-least-once"
12  ordering: "none"
13  persistence: true
14  retentionDays: 1
15properties:
16  visibilityTimeoutSeconds:
17    type: "integer"
18    default: 30

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