Redis Pub/Sub

Pub/Sub topicredis-pubsub

Fire-and-forget channel fan-out inside Redis; disconnected subscribers miss messages.

Provider
default
Category
Messaging
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
cluster · component propertyboolean—nofalseinherited
deliveryenumat-most-once | at-least-once | exactly-onceyes—▸ at-most-once
managedboolean—nofalseinherited
orderingenumnone | per-keynonone▸ per-key
replayboolean—nofalse▸ false
topicPerEventType · advancedboolean—notrueinherited
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: "redis-pubsub", component: "redis-pubsub" }
Other Pub/Sub topic products · 12
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Redis PUBLISH/SUBSCRIBE: fire-and-forget fan-out. Messages sent while a subscriber is disconnected are lost.
schemaVersion: "1"
type: "component"
id: "redis-pubsub"
kind: "pubsub-topic"
provider: "default"
docs: "https://redis.io/docs/latest/develop/interact/pubsub/"
defaults:
  delivery: "at-most-once"
  ordering: "per-key"
  replay: false
properties:
  cluster:
    type: "boolean"
    default: false

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