Generic Pub/Sub topic

Pub/Sub topicpubsub-topic

Vendor-neutral Pub/Sub topic. Use when the real product is not in the catalogue; every rule for this kind still applies.

Provider
default
Category
Messaging
Official docs
not recorded
Generic?
Vendor-neutral: the kind itself
Properties · 0 set by this component
propertytypevaluesrequireddefault
deliveryenumat-most-once | at-least-once | exactly-onceyes—
managedboolean—nofalse
orderingenumnone | per-keynonone
replayboolean—nofalse
topicPerEventType · advancedboolean—notrue
Rules that apply · 1

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.

pubsub-replay-required

The design declares that consumers must be able to replay history. A fan-out topic that does not retain messages cannot deliver that.

  • — all of these hold:
  • — the design requirement `messaging.replay` is true
  • — the node's `replay` is false
Use it in a design
nodes:
  - { id: "pubsub-topic", component: "pubsub-topic" }
Other Pub/Sub topic products · 12
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# The vendor-neutral Pub/Sub topic: the kind itself, with no product behind it. It sets no
# defaults and adds no properties, so every required kind property stays required on the node.
schemaVersion: "1"
type: "component"
id: "pubsub-topic"
kind: "pubsub-topic"
provider: "default"

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