Solace PubSub+ Event Broker

Event broker offering direct messaging by default and guaranteed messaging with disk spooling.

Provider: default
Kind: Queue
Category: Messaging
Official docs: https://docs.solace.com/Basics/Direct-Messages.htm

Properties · 6 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	▸ false
delivery	enum	at-most-once \| at-least-once \| exactly-once	yes	—	▸ at-most-once
deliveryMode · component property	enum	direct \| persistent \| non-persistent	no	direct	inherited
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ false
maxAttempts	integer	—	no	—	inherited
ordering	enum	none \| per-key \| global	no	none	▸ none
persistence	boolean	—	no	true	▸ false
redundancy · component property	boolean	—	no	false	inherited
replay	boolean	—	no	false	▸ false
replication · component property	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: "solace", component: "solace" }

Other Queue products · 23

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Solace PubSub+ Event Broker: direct messaging is the default delivery system and is reliable but not
3# guaranteed; guaranteed messaging spools to disk and only then uses a dead message queue, which does
4# not pre-exist ("Direct Messages", "Configuring Queues").
5schemaVersion: "1"
6type: "component"
7id: "solace"
8kind: "queue"
9provider: "default"
10docs: "https://docs.solace.com/Basics/Direct-Messages.htm"
11defaults:
12  delivery: "at-most-once"
13  ordering: "none"
14  persistence: false
15  deadLetterQueue: false
16  replay: false
17  managed: false
18properties:
19  deliveryMode:
20    type: "enum"
21    values: ["direct", "persistent", "non-persistent"]
22    default: "direct"
23  redundancy:
24    type: "boolean"
25    default: false
26  replication:
27    type: "boolean"
28    default: false

The same page as markdown, for an agent: /catalogue/components/solace.md